UDPFS Handoff & Diagnostics

Step-by-step diagnostic methodologies for troubleshooting UDPFS connection issues, interpreting server log prefixes, and utilizing the 45-second inactivity telemetry report.

Observability First

A server log that simply goes quiet cannot tell you what failed on its own. PS2 Servers Core includes active network-probing diagnostics that distinguish between console IOP crashes, driver read errors, and packet routing stalls.

1. Decoding Server Log Prefixes

Every incoming packet logged in PS2 Servers Core begins with a client endpoint prefix:

[192.168.1.150:62966] Discovery probe received (seq=0)
[192.168.1.150:62966] Session created -> data socket assigned 62967
[192.168.1.150:62967] OPEN DVD/SLUS_201.74.Rumble Racing.iso (flags=1)

Client IP Changes During Launch

If you see the IP change midway through booting (e.g. from 192.168.1.150 during game browsing to 192.168.0.10 on launch), the launched loader or game-specific configuration has a different static IP configured in its network driver. Ensure static IPs match across all configuration screens.

Repeated Discovery (seq=0 Loops)

If the server logs repeated seq=0 probes without advancing to data reads, the console is broadcasting discovery packets but cannot receive the server's reply. Check that the server's reply is not routed out of a secondary network interface (Wi-Fi).

2. The 45-Second Inactivity Diagnostic

When a console with active open files stops communicating for 45 seconds, PS2 Servers Core sends an active ARP probe and evaluates the network interface, printing one of three definitive diagnostic verdicts:

Verdict 1: "Still sending"

Meaning: The console is continuing to transmit UDP packets, but they are out of sequence or corrupted.
Cause: Packet loss or high latency on the network path. Ensure the connection is wired and that no conflicting UDP traffic saturates the link.

Verdict 2: "Still answers ARP"

Meaning: The PS2's network adapter is fully alive and responding to low-level link layer probes, but the game loader driver has ceased requesting data.
Cause: Neutrino and OPL drivers halt completely after a single unrecoverable disc read error. The log lines immediately preceding this message identify the exact sector or file that caused the failure (e.g. bad disc dump, unsupported compression container).

Verdict 3: "No longer answers ARP"

Meaning: The PS2 hardware is completely unresponsive on the network link.
Cause: The console's Input/Output Processor (IOP) crashed, the network adapter lost power, or the console was reset or turned off.

3. Step-by-Step Resolution Workflow

Pin the PC Bind Address: On the UDPFS card, click Use LAN IP to bind data packets directly to your PS2-facing Ethernet interface.
Test a Known-Good ISO: Always test with an uncompressed, 1:1 Redump-verified .iso image before troubleshooting compressed ZSO/CSO/CHD containers.
Verify Port Pairing: If running with a manual firewall, ensure both discovery port 62966 and your data port (e.g. 62967) are permitted in UDP rules.

Run Core in Verbose Mode: For deep troubleshooting, launch from the terminal:

python ps2servers.py serve udpfs --root-dir /srv/ps2 --bind 192.168.1.100 --verbose