A Windows Bedrock 1.26.51 client can connect directly to the server and play successfully after allowing TCP 19132.
On PS5, tcpdump shows the console repeatedly sending 33-byte UDP LAN discovery packets to the subnet broadcast address on UDP 19132, and the packets reach the BDS host, but BDS sends no response. ss -lunp | grep 19132 also returns nothing while NetherNet is enabled.
I also tested transport=raknet as a diagnostic. With RakNet enabled, BDS immediately opens UDP 19132 and logs:
IPv4 supported, port: 19132: Used for gameplay and LAN discovery
The server then immediately appears in the PS5 LAN list. However, BDS 1.26.51.1 reports that NetherNet is the only supported transport and players cannot connect while using RakNet.
Switching back to transport=nethernet causes the UDP 19132 listener to disappear and the server disappears from the PS5 LAN list again.
This appears to confirm that LAN discovery itself is not being serviced under NetherNet, rather than a network/firewall issue.
Emenecker
I can independently reproduce this on PlayStation 5 with the official Linux BDS 1.26.51.1.
Server: Ubuntu 24.04.4 LTS
Network: 10.0.0.0/23
PS5: 10.0.0.130
BDS: transport=nethernet, enable-lan-visibility=true
A Windows Bedrock 1.26.51 client can connect directly to the server and play successfully after allowing TCP 19132.
On PS5, tcpdump shows the console repeatedly sending 33-byte UDP LAN discovery packets to the subnet broadcast address on UDP 19132, and the packets reach the BDS host, but BDS sends no response. ss -lunp | grep 19132 also returns nothing while NetherNet is enabled.
I also tested transport=raknet as a diagnostic. With RakNet enabled, BDS immediately opens UDP 19132 and logs:
IPv4 supported, port: 19132: Used for gameplay and LAN discovery
The server then immediately appears in the PS5 LAN list. However, BDS 1.26.51.1 reports that NetherNet is the only supported transport and players cannot connect while using RakNet.
Switching back to transport=nethernet causes the UDP 19132 listener to disappear and the server disappears from the PS5 LAN list again.
This appears to confirm that LAN discovery itself is not being serviced under NetherNet, rather than a network/firewall issue.