For anyone troubleshooting external WAN clients timing out on NetherNet (InitialConnection-13 / InitialConnection-45):
Root Cause: The BDS executable configuration parser does not properly parse server-udp-ports range tuples (<IP>:<START>-<END>:<START>-<END>) or comma-separated lists as documented in bedrock_server_how_to.html.
When ranges or lists are used, BDS fails to build the external NAT mapping table and falls back to advertising only its local/private RFC 1918 host candidate in WebRTC ICE negotiation. External clients only receive the private IP, causing ICE/DTLS handshakes to fail.
Immediate Workaround: You must manually unroll your UDP port ranges into individual, single-port lines in
I have filed a dedicated root-cause bug report focusing specifically on this configuration parser defect: [BDS-23126]. Please upvote [BDS-23126] so the dev team prioritizes patching the range parser in the next BDS build.
ProtonPoblano
For anyone troubleshooting external WAN clients timing out on NetherNet (InitialConnection-13 / InitialConnection-45):
Root Cause:
The BDS executable configuration parser does not properly parse
server-udp-portsrange tuples (<IP>:<START>-<END>:<START>-<END>) or comma-separated lists as documented inbedrock_server_how_to.html.When ranges or lists are used, BDS fails to build the external NAT mapping table and falls back to advertising only its local/private RFC 1918 host candidate in WebRTC ICE negotiation. External clients only receive the private IP, causing ICE/DTLS handshakes to fail.
Immediate Workaround:
You must manually unroll your UDP port ranges into individual, single-port lines in
server.properties:I have filed a dedicated root-cause bug report focusing specifically on this configuration parser defect: [BDS-23126]. Please upvote [BDS-23126] so the dev team prioritizes patching the range parser in the next BDS build.