All Activity

If you don't have ALL devices connected to the R3 then they can take speed away from the router so that's a likely cause. Also splitting the WiFi bands and connecting directly to 5GHz would help.

I will pass it on to the team, if you could get wireshark logs that'd be really helpful as we don't have access to it. That would also mean it's unlikely to be properly supported until release when we can test it.

So these are the tests from my computer. Speedtest seems to be closer. On my phone that is connected to the gateway I get over 1000 mb over wifi though

Hello, Is there anyway that we can get deadlock added to the GeoFilter? I assume that it will be the same servers as CS2/DOTA2 as it's a valve game. If not, I can get Wireshark logs of the game as well. Thank you.

Ah okay thanks for posting an update/solution!

What do you get on speedtest.net? The in-built speedtest can be inaccurate at times. For the R3 to work most effectively ALL devices should be connected to it rather than the gateway. We'll need to update the Ping Heatmap via the cloud for the game, I'll let the team know, thanks for the report - it won't affect your ability to use the Geo-Filter.

No I don't unplug often and I don't use incog. I had to change the bookmark adddress and that seemed to fix it. Just an odd bug possibly thought I'd share

Also why can't I get a ping for some games?

Okay so that's good you're not being limited, you're getting your expected speeds it's just the in-built test displaying them incorrectly, this can occur due to the servers being used - they may be further away or some may be unavailable etc.

Yes I did enter the 1 GB speeds I pay for/expect, on my phone I get the full speeds it is connected to the gateway. I noticed my Ping average changed by +10ms so I tested the speeds to the duma I just have my pc wired to the duma and I have my other devices connected to the gateway from xfinity

bom dia no speedtest as velocidades sao de 1G dow e 520mb UP e no r3 250mb dow e 120mb up lembrando que antes da atualizaçao estava normal foi depois da atualizaçao que ficou assim me ajuda por favor

I don't really know how connecting the router could make the BT hub turn its WiFi back on, it doesn't make sense. Okay so you should be able to access the interface via 10.0.0.1 does that work?

Thanks for the report, we'll update it - it won't affect your ability to use the Geo-Filter though

I've given you Early Access which has the latest firmware there https://forum.netduma.com/forum/144-netduma-r2-early-access/ Reboot the router and then upgrade and it should work

HELLO PING does not appear in the listJ PING HEATMAP FC27 PLZ FIX I have updated to the latest version of the software and the DUMA OS app.

The bt hub was connected to the box coming into the house as normal and then the xr was hooked up via an ethernet port from the bt box to the to the internet port so i could run multiple ethernet ports from the xr, i have done it this way in the past with sky, virgin, bt and always in the past just turned off the wifi on the other router and used it as a modem but the problem i think is because the bt smart hub 3 cannot be used in modem mode and even if you try and shut off the wifi and everything as soon as it detects the xr it turns everything back on, when i reset the xr it did say it was assining an ip which would not cause problems with the ip but obviously something was still going a bit strange.

Hi guys, fairly new here and kinda useless with all this router stuff so please bear with me. My R2 has a habit of disconnecting from the internet, and I realised my firmware is well out of date. However when I try and update to the latest firmware, I just get the usual buffering icon and thats it. I have included the file I believe is the latest update. Any help or advice appreciated. DumaOS-R2-3.3.280.sig

Ok, Thanks for helping me out this far for the issue T'm having.

Okay so it looks like you do have a CG-NAT which could be the reason Ping Optimizer isn't always working, there isn't anything we can do about that unfortunately

1 4 ms <1 ms 3 ms *b*n***.*** [*.*.*.*] 2 * * * Request timed out. 3 12 ms 5 ms 3 ms *.*.*.* 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. This is what I'm getting from the link you provided, I just removed my ip address from the results.

That shouldn't affect your ability to access its interface though - when you were trying to access the XR were you connected to the XR directly via WiFi or ethernet or were you connected to the BT hub still? If the latter then it makes sense and you wouldn't be able to. You could give the XR a static/reserved IP on the BT hub which could help and then put it in the DMZ.

Have you entered the speeds you paid for/expect? Where are you testing the speeds exactly? Are ALL devices connected to the R3 or do you still have some connected to the gateway?

As above CG-NAT could affect it, you can see if you have that by following this guide: https://support.netduma.com/docs/dumaos-3/open-nat/#cg-nat

I think that's more of a question for EE, I would have thought they would have done testing to ensure the different types of products they have work well together. Disable AWP, does optimiser then appear to give you more options? Also disable optimiser then re-enable it to see if that works.