Bedrock Dedicated Server 1.26.51.1 does not appear in LAN worlds with NetherNet enabled

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.

Additional findings and confirmed workaround

Packet captures show that Bedrock clients send a 33-byte RakNet Unconnected Ping broadcast to UDP port 19132. The packet reaches the Linux server, but Bedrock Dedicated Server 1.26.51.1 does not respond and does not listen on UDP 19132 while idle.

The server does listen on TCP 19132 for NetherNet and on UDP 7551. Direct connections by IP address work normally.

As a test, I ran a small UDP responder on port 19132. It replies to the client with a RakNet Unconnected Pong containing the server information.

This workaround has the following confirmed results:

• The dedicated server immediately appears in the LAN worlds list on PlayStation 4.

• The iPhone processes the response and updates the displayed name of a manually added server.

• Without the responder, the PlayStation 4 does not display the server.

• The responder only provides LAN discovery; it does not proxy or handle the actual game connection.

Minimal proof-of-concept:

#!/usr/bin/env python3

import secrets
import socket
import struct

MAGIC = bytes.fromhex(
    "00ffff00fefefefefdfdfdfd12345678"
)

SERVER_GUID = secrets.randbits(63)

motd = (
    f"MCPE;"
    f"Test Server;"       # Server name
    f"2193;"              # Protocol version for 1.26.51
    f"1.26.51;"           # Game version
    f"0;"                 # Current players
    f"10;"                # Maximum players
    f"{SERVER_GUID};"
    f"Test World;"        # Level name
    f"Survival;"
    f"1;"
    f"19132;"
    f"19133;"
).encode("utf-8")

sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock.bind(("0.0.0.0", 19132))

while True:
    data, client = sock.recvfrom(2048)

    # RakNet Unconnected Ping
    if len(data) < 33 or data[0] not in (0x01, 0x02):
        continue

    if data[9:25] != MAGIC:
        continue

    response = (
        b"\x1c"                           # Unconnected Pong
        + data[1:9]                       # Original timestamp
        + struct.pack(">Q", SERVER_GUID)
        + MAGIC
        + struct.pack(">H", len(motd))
        + motd
    )

    sock.sendto(response, client)

This strongly suggests that LAN discovery is failing because the dedicated server no longer responds to the legacy RakNet discovery broadcasts sent by the clients. Sending the expected response is sufficient for the PlayStation 4 to display the server again.

At the same time, sudo ss -lunp | grep ':19132' returns no results. The server is running and listening on TCP port 19132.

I’m pretty sure the server is supposed to run on the UDP Port 19132.

But I got a similar issue on 1.26.51.1. For me when a launch the server with a minimal configuration like this :

server-name=TestServer
server-port=19132
server-portv6=0
difficulty=normal
transport=nethernet
enable-lan-visibility=false

I get this output :

[2026-09-25 20:40:35:313 INFO] Configuration: Publish
[2026-09-25 20:40:35:313 INFO] Contents of server.properties: {}
[2026-09-25 20:40:35:314 INFO] Level Name: level
[2026-09-25 20:40:35:314 INFO] Profiler config ('bootstrap.json') load result: success=1, errorMessage=(null)
[2026-09-25 20:40:35:314 INFO] No CDN config file found at: cdn_config.json for dedicated server
[2026-09-25 20:40:35:314 INFO] Game mode: 0 Survival
[2026-09-25 20:40:35:314 INFO] Difficulty: 2 NORMAL
[2026-09-25 20:40:35:317 INFO] Content logging to console is enabled.
[2026-09-25 20:40:35:318 INFO] 

#####################################################
#                                                   #
#               LOADING VANILLA WORLD               #
#                                                   #
#####################################################
[2026-09-25 20:40:36:420 INFO] Opening level 'worlds/level/db'
[2026-09-25 20:40:36:421 INFO] Accepting clients on [::]:19132
[2026-09-25 20:40:36:503 INFO] Pack Stack - None
[2026-09-25 20:40:39:712 INFO] Signed in to signaling service successfully
[2026-09-25 20:40:40:402 INFO] Waiting for Minecraft services...
[2026-09-25 20:40:40:502 INFO] Server started.
[2026-09-25 20:40:40:502 INFO] ================ TELEMETRY MESSAGE ===================
[2026-09-25 20:40:40:502 INFO] Server Telemetry is currently not enabled. 
[2026-09-25 20:40:40:502 INFO] Enabling this telemetry helps us improve the game.
[2026-09-25 20:40:40:502 INFO] 
[2026-09-25 20:40:40:502 INFO] To enable this feature, add the line 'emit-server-telemetry=true'
[2026-09-25 20:40:40:502 INFO] to the server.properties file in the handheld/src-server directory
[2026-09-25 20:40:40:502 INFO] ======================================================

So according to the logs the server should be listening to 19132

But when I actually run

UNCONN 0      0                    *:7551            *:*    users:(("bedrock_server",pid=3111,fd=14))

The server actually runs on 7551 for some reason?! From my understanding this is a port used in the old RakNet protocol. Anyway even though I checked the usual stuff I can’t connect to the server … but I can see with tcpdump that connections are coming through but with both 7551 and 19132 I get no response on the client (Android and iOS)

Also whats weird is that I have a second server which is has a very similar (both are Ubuntu 26.04 but running through crafty) where the same version works just fine … curiously enough though on that machine I don’t get Waiting for Minecraft services... line in the logs.

​Problem also exists with 1.26.52.3