UDPBD Server

UDPBD (UDP Block Device) exposes a single disc image as a virtual block device over the local network. Rather than translating filesystem calls, the console sends raw sector read and write commands directly over UDP port 48573.

Block Device vs Filesystem Protocol

While UDPFS and SMB serve an entire directory containing multiple games, folders, art, and configurations, UDPBD assigns one raw disk image (ISO or IMG) per server process. The console interacts with the server exactly as if it were a physical optical disc or hard drive plugged directly into the system bus.

1. Protocol Overview

Parameter	Value	Notes
Default Port	UDP 48573 (`0xBDBD`)	Standard UDPBD broadcast discovery and data port.
Payload Target	Single Disc Image	Select an `.iso` or `.img` file.
Discovery Mechanism	Broadcast Probe	Client broadcasts to `255.255.255.255:48573`; server replies with capacity and sector size.
Write Support	Optional	Server can run read-only or allow sector modifications.

2. Running UDPBD

Desktop Launcher

1. Open the UDPBD card in PS2 Servers Desktop.
2. Click Browse and choose your target .iso file.
3. Click Start. The server immediately begins listening on UDP port 48573.

Core Terminal CLI

python ps2servers.py serve udpbd /srv/images/game.iso --read-only

Add --bind <PC_IP> to pin the interface, or --port <PORT> if using a non-standard port.

Edge Native Server

ps2servers-edge udpbd --image /srv/images/game.iso --read-only

Fast Go native implementation with bounded sector caching and minimal CPU overhead.

3. Console Client Configuration

To boot from a UDPBD server, your console loader must include a UDPBD driver:

Neutrino: Supports UDPBD natively via its network boot driver.
RiptOPL: Select Network Boot in Game Sources and ensure the UDPBD backend is selected.
Ensure your console IP settings belong to the same subnet as the host serving the UDPBD image.