wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: lejeczek <peljasz@yahoo.co.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: secondary IP on wg0 fails
Date: Sun, 9 May 2021 07:17:12 +0100	[thread overview]
Message-ID: <61cb8e11-0441-6f4a-891e-7c5800391ead@yahoo.co.uk> (raw)
In-Reply-To: <204f6e7b-d594-c2c0-5242-1643055065c3@yahoo.co.uk>



On 08/05/2021 17:31, lejeczek wrote:
> Hi guys.
>
> I'm experiencing a pretty weird wireguard, or perhaps 
> kernel/OS stack bits behavior.
>
> I have three nodes which all can ping each other on wg0's 
> IPs but when I add a secondary IP:
>
> -> $ ip addr add 10.0.0.226/24 dev wg0
>
> it gets weird, namely, say when that sec IP is on
> A -> B ping returns; C ping waits, no errors, no return
> B -> both C & A pings return
> C -> neither A nor B ping returns
>
> I'm on CentOS with 4.18.0-301.1.el8.x86_64.
> All three nodes are virtually identical kvm VMs.
>
> any suggestions as to what is not working here or how to 
> troubleshoot are vey appreciated.
> many thanks, L.
>
>
>
>
What I've just noticed for the first time is, config eg.:
..
[Peer]
..
AllowedIPs = 10.0.0.2/32, 10.0.0.226/32
Endpoint = 10.1.1.224:51852

[Peer]
..
AllowedIPs = 10.0.0.3/32, 10.0.0.226/32
Endpoint = 10.1.1.225:51853

 > $ wg
interface: wg0
   public key: c+gJArxYd8+=
   private key: (hidden)
   listening port: 51851

peer: K/=
   preshared key: (hidden)
   endpoint: 10.1.1.225:51853
   allowed ips: 10.0.0.3/32, 10.0.0.226/32
   latest handshake: 16 seconds ago
   transfer: 124 B received, 2.14 KiB sent

peer: /KidNfhqgP/+c3A=
   preshared key: (hidden)
   endpoint: 10.1.1.224:51852
   allowed ips: 10.0.0.2/32                # !! no 
10.0.0.226/32 ?
   latest handshake: 3 minutes, 15 seconds ago
   transfer: 180 B received, 92 B sent

That is probably why only 10.0.0.3 with secondary IP is 
"reachable". Right?
If that is by design and expected - why is that and how to 
make a "floating" IP work if that is by design?

thanks, L.

      parent reply	other threads:[~2021-05-09  6:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <204f6e7b-d594-c2c0-5242-1643055065c3.ref@yahoo.co.uk>
2021-05-08 16:31 ` lejeczek
2021-05-08 16:50   ` Roman Mamedov
2021-05-08 18:49     ` lejeczek
2021-05-09  7:52       ` Roman Mamedov
2021-05-09  6:17   ` lejeczek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61cb8e11-0441-6f4a-891e-7c5800391ead@yahoo.co.uk \
    --to=peljasz@yahoo.co.uk \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: secondary IP on wg0 fails' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).