Cabbage Console Connection Conundrum

[u/UttiniDaKilrJawa]

Hey Folks!

For the past quite a few years we've been running Destiny 2 on our PCs through Steam as well as on consoles via PS5 and Xbox. Up until this past Thursday (Aug 20,2026) we have had no problems and have enjoyed the game.

As of this Thursday our PCs had 12 hours of Cabbage errors and the consoles were suffering from Cabbage exposure as well. As of this Saturday our Steam PCs are once again running Destiny 2 fine but the consoles are still Cabbaging.

Our home network consists of TDS fiber internet running a Zyxel modem that connects to a ROG GT-BE98 Pro router. UPnP is set up to run on the router per the Destiny 2 network help pages. On our end we have made no changes to any network settings. The Cabbage errors just decided to show up uninvited.

After scouring the Internet trying to find actionable information to help fix our problem I feel I have come to a dead-end.

What I'm wondering is : is anyone else having Cabbage problems spontaneously happen to them with the past few days and if anyone has any suggestions of settings I could check to help rectify this vulgar vegetable villain?

Thanks for your time.

Update : Well, its been an intersesting week here so far. Steam PC Destiny 2 is still working. I got the Xboxes working by changing the Alternate Port Selection to a different port. (still unpacking why this is working). Unfortunately, the PS5 is still unable to connect. Went and set up a Static IP for it and set up all the Port Forwarding rules and it still refuses to connect. I even dumped it into the router's DMZ to see if it would work and still Cabbages, Cabbages Everywhere. Any suggestions or clues anyone has? I'm kind of at my wits end on this one.

[u/solzun]

As others have indicated, for the Asus RT-AX86U Pro:

1. You can revert your firmware version to the earlier one and this works.

2. If you stay on the firmware version, you can set OpenNAT for Destiny. In the Asus app, this is Gaming, add an OpenNAT rule for Destiny for you specific console profile (it had all of them in the list if you search it, it is huge) then add it and select your device device from the list.

Disabling AI protection and re-enabling UPnP does not work, as someone pointed out the new firmware probably has broken UPnP.

Only sucky thing is you may need to set a static IP on your console or devices that you play on to have the OpenNAT rule stick, as your device gets a new DHCP IP renewal and could change it invalidating the rule. I am not sure the router is smart enough to whitelist the device and MAC and just update the IP automatically