Netduma Liam

For those wondering about DPI, as long as you have an R2 and you're on version 3.2.453 or newer, just resync your cloud manually from the three-line menu in Device Manager and you'll get the new DPI update. Give it a test and let us know how it goes!

The logs look as those they're cut short, there's no sign the router rebooted that I can see. Can you try going to Settings -> Monitoring -> Logs and see if they show any more information around the time of the disconnection there? Have you still got your IP reservations set as we mentioned earlier in the topic?

They seem to be quite unstable at the minute, I've got my setup pretty dialed-in at home and I still see ping fluctuations in Warzone specifically, it's just the servers for the most part I believe. We can still take a look and make sure it's not you though, can you send over screenshots of how you've got QoS setup? Also if you're still having trouble with Geo-filter, let us know!

OK, thanks. Given that your service has changed, it's advised that you now factory reset the R2 and set it up fresh with the new speeds. You should then see that it's detecting much closer to what you expect. If it still isn't, can you let us know whether your ISP requires you to use PPPoE, DHCP identifiers or VLAN tags?

As you say, it's something that will void your warranty. Even if your R2 suffers a hardware failure, we always do our best to ensure we can assist and are often able to provide replacements in these circumstances. However, opening up the R2 and doing this will prevent us from being able to do that for you. The team are aware of the maximum temperature before performance will be degraded for the R2, and it's operating temperature is well within that. Making a cooling modification like this will have a negligible impact on performance and has a lot of risk associated with it. Of course, you can use those fans and place them under the R2 with a gap between the fan and R2. As long as you're sensible with it I don't see a risk there. I'd advise against opening up the R2 though, the positioning of the chips will make it difficult to add a heatsink like the ones you've screenshotted and there's a lot of risk of damage.

We have actually heard of similar behaviour before, not with the R2 mind, but with some of the NETGEAR range. It is something I'd imagine will flush and fix itself over time, but it sure is disruptive when the problem is there. I'm afraid there isn't really anywhere in the front-end to view the routing table/specific DNS info. While we debug this, can you please disable filtering mode on any devices you've added to Geo-filter and also disable QoS from the sub-menu in Congestion Control. Could you disable IPv6 just on the LAN side not WAN, then check if you've still got internet access? Are the requests to discord still failing in this configuration?

In depends what you're doing to replicate the message, can you recall any specific actions that replicate this behaviour?

Out of interest, could you please try disabling IPv6 completely from the LAN and WAN settings in Network Settings, then try again?

Welcome to the forum! Yes, it's up to date. Resync cloud from Ping Heatmap and you'll see them again.

Welcome to the forum! Thanks for all the info, that's really helpful. The first issue is probably a product of the second I would think, so let's try to get you full internet access first. Could you try going to Network Settings -> WAN -> Network and un-toggle 'Use upstream DNS'. Then, toggle Override DNS and set the primary to be 1.1.1.1 and the secondary to be 8.8.8.8. If you prefer different DNS from cloudflare or Google, that's fine, use those. After that, you may need to reboot the R2, but check if you then have full internet access again. On your last question, if your ISP doesn't require you to use a DHCP identifier, which it sounds like they don't, then you don't need to worry about this option!

Have you updated your speeds in QoS -> Congestion control Sub-menu -> Set Bandwidth speeds? If you run a Connection Benchmark test, what results do you see? If you run a third-party speed-test, such as speedtest.net, are the results also the same?

OK thanks, what firmware version is it running? What's the exact problem you're having?

If you go ahead and resync cloud from the submenu in Device Manager, you should have the first new DPI release now. We're going to be continually updating it moving forward too so it'll continue to get better. Let us know how it feels!

We've just updated them again, if you resync cloud from Ping Heatmap, you should start seeing them again.

Correct, we're still working on it alongside the rest of our DPI work. A developer has made some changes and we're testing them currently. We're not sure yet whether we can resolve this purely with a cloud update, it may have to be part of a new firmware.

Do you have any issues if you connect the PC to the modem via an ethernet cable? If so, the problem does appear to be the PC.

Ah OK, so it's purely an ONT. Do you connect the XR direct to that? There's no other gateway?

Good advice above. Can you also send over a screenshot of your Geo-filter settings currently?

Yes, that will be in there too as far as I'm aware!

OK that's interesting, can you possibly provide a screenshot of the PPPoE Passthrough page? We may be able to work out together if/how we can configure that for you.

DMZ is typically the best solution as it essentially sends all traffic straight to the R2, it's unlikely this would cause any issues, though you could experiment with using bridge/modem mode if your ISP supports it. Does your ISP require you to use PPPoE in order to get connected to the internet? Did you have to fill in some PPPoE credentials in the R2s WAN settings when you first set it up? If not, I don't think PPPoE passthrough would be relevant here. What indication did you get that suggested double NAT might be the issue? DMZ should resolve any NAT issues you experience, so i'd be a little surprised if you were still having that issue.

Is everything still OK on other devices that connect via ethernet, it's just the PC that's having problems right?

Ah OK yeah a log might be helpful if you can grab one. Could you also please try going to the DumaOS interface -> Settings -> Setup -> LAN Setup and set the minimum DHCP value to .100. After that, reserve an IP address for each device on the network. Make sure you give them IPs from .2 to .99. See if you're still having disconnections after that.

We've been testing the bug fixes since the last test internally to verify they're going to work before getting another build. It's all looking good so we're now waiting on the next build from NETGEAR. Once we're happy with this one we'll go ahead and release it here and on the NG forums as a sort of 'beta' firmware so it doesn't have to wait on NG testing. There's been some issues with the XR1000 which I need to catch up with the team on later, I'll update the firmware progress article once we've discussed that.

Il tuo ISP ti ha detto che dovevi impostare queste credenziali in DumaOS? Penserei che se hanno impostato l'IP statico per te, puoi lasciare l'R2 impostato sulla modalità DHCP e il suo IP può essere gestito dal tuo gateway.