Netduma Fraser

That's what you should do so you're doing it correctly. In some games what you're doing can work, the game just forces a server the lobby host can connect to, in some however it doesn't work that way and sounds like what may be happening here. In this occasion I think the only thing to do would be to have them also use a DumaOS router to force the same area as you. Geo-Latency could work in this scenario but I couldn't guarantee it and that's only available on the R3 and will be on the R2 (w/a future Early Access firmware).

All you need to do on the Asus is enter the R3 into it's DMZ then forget about any other settings on the Asus, this should open the NAT for you. If it doesn't you can then put your PlayStation in the DMZ on the R3. Are you having trouble locating the DMZ on both routers or struggling to activate them? The team can look into VLAN yes but have you tried the latest Early Access firmware? Some changes there may improve your experience. Congestion Control wouldn't be as needed in this situation so you could disable it if you want to but still generally a good idea to keep it enabled. Do you see anything blocked on the map when you get kicked from the game? Does the game have a server/host migration feature? Ping Assist is a method of filtering servers - is this what you're referring to? Looks like you may be referring to Steady Ping and it not being able to stabilize the ping when it can't ping the server? As you mentioned it can't ping every server unfortunately but in some cases it can still stabilize the ping when the server doesn't show a ping reading. Ignore MTU it will not make any difference.

I suspect you're making a direct connection to them in which case the details are unlikely to be correct (this could be abused if they were), looks like you've added it to your allow list which is good. In this scenario it'll be SmartBOOST/Congestion Control that will help the most, how do you have them set?

I'd be surprised if it was defective but do try the new firmware. Does the Eero see the R3 connected if you check that interface?

What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g. R3 in its DMZ, modem/bridge mode

Good to hear, thanks for the update!

Added

Added

I will chase him, I know there is a big cloud update being worked on

Are you on the latest Early Access firmware?

Are you able to access the interface? On the WAN Settings page does it show as connected/getting internet? Does your modem see the R3 as an attached device.

What features are they exactly? Hold the reset button in the back of the router for 30 seconds, then wait 4 minutes before accessing the interface and it'll then take you through the Setup Wizard.

Added you both https://forum.netduma.com/forum/151-netduma-r3-early-access/

Added https://forum.netduma.com/forum/151-netduma-r3-early-access/

Reboot the modem, wait 4 minutes then reboot the R3, wait 4 minutes, do you get internet then?

I think you mean Auto Ping vs Ping - Auto Ping gives you those extra stats, manually pinging doesn't. Ping Assist is a way of filtering and doesn't determine what stats appear. The higher the tick rate the better but it's not something you can control.

You need to wait at least 2 minutes for the connection to be fully severed - even better, restart the game - otherwise it can still be connected to next time you search.

Presumably it's actually unable to ping the server properly but we'll get those moved, in the meantime block them

Can you provide a screenshot of the whole Geo-Filter page showing what you see when that happens please?

I get that but we've identified just using long cables can cause it, regardless of what it is connected to/causes to disconnect

Could you try without that long cable and just use the Xbox on WiFi for the a few days and see if it stays online when it would have usually disconnected?

We might need to reclassify the game, prioritize the PC as a device instead of using activities.

Yes please, we are looking into the issue as a priority. We have identified a few potential causes, do any of these apply to you: Use of a network switch Use of very long ethernet cables Initiating a large download prior to the disconnect

Could you try the firmware here please? https://forum.netduma.com/topic/56332-r3-disconnections/?do=findComment&comment=420716 it doesn't seem to have fixed it for people but it may work better for you

All you need to do is put the R3 in the DMZ on the Asus - you don't need to change any other settings regarding this for NAT. If you disable SmartBOOST fully that will disable Congestion Control fully, 100% is also disabled. Use the mode Always and see if it works better.