Netduma Fraser

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

Just do a speedtest.net test just for speeds, what do you get? Is 600/20 the speeds you have set in the router? Also if you have speedtest bypass enabled that may impact your bufferbloat results. Are you testing the speeds of WiFi or ethernet?

Delete the file from your PC and then re-download it please and then try again

You have R3 Early Access, please try that one as it should be more reliable https://forum.netduma.com/forum/151-netduma-r3-early-access/

That would be great but it's unlikely they'll be any more feature updates made. Are you leaving the VPN constantly? If so that could be why. Otherwise you mentioned configs, are you loading configs that were saved on previous firmware versions?

Oh I see, that's fine, it won't always do that, do you still see servers in your radius when playing warzone? Looks like you are from the above?

Take your PC out of the DMZ, that is a major security issue, it may also be contributing to the issue. If it happens again please grab the log and I can take a look.

The above would be the only counter really and I doubt there is anything further we could do on that as it would basically be that exact option

Set your ISP modem to ensure all traffic flows to the R3 either with the R3 in its DMZ, modem or bridge mode. You shouldn't then need to do anything on the R3 to get an Open NAT.

If the issue is on the ISP side then it won't be able to help, if it's on your side then it can help. It's hard to give you a recommendation as I can't be sure of the root cause of your issues. I'd suggest checking the return policy and if you're fine with that: https://netduma.com/terms (we do provide a US address for US returns) then give it a go.

Great thanks, I've pass it onto Alex to have a look at