diff options
| author |   Jason A. Donenfeld <Jason@zx2c4.com> | 2019-09-28 19:20:49 +0200 |
|---|---|---|
| committer | Jason A. Donenfeld <Jason@zx2c4.com> | 2019-10-01 13:59:42 +0200 |
| commit | bba001018f0a8f2fb1c88a6b97adb23690a6512b (patch) | |
| tree | 9e9d8ad1787e72f9398fdf3b01f003d743178d2e /tunnel/winipcfg | |
| parent | elevate: use fallback shellexecute when not EV-signed (diff) | |
| download | wireguard-windows-bba001018f0a8f2fb1c88a6b97adb23690a6512b.tar.xz wireguard-windows-bba001018f0a8f2fb1c88a6b97adb23690a6512b.zip | |
tunnel: windows does not always add/remove routes with up/down interface
On Linux, we're used to routes being added after an interface is up, and
routes being removed as a consequence of an interface going down. On
Windows, this isn't always the case, at least not from the perspective
of the route notifiers. In order to work around this and make a
multi-interface model coherent, we search for a new default route not
only whenever the routing table changes but also whenever any interface
link parameters change, such as up/down.
The practical consequence is that now WireGuard connects properly when
wifi is disconnected and then reconnected.
Reported-by: Nenad Kozul <me@nenadkozul.com>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to 'tunnel/winipcfg')
| -rw-r--r-- | tunnel/winipcfg/types.go | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/tunnel/winipcfg/types.go b/tunnel/winipcfg/types.go index 684a6c77..81f9335d 100644 --- a/tunnel/winipcfg/types.go +++ b/tunnel/winipcfg/types.go @@ -510,6 +510,10 @@ const ( MibInitialNotification // Initial notification ) +type ChangeCallback interface { + Unregister() error +} + // TunnelType enumeration type defines the encapsulation method used by a tunnel, as described by the Internet Assigned Names Authority (IANA). // https://docs.microsoft.com/en-us/windows/desktop/api/ifdef/ne-ifdef-tunnel_type type TunnelType uint32 |