Andrew Dunham 77ff705545 net/portmapper: never select port 0 in UPnP ... Port 0 is interpreted, per the spec (but inconsistently among router software) as requesting to map every single available port on the UPnP gateway to the internal IP address. We'd previously avoided picking ports below 1024 for one of the two UPnP methods (in #7457), and this change moves that logic so that we avoid it in all cases. Updates #8992 Signed-off-by: Andrew Dunham <andrew@du.nham.ca> Change-Id: I20d652c0cd47a24aef27f75c81f78ae53cc3c71e		2023-08-21 14:33:26 -04:00
..
disabled_stubs.go	all: update copyright and license headers	2023-01-27 15:36:29 -08:00
igd_test.go	all: avoid repeated default interface lookups	2023-04-20 15:46:01 -07:00
pcp_test.go	all: update copyright and license headers	2023-01-27 15:36:29 -08:00
pcp.go	all: update tools that manage copyright headers	2023-01-27 15:36:29 -08:00
pcpresultcode_string.go	all: update copyright and license headers	2023-01-27 15:36:29 -08:00
pmpresultcode_string.go	all: update copyright and license headers	2023-01-27 15:36:29 -08:00
portmapper_test.go	all: avoid repeated default interface lookups	2023-04-20 15:46:01 -07:00
portmapper.go	all: avoid repeated default interface lookups	2023-04-20 15:46:01 -07:00
upnp_test.go	cmd/tailscale, cmd/tailscaled: move portmapper debugging into tailscale CLI	2023-03-03 14:21:38 -05:00
upnp.go	net/portmapper: never select port 0 in UPnP	2023-08-21 14:33:26 -04:00