I can reproduce a related issue on BDS 1.26.51.1 with transport=nethernet.
Behind IPv4 NAT, external connections only work reliably when I explicitly specify the public IPv4 address in server-udp-ports.
Also:
With only one UDP mapping, only the first distinct client can connect. The same client can reconnect repeatedly, but another client cannot connect until BDS is restarted.
Multiple clients can connect if I list several UDP mappings individually, for example: server-udp-ports=<PUBLIC_IP>:55000:55000,<PUBLIC_IP>:55001:55001,...
The documented range syntax, for example: server-udp-ports=<PUBLIC_IP>:55000-55019:55000-55019 does not work for me.
The router/firewall configuration is unchanged between these tests, and packet captures confirm that UDP traffic reaches the BDS host.
guregoro
I can reproduce a related issue on BDS 1.26.51.1 with transport=nethernet.
Behind IPv4 NAT, external connections only work reliably when I explicitly specify the public IPv4 address in server-udp-ports.
Also:
With only one UDP mapping, only the first distinct client can connect. The same client can reconnect repeatedly, but another client cannot connect until BDS is restarted.
Multiple clients can connect if I list several UDP mappings individually, for example:
server-udp-ports=<PUBLIC_IP>:55000:55000,<PUBLIC_IP>:55001:55001,...
The documented range syntax, for example:
server-udp-ports=<PUBLIC_IP>:55000-55019:55000-55019
does not work for me.
The router/firewall configuration is unchanged between these tests, and packet captures confirm that UDP traffic reaches the BDS host.