Netduma Fraser

Ah you're using PC, make sure you quit Battle.net from the System Tray if you didn't reboot the PC

Okay if you could check and make sure it's using the normal software version please

Definitely won't cause you any problems not using IPv6. Leave it with me and I'll see what we can get done.

Make your Geo-Filter settings then reboot the console then try again please - don't change the settings once you're playing

Are you on the Xbox Insider Program by any chance?

Okay great, could you remove the port forwards, reboot the R3, wait 4 minutes, reboot the Xbox, wait a minute then do a test connection on the Xbox, then launch the game and check again please? As you have an Open NAT and the port forwards aren't doing anything they're not needed and maybe confusing the router.

Very strange, if you connect a device direct to the Hub does it get IPv6? Yes that's right, I don't have a time frame at the moment but I'll see if we can expedite it

We're sure you'll love the R3, thanks for the purchase!

Not a joke, just a bug, change to english complete the wizard, complete the upgrade path then once on RC14 on the interface switch back to Russian

If you check the IP on the console itself and then check the Device Manager on the router for the XBOX device, do the IPs match?

As above! It should mention it on the quick start guide on the box, you can also use http://dumaos

Use an incognito window and see if you can get through it then or factory reset it again then complete it and continue the upgrade path

I notice the hub is reading the router as host 1 now instead of dumaos which may have something to do with it. Reboot the hub, wait 2 minutes, then reboot the R3 from the interface, wait 4 minutes then check again please

Reset the MAC address in the Xbox network settings then reboot it, does it work properly after that?

Access routerlogin.net/adv_index.htm and continue the upgrade to RC14 and factory reset after that

Great news on NAT. It can be quite sensitive in that if nothing is happening it'll show as inactive/offline, if you actually play a game on the console does it show its working then?

Sorry I meant disable IPv6 on the R3 LAN not WAN, keep ULA disabled on the hub

Disable IPv6 on the R3 WAN then reboot please and see if it works then

Clear browser cache/cookies then you should be able to continue the wizard

¿Puedes aclarar por favor?

No there isn't but we can certainly look into implementing that

I think it's about 8ms on average but you can adjust this with expert mode from 0 - 80ms and of course you can disable it as well but yes the idea is to give you one consistent ping so you never experience jitter or spikes

I suspect yours was definitely shipped:

Interesting, it'll likely resolve itself, they may be backed up a little but if not let us know if there is anything we can do

Could you disable ULA at the top there then reboot the R3 from the interface and see if you get IPv6 then please?