Netduma Fraser

Could you do a factory reset please then do your normal things and try to connect it and then provide the log please, that should tell me what the issue is

The ports are gigabit so you'll never see that .3 using the router, 950Mbps would be the max after the routing yes. Did you do the guide I mentioned previously? I think you might be worried about the wrong thing, bufferbloat occurs when your network is saturated i.e. all available bandwidth is being used - unless you're running downloads every time you play it's very unlikely your connection is saturated. Also, using Congestion Control prevents the connection being saturated.

If you're done using the VPN and you leave it enabled yes, presumably you're not using those devices while sleeping and so the VPN wouldn't be required? It's possible that a timeout is being triggered that is causing it which then isn't handled very well preventing it from working again. A reboot should resolve it though, I don't think you'll need to go through that upgrade process each time. Try it, next time you're done using it disable it, then in the morning when you need it again enable it, does it work then?

Those rules are unnecessary, you're allowing traffic all the time but it's always allowed anyway so it's probably overloaded the amount it can record. Do not use those rules and see if Adblock works please

There will be a reason for it - are you doing the tests during peak and non peak times for example with peak times being slower? Are more devices being used at the time or a download happening when it's slower?

Are you leaving the devices in an instant on/standby mode? If so, shut them down fully and see if the problem persists the next time. Are you using manual network settings on the console itself? Have you made any specific settings changes towards these devices on the router?

It may not be able to detect at the time the specific game but it can tell it is gaming so will still be prioritizing

Possibly, if the lease on that is renewing it could potentially provide the same effect - reboot the hub first, wait 2 minutes, then reboot the router at a similar time and see if it continues

It may take around 30 seconds if you leave it to get internet - does that happen?

Glad to hear it's working now - it won't be able to stabilize or ping every server/game but we're working on a new ping method that may improve that

Are the devices all directly connected to the router or are they connected via switches, extenders etc? Once you've renamed them all once you don't need to do it again. Then it won't be a rule to the correct device - if you're connected devices via 2.4/5GHz or ethernet i.e. you've connected them via different methods then they will have different MAC addresses. So you may have reserved an IP for the 2.4GHz connection for that device but not the ethernet connection if that makes sense. If you do #2 correctly then you can disable DHCP and it will work. Any new devices you would need to set a reserved/static IP on the device itself first to connect to the router then you can make the rule on the router. It's not a problem, it's a normal background process. By reset do you mean a reboot or a factory reset as there is a big difference. There isn't and is very unlikely to be a schedule reboot option for it, no new firmware. I don't think it's necessary in this case to use TFTP.

You definitely wouldn't get an Open NAT using the DMZ - you'd have to do 3074 for one device, 3075 for another, 3076 for the other. Can you provide the config you're using for the VPN please? The log is in Settings > Troubleshooting.

Open it in an incognito window and see if you can continue, if not try another browser, otherwise download the DumaOS app on your phone and try to continue that way

It is actively avoiding you getting that server then - do you ever get it without the Geo-Filter & VPN or direct to your ISP modem?

There isn't a way to do that with the router, it doesn't read your traffic, you'd need an alternate solution for that purpose

Sorry I'm not sure I follow, can you clarify please?

It could be that your ping with the VPN would cause it to be much higher on the other servers so it essentially forces you on to Dallas. Try it again with Geo-Latency and have your radius only cover Dallas.

How are you determining you're on the Dallas server in that instance? It'll be the game deciding where to put you - unless your routing to the Dallas server is so bad it automatically won't connect you to it but that's unlikely

Ping Heatmap isn't showing is currently on any game, that's an issue we're aware of but assuming the game still has it you can connect to it. Filtering for Fortnite though is quite difficult, you would need to use Geo-Latency really to avoid being kicked frequently but it won't be full proof just due to the way they handle matchmaking.

If your ISP modem/router has WiFi, set it up so that it is in bridge or modem mode, you can also use the DMZ. Copy the WAN IP from the R2 (found on the System Information page) and enter it into the DMZ function on the ISP modem/router. Disable IPv6 in LAN/WAN on the R2 and enable remote support in Settings. Then post back here from a device connected to the R2 when you've done that and we'll attempt to connect to force through an upgrade. Depending on when you do this is might have to be tomorrow but you don't have to be around or do anything other than what I've mentioned for us to do it.

It would be worth doing a factory reset on that version, depending on your previous version a lot will have changed

Reboot the router, the try again please, if that doesn't work then do the same but with a factory reset

As above, gaming barely uses any bandwidth, if it's showing then it's likely to be prioritizing the game

That is the latest, I'll check in and see if there were any issues with the cloud and if another can be put out

Just to clarify, you said you have a port forwarding rule on your modem? You don't need that and could be causing conflicts, the R3 should be in the DMZ on your modem and then no port forwarding rules on the modem - then see if you have the issue through the R3