markus.woschank at gmail.com
Sun Nov 5 01:05:18 CET 2017
>> While searching for arguments I realised that wireguard will allow a
>> peer to connect with a different IP from the one set in the
>> Not sure if this is the best behaviour (I understand that the peer
>> needs to know the secret key, anyway not sure).
> Yes, wg does this. It's a deliberate design decision which is important
> to support roaming peers.
> This is not a security problem. Since wg uses UDP as a transport
> protocol, source IPs can be trivially forged by an attacker; therefore
> checking source IPs wouldn't add any real value.
Nevertheless this is different from the behaviour I expected:
If I specify an endpoint IP the peer is only allowed to connect via
the specified IP/Port.
If I don't specify an endpoint IP the peer is allowed to connect from
Yes, I could have read the documentation more carefully but maybe
restricting the remote IP/Port in cases the endpoint has been
specified would prevent some confusion/discussion.
This would also make the behaviour of the showconf command more
"consistent" because then the information, if the endpoint is set by
config or not, would be available and also the showconf command could
generate an equivalent configuration.
I imaging specifying an endpoint IP for a peer and than discovering
that it connected from a different IP may be surprising to some. I
generally prefer for things to break if I configure them the wrong way
and not work "sometimes" (wrong endpoint IP on one side but the other
first initiating the connection most of the time).
More information about the WireGuard