You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not migrate v2 "Network settings" to a "Routing" module. They just are not the same.
In particular, when overriding the "Default gateway", v2 used to tweak in place:
The redirect-gateway flags in OpenVPN configurations (and this usually works)
The AllowedIPs directive in WireGuard configurations
The "Routing" module in v3 is doing a different thing, i.e. "include/exclude this route in/from the tunnel interface".
With WireGuard in particular, this is insufficient because the tunnel performs additional checks on allowed IP packets. E.g. if we include the default route with a "Routing" module, but the same route is not also present in AllowedIPs, this will happen:
IPv4 packet with disallowed source address from peer
and traffic will be dropped.
The text was updated successfully, but these errors were encountered:
Do not migrate v2 "Network settings" to a "Routing" module. They just are not the same.
In particular, when overriding the "Default gateway", v2 used to tweak in place:
redirect-gateway
flags in OpenVPN configurations (and this usually works)AllowedIPs
directive in WireGuard configurationsThe "Routing" module in v3 is doing a different thing, i.e. "include/exclude this route in/from the tunnel interface".
With WireGuard in particular, this is insufficient because the tunnel performs additional checks on allowed IP packets. E.g. if we include the default route with a "Routing" module, but the same route is not also present in AllowedIPs, this will happen:
and traffic will be dropped.
The text was updated successfully, but these errors were encountered: