Netduma Fraser

Buying second hand is always a risk, it's likely they were having issues which is why they sold it in the first place, I'd suggest you return it to them utilizing the return policy on the applicable marketplace. It's almost impossible for me to give you a reason for an issue occurring when I have no idea what kind of state it was in initially even if it seemed to be working fine. As per your other topic there isn't any specific recovery procedures and we're waiting on a developer to remotely upgrade you. It's not bricked as you are able to access the interface to get logs but it does appear you have an unfixable kernel error that even if you get better access to the router features will still likely cause you issues so I would highly suggest you return it.

Added https://forum.netduma.com/forum/144-netduma-r2-early-access/

The R2 was our first foray into our own hardware and we've learnt a lot since then hence the R3 is a lot more robust. You are also on an Early Access version so there can be issues as you've seen. I will come back to you once I know more.

If you haven't already do a factory reset on that version, it's quite a big jump. We're aware Ping Optimizer isn't 100% reliable currently. It can work you just may need to try again later. In the meantime you can adjust Congestion Control manually to achieve the same effect which can be found in Ping Optimizer > Advanced.

Yes you'd put 0. The ISP timeout must be set to 5 then, if they're otherwise unhelpful perhaps they could change the timeout for you just to see if the issue improves

On your ISP router set a static/reserved IP for the R3 then on the R3 in Settings > DHCP > Add Rules > Select Device > Save. Do that each device you're noticing the disconnects/issues with. Then in DHCP > Advanced change the lease time to 10000, save, reboot the router from the interface and see if it happens again please.

Good to hear you got it sorted, it was just a security update so it should have no effect on use whatsoever

They're blaming it on a 3rd party router and when replacing the bridge device it seems to work so I think it if is that device then if possible I would directly connect your PC to the bridge device for awhile and see if the same issue happens. If it does then it's definitely the bridge device and they can't blame the router, hopefully they'd then do the right thing. If not then it's more likely the bridge device and XR don't play well together, in which case you may not want to but the Dasan may be the best setup to use - if you're using the XR for WiFi then perhaps you can remove the Dasan antennae for better aesthetics. On the Internet Setup page on the XR for the timeout option update this to whatever the maximum value it will allow you to enter is, apply, reboot the router from the interface and then see if it works better overall after that. How do you usually resolve the issue if the connection doesn't restore itself?

You have Early Access so you should use this firmware which is more up to date https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/

No that's not possible and internet isn't required to access the interface. Use the IP address 192.168.1.1 or 192.168.1.1/adv_index.htm to reinstall the firmware or 10.0.0.1 if that's the IP

Impossible to say just based off the information you've given but it looks like you're on an outdated version of the cloud, the cloud is out of date anyway so we'll need to update that but regardless we don't know where you're from. If you're in Europe then it's more understandable, if you had local congestion at the time its understandable etc.

Good to hear, thanks for the update!

I've not heard anything back yet, as soon as I know I'll let you know

It won't show you the game server you're connected to until you actually start searching/get into a match. Also you have filtering disabled so it's not using trying to get you games in any of the areas you've selected

They weren't able to on Friday and aren't available at the weekend, they'll try again today and will see if there is an alternative if they're unable to.

NAT is not something the Geo-Filter can cause being open or moderate. You either have an Open NAT or you don't. You do have an Open NAT. The Geo-Filter blocks the server to test your NAT - it's not causing a moderate NAT. The test because it is unable to reach the server defaults to showing moderate. When it is able to reach the server i.e. with the Geo-Filter disabled then it is able to show you Open. This does not mean you only have an Open NAT with the Geo-Filter disabled and Moderate with it enabled. The NAT is open in both scenarios, it is just the reporting that is different. @Krush can you translate what I'm saying please?

As above look for anything blocked with the map fully zoomed out to find the server responsible and allow it. However, you do not need to do this, it is not making your NAT moderate it is simply blocking the server its using to test NAT and because it can't be reached it's defaulting to reporting moderate but you're still open regardless if the Geo-Filter is enabled or disabled.

I assume you mean the router interface? What do you see when trying to access 192.168.77.1 or http://dumaos in your web browser? When did the issue start?

You shouldn't have any trouble with getting an Open NAT with how you have it set - if you disable the Geo-Filter then launch the game is it open? If so then you can ignore the reading going forward as you're actually open. Otherwise, have you ever been able to get an Open NAT through the XR?

Yeah it is a shame, perhaps you'd have more luck forcing EU servers

Not exactly no, the devs will just do it when they have a spare moment, you also don't need to be present for them to connect. As long as you've made yourself accessible how I mentioned they will keep trying.

There will be quite a few servers in that Irish location so you may need to do it a few times before you can properly filter. They may also have a ping limit in place that will prevent you from connecting to a server that far away - they did this in an update to Ricochet Anti-Cheat in BO6 so unless they've removed it then its likely still present in BO7.

Port forward 3074 for one device and 3075 for the other and then you should be able to get an Open NAT at the same time.

The latest public version of the firmware has the DumaOS version from the beta in so you don't specifically need the beta firmware. Just make sure to update to the latest public version.

Great to hear that, thanks for the update!