Netduma Fraser

That's brilliant to hear, thanks for the update! You're welcome, all good here, hope you're good too!

Okay great, keep us posted!

That's fair enough!

Skip that part and continue the wizard, once complete you should be able to enter it in settings to get a connection. We're testing an update already that fixes that

Might be that the Smart Hub is required by your ISP or that you need other details to connect which you may not have. Connect back the hub then connect the R3 to that and restart the setup

You can do it either way really but try replacing the smart hub first so you connect the R3 direct to the modem

Unfortunately not as Netgear are a completely different company. Not sure to be honest but we'd be happy to have you as part of our community! Of course any issues/questions you have going forward don't hesitate to ask!

Hey, welcome to the forum! I would say so, of course I am a little biased but with DumaOS 4 we've introduced new features to improve your ping so if that is your biggest problem then it does have that advantage over the 1000.

Unplug it from power for a few days then try accessing again, that can bring them back to life sometimes

Have you changed your DHCP lease time at all? Does anything appear to trigger the disconnect at all? e.g. changing a setting, specific network usage etc

We did have trouble with some people not getting the confirmation emails so likely the same issue here. As long as you have the DHL email to track you're all good. Alternatively if you want to make sure you can email us and we can check the tracking matches the one you received. That's annoying but it's likely just clearing customs and shouldn't take too long

You could do the TFTP method to reinstall it completely, otherwise multiple factory resets should recover it, just takes the one!

Thank you for the log, I'm having the team look through that, in the meantime could you have a device connected directly via ethernet to the R3 so we can see if its specifically another router/switch that disconnect?

Yes it should do

You will get one not to worry. There is no easy way to tell how many orders we may get done in a day and what dates that might cover. Likely to ship by the end of this week. That may have gone to spam, double check there

You're welcome! Where are you measuring the bufferbloat exactly, using Connection Benchmark? What is the base stability of your upload like?

You need to upload the file on the router interface, not open the file on the PC

What web browser/device are you using to add the device/change CC slider changes? You may need to do a hard refresh on the web browser but it will appear under the Congestion Control mode options. You're welcome, thank you for giving us your time! Okay if you don't mind for the speed test/ping optimizer lets wait for the new version so you can run it directly to the ONT with PPPoE

In DHCP settings disable the option for it to run as a DHCP server, then add addresses for each device - a number between .2 and 253

Responded to your topic

No worries, thanks for trying, got some late minute feedback that re-installing it worked for the R3 so wondered if it would do the same here. No worries, we have reproduced the issue and will be fixing. You could reupgrade the 500 using routerlogin.net/adv_index.htm and it should work after that

Not sure on how you set them up exactly but what you suggested there would work. R3 LAN > Orbi WAN

Due to circumstances outside of our control we've been waiting for a build for a long time. The release will not be an official NG release and therefore will not go through their testing process which means we need to ensure it's of a high enough quality ourselves for a release (i.e. testing what they would have tested), it won't be much longer.

We don't have a beta to provide it at the moment, also with launch we don't want to start mixing up versions. It won't be long before it is available. Yes PPPoE & QoS will work together now.

I've just checked this for you and it is going to the correct address from the order. I think what you're looking at is the destination service area - so basically the DHL hub in closest proximity to you that's where it is aiming to get to first and then it will show as out for delivery sometime after that.