* Wireguard using wrong source IP and confusing NAT devices
@ 2019-10-01 14:53 Martin Wagner
0 siblings, 0 replies; only message in thread
From: Martin Wagner @ 2019-10-01 14:53 UTC (permalink / raw)
To: wireguard
[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]
One of my servers has two IPv4 addresses. When I try to connect to the
one that isn't configured as default route wireguard is still responding
on the other IP which is causing my NAT to drop the response. If I
change the Endpoint= in the client config to the default ip of the
server everything works fine.
Is this the expected behavior?
Traffic captured on the server:
1 0.000000000 client_ip → server_ip_1 WireGuard 190 Handshake
Initiation, sender=0xF493E197
2 0.000693930 server_ip_2 → client_ip WireGuard 134 Handshake
Response, sender=0x5A3B09B6, receiver=0xF493E197
3 5.119191567 client_ip → server_ip_1 WireGuard 190 Handshake
Initiation, sender=0x4064907A
4 5.119838133 server_ip_2 → client_ip WireGuard 134 Handshake
Response, sender=0xCAB5E13D, receiver=0x4064907A
Traffic captured on the client:
1 0.000000000 nat_ip → server_ip_1 WireGuard 176 Handshake
Initiation, sender=0xBC6FCC0F
2 5.116674624 nat_ip → server_ip_1 WireGuard 176 Handshake
Initiation, sender=0x87E999EA
[-- Attachment #1.2: Type: text/html, Size: 1388 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-11-27 9:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-01 14:53 Wireguard using wrong source IP and confusing NAT devices Martin Wagner
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).