Became unplayable this week.

Tried reinstalling and it didn't fix it.

Anyone else having this issue?

To the PlayStation Engineering and Firmware Development Team / Community:

I am reporting a critical interoperability bug regarding the PlayStation 5 Pro Wi-Fi 7 (802.11be) implementation when connecting to standard Dual-Band (2.4GHz + 5GHz) Wi-Fi 7 access points with Multi-Link Operation (MLO) enabled.

The Issue: When the PS5 Pro detects beacon frames advertising an MLO profile consisting exclusively of 2.4GHz and 5GHz bands (without a 6GHz spectrum), the console's wireless controller not only aborts the multi-link aggregation (likely by design to prevent jitter) but completely drops the network negotiation. This causes a total collapse of the DHCP exchange.

Instead of executing a graceful fallback to a Single-Link 5GHz 802.11be connection, the console connects at the physical layer but fails to obtain an IPv4 address, resulting in no internet access.

Technical Evidence (Router CLI Log Extract): Upon isolating the console's MAC address (D4:F7:D5:XX:XX:XX) and analyzing the AP logs during the connection attempt, the system throws the following critical errors:

[2541.291][host] 445 - ERROR: not find ipv4 client(D4:F7:D5:XX:XX:XX). [2610.255][host] 838 - ERROR: client(D4:F7:D5:XX:XX:XX) ip() active(1) lanType(1)

Impact: The PS5 Pro establishes a physical link (active(1)) but IP allocation remains empty (ip()). To restore connectivity, the entire Wi-Fi 7 network must be severely degraded to Wi-Fi 6 (802.11ax), or the MLO broadcast must be disabled entirely at the router level—which impacts all other modern clients on the network.

Requested Action: The Wi-Fi driver requires a proper fallback mechanism to accept 5GHz 802.11be Single-Link gracefully when 6GHz MLO is unavailable, without halting the DHCP process. Has anyone else replicated this specific DHCP drop on dual-band BE routers?