James Tucker 7df6f8736a wgengine/netstack: only add addresses to correct protocols ... Prior to an earlier netstack bump this code used a string conversion path to cover multiple cases of behavior seemingly checking for unspecified addresses, adding unspecified addresses to v6. The behavior is now crashy in netstack, as it is enforcing address length in various areas of the API, one in particular being address removal. As netstack is now protocol specific, we must not create invalid protocol addresses - an address is v4 or v6, and the address value contained inside must match. If a control path attempts to do something otherwise it is now logged and skipped rather than incorrect addressing being added. Fixes tailscale/corp#15377 Signed-off-by: James Tucker <james@tailscale.com>		2023-10-23 17:29:36 -07:00
..
netstack_linux.go	all: update copyright and license headers	2023-01-27 15:36:29 -08:00
netstack_test.go	wgengine, proxymap: split out port mapping from Engine to new type	2023-09-17 20:06:43 +01:00
netstack.go	wgengine/netstack: only add addresses to correct protocols	2023-10-23 17:29:36 -07:00
subnet_router_wrapper.go	tsd: add package with System type to unify subsystem init, discovery	2023-05-04 14:21:59 -07:00