Netduma Liam

You can use bandwidth allocation, with Share Excess disabled from the submenu in Bandwidth Allocation. You can then limit the bandwidth to specific devices.

That's already been added, I don't know whether it'll be in the next release or the one immediately after, but it won't be long!

Welcome to the forum! Are all devices connected directly to the R2? Can you send over a screenshot of how you've currently got QoS configured?

Move the sliders back up to about 70%, then go down to Traffic Prio and disable all rules. Add a new rules, select your gaming device and select 'Games Console' as the service. Test that and see how it feels.

Of course, thank you!

We believe we're getting close now, we've fixed what we believe was the last big bug and are now awaiting more firmware. Once we've got that we'll test again and if it's all good we'll go ahead and start releasing it.

That's bizarre, OK let me see if we can reproduce this issue internally and figure out what's causing it.

Bien, ¿entonces lo desconectas y lo vuelves a conectar con bastante frecuencia? ¿Puede enviar un correo electrónico a [email protected] con su número de pedido original y la dirección de entrega, por favor?

Benvenuto nel forum! Il mio suggerimento sarebbe semplicemente quello di aggiungere una nuova regola alla prioritizzazione del traffico, selezionare la PS5 come dispositivo, quindi selezionare Games Console come servizio. Dovresti quindi avere tutti i tuoi giochi dalla PS5 prioritari. Consulta questa guida per ulteriori informazioni su come ottenere la configurazione QoS in generale: https://support.netduma.com/support/solutions/articles/16000077073-dumaos-optimal-settings-guide-qos

Can you click on the server you're seeing that's appearing as being whitelisted (has the circle around the icon) and send me the ID of it? It's possible it's been whitelisted by mistake. I'm afraid there isn't currently a way to take the data you see in Ping Heatmap and apply it directly over to Geo-filter.

Welcome to the forum! Sorry to hear you're having trouble. Is your PC running Windows? If so, could you please try setting a static IP in Windows with the following information: IP address: 192.168.77.100 Subnet mask: 255.255.255.0 Default gateway: 192.168.77.1 If you're not sure how to do this, you can use this guide: https://kb.netgear.com/27476/How-do-I-set-a-static-IP-address-in-Windows After that, could you please reboot the R2 and see if you can access the interface again.

Yeah that's fine, as long as it's connected via ethernet. Perhaps it's a hardware problem on the PC then!

Do you have any servers in your allow and deny list? There server that's appearing in the UK is manually whitelisted, hence why you're getting connected to it.

Odd, that shouldn't be related to the cloud update. Are you getting this if you access the interface from a completely different browser? If so, could you perhaps try rebooting the R2?

It seems less likely to be an issue with your hardware, it shouldn't have much affect on streaming content from YouTube. That being said, full/failing drives can cause some really bizarre problems. Can you see if you can find another device you can connect via ethernet, then stream some content on there and see how it is?

Is it definitely still enabled from the wireless settings on the XR700? I believe you need to download the Nighthawk app on your mobile device.

You can pick Gaming/Voice there. Which firmware version are you running out of interest?

@Bul Remove your current profile, then re-add it. Instead of selecting a service, pick 'Choose manually' when prompted to pick a service. Give that a test and see how it feels. We're updating the Ping Heatmap servers for MW2 again today. They seem to mess around with their servers a lot when the game first launches, we're also working on a solution that will affect you guys less when this happens.

@alex.devine @johnnytran Have you guys tested out my suggestion above? The key part being adding the custom rule to Traffic Prio, I think it should help you. As you mention, we are also working on a update to help DumaOS detect the new CoD's traffic much more fluently, that should improve matters.

This one's likely all about QoS. My initial suggestion here for you: Make sure ALL devices on your network are connected through your R2 Make sure your bandwidth speeds are set correctly in QoS (Click the three-line menu in Congestion Control -> Set Bandwidth Speeds) Set Congestion Control sliders to about 70% each, to start with. Set Congestion Control to Auto-enable Disable ALL rules in Traffic Prioritisation Manually add a new rule to Traffic Prio, select the device you're playing on, then select 'Games Console' as the service. Go ahead and play some games and see how it feels. If you're still having issues, post a screenshot of how QoS and Geo-filter are currently setup.

Yes, there's no reason why not. The biggest obstacle currently is detecting that type of traffic, but we've been making huge progress in how we categorise applications and identify them (DPI), so DumaOS should work better and better with Mobile gaming as time goes on.

Not 3.0, the plan is to bring you up to 3.2 I believe. We're working on this firmware for the XR500 currently, once we've fixed the remaining bugs we'll build an XR700 firmware with the same changes and that should be a much quicker turnaround.

We're still working on the new firmware, yes. I believe if you click the three-line menu in Device Manager you can download a list of all device names, then upload that again after the reset so you don't need to go through and rename your devices.

So what's happening with Ping Assist set to 0? Are you still getting into lobbies outside the UK? What are you seeing on the Geo-filter map when this happens? Can you provide a screenshot?

We've had a lot of problems getting the XR500 on 3.2. The reason testing is taking so long is because it's not just testing, we've found a couple of big bugs, had to debug them, send patches/fixes to NETGEAR, then when we get a firmware back with that fix we are able to test deeper and uncover new issues. We're now waiting on an updated build with some new fixes to continue testing, we'll update the progress page accordingly today.