Network Storage (UDPFS)

UDPFS exposes a folder on a PC over your local network as the Network (UDPFS) device (udpfs:). It is the fastest way to browse PC files, copy things to and from the console, and boot Neutrino ISOs without moving a drive.

Setup

1. PC: start UDPFSD with the folder to serve. Allow it through the PC firewall (it uses UDP, so it is local-network only).
2. PS2: in Settings > Network set the IP address, netmask and gateway (defaults 192.168.0.10, 255.255.255.0, 192.168.0.1). They are stored in IPCONFIG.DAT beside the running ELF, or in mcN:/SYS-CONF/IPCONFIG.DAT. UDPFS is given the IP address; there is no DNS field. Choose an address in the PC’s subnet.
3. Open Network (UDPFS) in the Files tab. Launchstation loads DEV9, the UDPFS Ethernet driver, a tiny built-in IP stack and the UDPFS filesystem, then opens udpfs:/. When the server answers the card shows the console’s network settings; otherwise UDPFS server not found (“Check the cable, IP settings and that the UDPFS server is running”).
4. Optionally enable Settings > Storage & devices > Start devices automatically > Auto-start network (UDPFS) (off by default).

What you can do

• Browse and copy. Directory listings come from the server with sizes and dates. A listing that fails part-way is treated as an error rather than a partial list, so a copy never silently skips files. The UDPFS driver reports every close as successful, so each file pasted to udpfs:, and each finished .psu backup written there, is opened again and its size compared with what was written; a missing or wrong-sized copy fails at Verifying destination and a Move (or Cut, then Create PSU) keeps its source. A .cso/.ciso/.zso/.ziso/.chd image that the server reads back decompressed is accepted. Get Size takes a file's size from the listing when the server does not answer a stat.
• Writing is off by default. The File Browser’s write commands (copy to, delete, rename, new folder, paste) stay disabled on udpfs: and host: until Settings > Network > Allow writing over the network is on. This does not affect FTP.
• Neutrino ISOs. Backend udpfs; the ISO is read straight from the PC. The Neutrino ELF can be on the share, a memory card or elsewhere. See Neutrino.
• Ember. The Ember path check does not exclude UDPFS, but that combination has not been hardware-verified.
• HDD header injection. udpfs:/__Headers/<partition>/ is one of the header sources for the HDD Manager.
• VMC images. A virtual memory card image on the share can be mounted from the File Browser.
• Not supported: POPStarter VCDs from UDPFS. Launching programs straight from the share is not a documented path; copy the program to USB, HDD or a memory card if it will not start.

Stack rules

• UDPFS and FTP / PS2Link / Google Drive are different Ethernet stacks. Only one can be loaded; switching resets the IOP (see Network & PC Integration). After using FTP or cloud features, opening UDPFS reloads the other stack.
• DEV9 sharing. UDPFS, the internal HDD and exFAT HDD all use DEV9 and can be active together. On an early Japanese console the PC CARD CF driver owns the bus instead, and network loaders refuse to start while it does.
• Copying between UDPFS and host:, SMB or PC CARD CF is refused (“Incompatible drivers to perform action”) before either driver is loaded. host: and SMB run on the other Ethernet stack.
• The IP address is handed to the UDPFS stack when it loads, so use Tools > Reboot IOP after changing it and then open the device again.

Troubleshooting

1. “UDPFS server not found”. Verify cable and link lights, the PS2’s IP/netmask, that the PC is on the same subnet, and that UDPFSD is running and not blocked by a firewall.
2. Writes are disabled. Turn on Allow writing over the network (and make sure the server share is writable).
3. Nothing happens on open. If DEV9 is owned by PC CARD CF, or an earlier stack switch was refused, reboot the IOP from Tools and try again.
4. Copy to a memory card fails mid-way. The error message includes the driver code. UDPFS can return partial progress before an error; Launchstation handles short reads and stops at the error without claiming success. Report the exact build, server version, and a serial log if available.