Brad Fitzpatrick 22c462bd91 wgengine/monitor: fix copy/paste-o to actually monitor route changes ... Due to a copy/paste-o, we were monitoring address changes twice, and not monitoring route changes at all. Verified with 'tailscale debug --monitor' that this actually works now (while running 'route add 10.3.0.0 mask 255.255.0.0 10.0.0.1' and 'route delete (same)' back and forth in cmd.exe) In practice route changes are accompanied by address changes and this doesn't fix any known issues. I just noticed this while reading this code again. But at least the code does what it was trying to do now.		2020-10-09 09:04:26 -07:00
..
monitor_freebsd.go	wgengine/monitor_freebsd.go: remove duplicated errcheck	2020-08-21 09:48:22 -07:00
monitor_linux.go	wgengine/monitor: add, clean up netlink logging on route changes	2020-08-12 13:27:14 -07:00
monitor_unsupported.go	wgengine/monitor: add Windows linkchange monitor	2020-08-13 07:39:26 -07:00
monitor_windows.go	wgengine/monitor: fix copy/paste-o to actually monitor route changes	2020-10-09 09:04:26 -07:00
monitor.go	wgengine/monitor: add a poller to the Windows link change monitor	2020-08-24 21:23:52 -07:00