Netduma Fraser

Okay re-enable DST and see if it's correct with the new NTP server please. So the fe80 is a link local IPv6 address, you can ignore that, your connection isn't using IPv6 but as the options are enabled that's why you're getting it, you can ignore it completely, it won't have any affect. As for the other addresses that will be what I mentioned previously, if you give each device a reserved IP and reboot then it will just have the one & the link local IPv6 address (unless you disable IPv6 in LAN/WAN) but you can ignore it, it won't cause any issues. Setting the reserved IPs may help with them showing offline but otherwise it will be due to using the APs, also if traffic isn't going through a device it will very quickly switch to offline even if it's still connected.

So the Ping Test in the middle is a baseline test and it does indicate you have a big spike issue, it could be your connection to the Google server specifically which is used for the test or an indication of a bigger issue with your ISP/line. Best thing to do to check is to connect directly to the modem and see if you have the same issue.

Welcome to the forum! To answer your questions/concerns: Did you do a factory reset after you upgraded to the latest firmware? If not that is highly recommended. Do you have Armor enabled? They will show connected via ethernet because technically the router is receiving/sending traffic via ethernet to those devices. In regards to the offline aspect I believe that is something we're looking at fine tuning, it's due to the APs basically, a reboot of the router should resolve it in most cases. Change the NTP server to 0.uk.pool.ntp.org and disable DST and apply, does it work better then? Could you provide a screenshot of an example of a device receiving two IP addresses? Likely what has happened is that DHCP has assigned a different IP when the lease renewed, the old one won't be used and would be removed after a reboot.

First of all, excellent way to ask questions, love it! Really the answers depend on whether the mesh is handing out IP addresses itself or if the R2 would be assigning IPs, given mesh systems usually exist as a replacement to your existing router I would have thought it would be the former, could you confirm the situation for the mesh you're using? Then I can more accurately provide answers to your questions.

Please do so via email, Liam will be away next week and so to ensure a quick replacement email is the best best. If we end up troubleshooting it we'll get back to you!

When making changes to the R2 WiFi it won't affect the WiFi of the devices behind it so you wouldn't do anything on there to get the Ubi devices using 5GHz only, you would do that on their interfaces. If devices were connected to the 2.4GHz then they would disconnect until you then reconnect them to the 5GHz. You may have some devices that work with 2.4GHz only. If for some reason the WiFi of the R2 being on/off somehow causes the Ubi WiFi to go off then just re-enable the R2 WiFi but select the option to not broadcast the SSID, that will prevent it showing in the list of WiFi networks in your area.

Perfect explanation above!

Congestion Control is the main feature that would prevent local congestion causing you to lag, Traffic Prioritization helps to keep your ping stable and free from spikes/jitter so I would recommend using them both but absolutely experiment with it and find what works best for you. Every connection is different so there is no one way it has to be used to reap the benefits.

Welcome to the forum! Sorry to hear you're having this issue, have any settings been changed or any new devices being added prior to the issues occurring? How did you figure out it did a factory reset without being able to confirm by accessing - did the WiFi SSID revert to the default? What is the model of the modem/router you're using that the XR is connected to? In LAN Setting, set the DHCP range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range, apply, reboot from the interface, wait 2 minutes and see if that stops the disconnects.

We are prepped and ready to test the games and to make any necessary adjustments we may need to get them supported with the router, so far the server locations every year haven't really changed too much so I suspect it will probably be the same but we'll double check that of course.

Best way to tell if it is getting bogged down would be to give it a reboot, wait 2 minutes then play, if you notice a difference then that could be it. Doing a bufferbloat test won't necessarily always indicate whether you need to apply QoS or not, a single download will saturate your connection, any devices using the internet while gaming will create a network queue and QoS will help stop both of those things happening so I would recommend you use it and see if you notice an improvement.

So the setup is modem > R2 > XR1000 (AP)? I don't think that would be a significant factor unless System Information is showing very high CPU usage constantly for example, I suspect that if it's a recent thing that more people are jumping online in preparation for the CoD beta and the servers may be under more stress, try forcing different servers even if they're slightly higher ping and see if they perform any better.

DumaOS Classified Games uses DPI to detect and prioritize a game, as it's not one we have tested and therefore added support for it won't work currently. However, the Games Console services uses a range of ports that all games use and therefore it will work for every game without us needing to do anything. Classified Games would be better as it specifically targets the game, however the range of ports the Games Console service prioritizes are not commonly used by other applications/services so it will still work very well.

As I mentioned, we haven't changed anything on our end and anything we can/do change is to ensure it continues functioning in the correct way, otherwise it can become outdated. The only anti-cheat feature we have is that when you add a peer to the deny list that it takes 2 minutes to take affect after you're disconnected from the host, that's been in place since 2014. We've not accused you of cheating nor have we put anything in place that would have prevented you doing any kind of filtering. The issue you're having right now is isolated to your router, if it was something we had done then everyone would be affected (we can't specify routers to apply a cloud update to) and we'd very quickly be inundated with posts. Has it worked after re-updating/resetting?

Let us know how you get on!

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.

The main functionality of the router won't be changed by cloud updates, only by firmware, for the Geo-Filter we only update the classification so whether it's a peer or server, the location of a peer/server and whether we add a server to the whitelist or updating a service but none of those would have affected it. On the PC itself take a look at the IP address then on the Device Manager look at the device you believe to be the PC, do the IPs match?

Ahh that's interesting, thanks for letting us know!

Thanks for the screenshot, everything looks okay there, very odd that disabling mirror mode would reduce the speeds on ethernet, we'll have to look into that but well done on figuring that out. 200 is what I would expect most people to be able to achieve, it may be possible to get more, try these suggestions and see if that boosts it: Use a WiFi analyzer to find the least congested channel and change to that Experiment with the widths to see what gives better results Ensure it's in an elevated position - not on a metal surface Ensure there aren't any electrical / wireless devices e.g headphones etc within close proximity ~3 feet if possible Set the antennae to this position _ | | _

It looks like it's acting like a switch so it will need to be reset to start working again. Unplug the router from power for 10 minutes, plug in, wait 2 minutes, hold the reset button for 30 seconds and release, wait 2 minutes then see if you can access the interface

I have let the team know and they should push an update tomorrow

It's up to you really, if you don't have many devices online and using a lot of bandwidth and you would prefer to have higher speeds then you can leave it off if you want. Otherwise I'd say re-enable QoS and experiment with the percentages to get the best results on Benchmark.

Okay that will be the max speeds you're able to get through your R2 then so I'd suggest setting those speeds as what you get then do my first post again to get the Ping Under Load as stable as you can

Did you follow all the steps again, if you're already on the game then it likely wouldn't detect. We recommend it because the specific services can get out of date which is what I thought could possibly have happened here.

Did you do step 3 & 5 from my steps? As it should be added with the Games Console service instead of Fortnite which should then work