Netduma Fraser

Follow these steps exactly: 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 R3 (found in Settings > WAN) and enter it into the DMZ function on the ISP modem/router. Disable IPv6 in LAN/WAN on the R3 and enable remote support in Settings > Troubleshooting. Then post back here from a device connected to the R3 when you've done that and we'll attempt to connect. I can see you're still using IPv6 currently which means you haven't follow those instructions properly yet.

That is just so we can get a dev to remote in next week to look at the issue. Making those changes themselves won't fix the issue. Also I can see you still have IPv6 enabled.

That doesn't make any sense really, even in your above screenshot all those servers were allowed in your radius - what firmware version are you on with the R1? If you disable Congestion Control/QoS fully does it continue?

Added but it has been temporarily removed

That would absolutely affect your bufferbloat results, you had settings that worked for 1/10th of the speeds you have now so they won't work the same now, you'll need to fine other values that work for the new speeds you have. This could be a lower % value or higher. The router doesn't just go 'bad' and your own conclusion on the cause isn't a valid reason for an exchange, that's my job to determine what the cause of a problem is and to respond accordingly. If we allowed everyone to determine their router was faulty themselves, the amount of returns we'd receive because settings just needed to be changed would be crazy.

Thanks for the logs, I'll pass them onto the team. Re-upgrade back to the latest Early Access version, then 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 R3 (found in Settings > WAN) and enter it into the DMZ function on the ISP modem/router. Disable IPv6 in LAN/WAN on the R3 and enable remote support in Settings > Troubleshooting. Then post back here from a device connected to the R3 when you've done that and I'll see if I can get a dev to connect and have a look at what is going on next week.

If you haven't changed anything then also nothing on the router has changed so that would indicate either your internet usage has increased/decreased which would effect the results or something on the line from your ISP has changed. Either way if you fine tune Congestion Control it should be better. Also just to be safe, 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 We wouldn't provide an exchange or a refund for this because it's a common query that just needs changes to be made and isn't indicative of a fault at all.

I wasn't able to reproduce the issue but delete all the rules then reboot, then add them again, does it work then?

No there isn't a way to do that unfortunately. It has been requested before but it would require two separate firmware versions, one with them off and one with them on, can't be a toggle option apparently

You should be able to still get access as the interface doesn't require internet, if you still can't though, try going to 192.168.1.1/adv_index.htm or 10.0.0.1/adv_index.htm or whatever other LAN IP you're using followed by /adv_index.htm and see if you can grab the logs from the settings there when it next happens

Disable Geo-Latency in the R3 settings and check again please

That's expected behavior, you won't get an Open NAT using a VPN

Okay lets try the first firmware, same process as above please https://drive.google.com/file/d/11j913tnodzS5TKASdxtKpBI4KQ_no1ec/view

Not being added to the router wouldn't cause high ping or lag - what ping are you seeing through the router? How do you have Congestion Control/SmartBOOST set? 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

Please reboot the router from the interface and then see if you can re-add the rule again

If you've updated the router then settings that worked previously may need to be changed, you'll just need to fine tune it again and it will be fine

That's good to hear, let us know how you get on, hopefully it won't happen again

Did you reboot after the issue before getting the logs? If so you have to get it before the reboot, there isn't anything there

Added

You can't update it with anything other than the official XR700 firmware, you're on the latest update and DumaOS 4 won't be coming to the XR range.

Try this one, then factory reset, if the RGB comes back then re-upgrade again DumaOS-R3-4.0.219.sig

Is that the public .134 version or the beta one? Should say RC14 in the version name top right of the interface

Disable Geo-Latency, reboot the game device then try again please

You've not really explained your issue at all, if it's your bufferbloat results then you just need to fine tune your Congestion Control settings to find what works best

Downgrade back to one of the first firmware versions, can you get it to show then?