Netduma Fraser

I'd recommend using VM in router mode with the XR in its DMZ, that's what I always did and found it to be more stable. By don't have WiFi do you mean it doesn't appear in WiFi lists or you can connect but no internet?

It's not a wide spread issue so it will be down to something in your setup, are you using automatic or manual network settings on the console? Have you set an alternative port for it to use? Do you leave it in an instant on/standby state all the time? There aren't any IPv6 DNS options currently.

Direct to the modem what speed are you getting again, half? What settings did you change on the router prior to it happening? What IP did you put in the DMZ exactly?

Go to routerlogin.net/adv_index.htm this should load NG settings without DumaOS, from there go to Advanced WiFi Settings, disable WiFi, apply, reboot from the interface, wait 2 minutes, re-access using the same link, enable WiFi, apply, reboot from the interface and wait 2 minutes. Then see whether it loads correctly using the normal URL and if the WiFi now starts appearing.

You can either do so by allowing the router to do it from Settings > Firmware Update or by download the firmware from support.netgear.com and uploading it to the router in the same place

Modem mode can be finicky in my experience, however, once you've put it in modem mode reboot the XR and wait 2 minutes, then it should get internet

Don't do a 30/30/30 update, it can damage the router so isn't recommended, also a 7 second reset won't be resetting it, it will just be rebooting. Reinstall the latest firmware using TFTP, wait 5 minutes once you've done that, hold the reset button for 30 seconds, release, wait 2 minutes then attempt access.

Hey, welcome to the forum! Approved!

No it wouldn't at all, the servers are still all able to be connected to via the Geo-Filter

Hello, welcome to the forum! Nothing you need to do, they just update the servers often so Heatmap can get out of date, we'll push another update on Monday for it.

So the Geo-Filter shows your ping direct to the server. Games have processing delay, not all games choose to include this in their ping calculation but CoD does which is why it will be higher, as you mentioned the ping seems about right in both cases. As for the latency bar I couldn't say how that is being calculated. We're still improving the results from the tests on the router, it uses a speedtest you probably haven't used before and it's possible that it isn't selecting the closest server.

No there isn't, NG don't generally do betas, we did push for 3.0 to go into beta but this time around we're quite confident once the remaining issues are sorted that it can go out without a beta - if we think a beta is helpful we will push for it.

I think it's one you'll need to have a look around for, doesn't seem to be connection related, someone else said reinstalling the game worked

Seems ridiculous to me but looking at the error online, quite a few people on reddit said that fixed it for them - it seems there are quite a few bugs in this iteration, I've seen DMZ has quite a lot

We're still improving auto detect, it uses different servers so if it reports lower than what you expect then set it manually. If you're not receiving speeds without the router you'll have to resolve that first, connecting the R2 won't have caused that to happen on the modem

Interesting, glad it's all resolved now, do keep us posted if it happens again

You haven't set your correct speeds first of all, set your bandwidth speeds to what you expect, then it should increase

For router MAC address select Use Default Address, apply, reboot from the interface, wait 2 minutes then delete the device and see if it reappears. Given it's just the router though it won't cause you any problems and isn't a risk

What is the model of the ISP modem/router? Are ALL devices connected to the R2? Can you provide a screenshot of your QoS page please?

Yes please if you could, it’s important to do so before a reboot otherwise it will be lost

Having a look apparently changing your Activision ID fixes the error, no idea why but worth a try!

Approved!

Very strange, probably the easiest way is to make a whitelist for any NowTV URLs as that will work across the whole feature, then it should work

Could you provide a screenshot of a completed Connection Benchmark test please?

I believe it does work still if you've given reserved IPs on the router first then disable DHCP, those devices still get a connection but I totally understand why you'd want to wait.