Netduma Fraser

If you're having an issue make a new topic and we can help you there

It has AX WiFi but other than that not really, I wouldn't say it's worth the upgrade at the moment as the XR range won't be receiving any new feature updates

You'd have to test the speed with the PS out of the DMZ first. What Tray means is that NAT Type 1 you can only achieve by connecting the PS directly to the modem, NAT Type 2 is for modem > router > PS but its still open

It won't have the same issues once ported and will be a lot easier for us to make changes and make it more powerful

Thanks, so looks like it pinged the first IP which was correct and then got put onto pinging the latter for some reason, it might be relaying you to that other server. Add it to your denied list and see if you get anymore like that

I'll let Alex know, thanks!

Good to hear, thanks for the update!

Okay thank you, will let Alex know

They're both essentially the same, they had to replace the CPU I think due to supply chain issues but functionally no different

Disable SmartBOOST fully from the icon > Settings on the page then test, what do you get?

Glad to hear it's working now, the next firmware is a beefy one so will be all around more stable

We haven't had many comments on the R2 beta for awhile - likely waiting for DumaOS 4

DMZ option is definitely the easiest way! In the next version we have improvements to UPnP which should help

If you could grab the logs from the System Information page when it happens please I can take a look and see what the issue may be

If you open command prompt on your PC and paste tracert 34.154.57.115 what ping do you get to it? Then what do you get if you do this: tracert 115.57.154.34

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

Most people purchase the router specifically for the features which they wouldn't be able to use in AP mode. Now we have the R3 we are considering adding an AP mode to the R2 so that those that have both can use them more easily together, it would be a ways off though.

Glad you got it sorted, thanks for the suggestion!

People can disable it from the settings pretty easily. We think we've fixed the issue now!

We have a firmware being tested internally currently so shouldn't be much longer now. Here is a rough change log so you can get an idea of what it includes. As you can see it's quite a beefy update, hence why it took longer than the previous ones. Addition of Hybrid VPN Improved SmartBOOST performance Various frontend improvements Fix for memory leak (sometimes manifesting as being unable to access the interface) Potential fix for "frequent disconnects" issue Chromecast and local transfers fixed (this is the WiFi bug where devices can't communicate with each other when they're connected to the same WiFi band e.g. 2.4/2.4GHz) Fix for "No Internet Detected" bug in Setup Wizard IPv6 PPPoE now works with SmartBOOST Ping Optimizer reliability improvements UPnP Improvements Before you ask, no I cannot provide this to you before it's deemed to be stable so please don't ask as you'll get a disappointing answer! When ready we will release it, please don't ask for an ETA!

It's not possible unfortunately. The interface is only able to be accessed locally unless you enable the remote management option so it isn't necessary really like mentioned above.

The power won't flash but the others will. Do this instead and then you can gain access to the router: Set a static IP on the PC with the following details IP address: 192.168.77.100 Subnet Mask: 255.255.255.0 Default gateway: 192.168.77.1 DNS: 192.168.77.1 If you're not sure how to do this, you can check this guide: https://kb.netgear.com/27476/How-do-I-set-a-static-IP-address-in-Windows then try accessing 192.168.77.1 please and see if it works.

Factory reset after the upgrade is the correct way to do it to prevent any issues caused by remnants of the previous version. Shouldn't be long now for a new firmware.

You should still get an Open NAT, if you hard reboot the console, or you can port forward but yes in the next version we have made improvements to UPnP

I'll check it with Alex on this, I think we have a bit of a delay on cloud things as we're having to do it manually at the moment