Netduma Liam

Yes, that's because these devices are strictly limited to their allocation and cannot borrow from other devices. That's the only way to specifically hard limit a device though.

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!

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.

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.

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.

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.

@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.

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.

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.

Last I checked, you should still be able to filter which of the SDR servers you connect to. This may be slightly different from the actual game server, but it should be close enough. If you set your filter area for Western Europe, it would make sense that you're unable to connect to a US server, unless I've misunderstood you there?

I'd suggest signing up for the Early Access beta as Fraser mentioned, you can then try a newer firmware with bug fixes.

If you add your Xbox to Geo-filter, but select "Choose manually" when prompted to pick a service, it'll then automatically filter any games you play, including Destiny. Let us know if you need anything else!

Maybe we're dealing with some Wireless contention here. Could you try downloading a Wi-Fi Analyser (there's one on the Microsoft store called Wi-Fi Analyser) and run a couple tests. Find which channels are least congested and switch your Wi-Fi on the R2 to use those. I know you mentioned you'd experimented with some different ones, but this test actually tells us which are the best to use. Now the R2 is back in the network, you've currently got ALL devices connected to it again, is that right? Have you still got the Traffic Prioritisation rule we added for your games console, and you're still seeing occasional stutters and ping spikes with this? Is this occuring when the network is very busy (downloads, updates, etc) or do you get this regardless of how busy the network is?

I'll let the team know the big release is today and we'll see if we can get it on Ping Heatmap! Are ALL devices on the network connected to your XR1000 or do some still connect to the upstream router/modem? What device are you playing on? How is it connected to the XR1000? Do you know anything inbetween your gaming device and the XR such as powerline extenders, Wi-Fi boosters, etc?

Yeah I think it's more a case of how HybridVPN reads the config files, it clearly has issues with the first one and not the second. We're still investigating so we hope to have it fixed for then next update. Feel free to send the config files you've got over to us, it may also help our developer in debugging the issue.

We believe there may be an issue with the R2s throughput when it comes to PPPoE. Hence why Fraser suggested using the XR500 to handle this. You can then disable any and all DumaOS features on the XR500 and configure all of this on the R2 if that's what you'd rather use. Just be sure to put the R2s WAN IP in the DMZ of the XR500, you can find this setting in Settings -> Setup -> WAN Setup -> Default DMZ server. Test your throughputs then through the R2 and it should all be good.

Since the reset, can you access the DumaOS interface if you use an incognito/private window in your browser?

I'm afraid not, I asked about it this morning, there's is one bug which is now fixed, but I believe there's still a separate issue. We'll get an early access/beta firmware built when we've got more information on the issue and hopefully we can give it to some people such as yourself and you can test it. I don't have any kind of an ETA for such a fix as we're not sure whether we're going to be able to do that yet, but in an ideal world that's how we'll proceed.

Can you clear your browsers cache now that you've completed the update and see if it works after that?