On Sat, 8 May 2021 19:49:06 +0100
lejeczek wrote:
> > Also remember that sets of AllowedIPs should be unique within the network,
> > i.e. can't have the same AllowedIPs or ranges listed for multiple nodes at
> > the
> > same time. Setting it to the same /24 on all nodes will not work.
> >
> >
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,
On 08/05/2021 17:50, Roman Mamedov wrote:
On Sat, 8 May 2021 17:31:58 +0100
lejeczek wrote:
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
On Sat, 8 May 2021 17:31:58 +0100
lejeczek wrote:
> 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
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