On Tue, Nov 28, 2017 at 00:13:06 -0600, Bruno Wolff III <[email protected]> wrote:
I do some source address rewriting and it may be that the initial addresses used for the encapsulating packets are different than the ones later.
When I'm on the local network, 192.168.6.1 gets used for the initial source adddress and gets rewritten to 98.103.208.26 in order to make the source consistent for the laptop whether or not it is on the local network. (That way I don't need to allow connections from 192.168.6.1 somewhere else where it wouldn't be my router.) When this happens the source port seems to normally get changed. Wireguard on the laptop remembers the new source port and tries to keep using it after the router is rebooted. But during the reboot the router forgets about the port mapping so it ends up dropping the packets. It has no reason to send packets on its own to the laptop (and wouldn't know where to send them) so the port doesn't get corrected.
I think the correct fix is to know if I reboot the router for testing something, I need to also restart wireguard to make sure it is sending data to the expected port. This isn't going to be an issue in normal operation.
_______________________________________________ WireGuard mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/wireguard
