mirror of
https://github.com/tailscale/tailscale.git
synced 2024-11-26 19:45:35 +00:00
1608831c33
Windows requires routes to have a nexthop. Routes created using the interface's local IP address or an unspecified IP address ("0.0.0.0" or "::") as the nexthop are considered on-link routes. Notably, Windows treats on-link subnet routes differently, reserving the last IP in the range as the broadcast IP and therefore prohibiting TCP connections to it, resulting in WSA error 10049: "The requested address is not valid in its context. This does not happen with single-host routes, such as routes to Tailscale IP addresses, but becomes a problem with advertised subnets when all IPs in the range should be reachable. Before Windows 8, only routes created with an unspecified IP address were considered on-link, so our previous approach of using the interface's own IP as the nexthop likely worked on Windows 7. This PR updates configureInterface to use the TailscaleServiceIP (100.100.100.100) and its IPv6 counterpart as the nexthop for subnet routes. Fixes tailscale/support-escalations#57 Signed-off-by: Nick Khyl <nickk@tailscale.com> |
||
---|---|---|
.. | ||
callback.go | ||
consolidating_router_test.go | ||
consolidating_router.go | ||
ifconfig_windows_test.go | ||
ifconfig_windows.go | ||
router_darwin.go | ||
router_default.go | ||
router_fake.go | ||
router_freebsd.go | ||
router_linux_test.go | ||
router_linux.go | ||
router_openbsd.go | ||
router_test.go | ||
router_userspace_bsd.go | ||
router_windows_test.go | ||
router_windows.go | ||
router.go | ||
runner.go |