aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/go.sum
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2019-09-28 19:20:49 +0200
committerJason A. Donenfeld <Jason@zx2c4.com>2019-10-01 13:59:42 +0200
commit352fb4c3518b648a5ad9b6bbac8d2b5fa8854179 (patch)
tree9e9d8ad1787e72f9398fdf3b01f003d743178d2e /go.sum
parentelevate: use fallback shellexecute when not EV-signed (diff)
downloadwireguard-windows-352fb4c3518b648a5ad9b6bbac8d2b5fa8854179.tar.xz
wireguard-windows-352fb4c3518b648a5ad9b6bbac8d2b5fa8854179.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>
Diffstat (limited to 'go.sum')
0 files changed, 0 insertions, 0 deletions