Netduma Fraser

Take it out of the DMZ, it shouldn't be there permanently, then re-test again please so we can see properly if those changes helped at all.

To select Gaming as a whole just click Add to Favorites and click Gaming. To add a Games Console select Gaming from the tab there and scroll down until you see Games Console

Very odd that the speeds are actually worse through DMZ. Change your DNS to 1.1.1.1 & 1.0.0.1 it may not help too much but it's worth a try. On the Traffic Controller page make a rule to allow ALL traffic to the PC then run a speed test again please. Nothing unusual in those logs as far I can tell, I have some of the same entries and everything is running fine.

How are you prioritizing? Are you prioritizing gaming as a whole, game console or Call of Duty? Try with each and see if you notice any difference between them.

Hi all, I've added all 3 of you to the beta, you can find it here: https://forum.netduma.com/forum/145-nighthawk-pro-gaming-beta/ Enjoy!

That looks good to me, especially as it is used to power routers you know it'll be safe to do so for the R2

I reply up until midnight BST/GMT every day other than Wednesday (my day off) so all good on that front! Okay so no that won't be it unfortunately. On Connection Benchmark, what speeds does it say you're getting there? After you've done factory resets in the past are there any settings you change right away other than disabling QoS and the other settings you've mentioned so far? As a test put the PC in the DMZ on the R2 then do a speedtest please and see what you get, after you've done that remove it from the DMZ again. I just want to see if with all traffic passing directly through to the PC whether that gives you higher speeds and therefore whether it is something on the router limiting you.

Have you tried this? It seems to have worked for another user having issues with that specific server.

Good suggestion, I'll add it to the list, are you all playing separate games or together?

Great to hear that and no worries at all, I totally understand where you're coming from. If it's not achieving your needs then of course you would wish to return it. Set it up the R2 back to the ONT so the R2 is handling PPPoE, that's what you want to do so lets just start with that. Could you also use speedtest.net to test as well please just so we can get some alternative results. I'm not sure if you were referring to disabling IPv6/protection options on the R2 or not but if you weren't, disable IPv6 in LAN/WAN and the protection options in WAN Settings please as that should boost the speeds a little, give the router a reboot from the interface, wait 2 minutes. Once you've done that please do a speedtest.net test and let us know what you're getting. Assuming you're still not receiving full speeds after that, please grab the MAC address of the router you previously had connected directly to the ONT, then in the R2 WAN Settings set the R2 to use that MAC address, give the router a reboot from the interface, wait 2 minutes and check the speeds again please. The reason I'm mentioning to do this is some ISPs are a bit funny about switching out routers and so you may not get full speeds for a few days if that is the case, by switching the MAC address we can fool the ISP into thinking you're using the old router and therefore higher speeds can be achieved sooner. If that's still not working let me know and then I'll have a few other things we can try/test.

I've responded in your other topic.

By purchasing the router you're agreeing to the terms set out on our website. I explained that the package is opened so we can flash the router to a more up to date firmware. A user cannot determine that the router is faulty, yes I said it could be an issue which it didn't turn out to be in the end but more troubleshooting would either lead us to a solution or a faulty determination. I understand you're frustrated, if you would like to continue troubleshooting then great either we'll come to a solution or we won't and I'll declare it faulty and then you'll get your full refund, you've been great on the information you have provided thus far and so it is likely that within the next few responses we would have reached an endpoint. If you want to just return it then you would have to send it back and we would deduct the shipping cost. I am just following the legal terms on the website agreed to. Please let me know what you would like to do.

Yes that's correct

Added, you can find it here: https://forum.netduma.com/forum/144-netduma-r2-early-access/

It's only just hit Early Access so if you signup here: https://forum.netduma.com/topic/39415-introducing-early-access/ you'll be able to try it.

No worries at all, I'll check with the team to see if they want a generic capture when using the speaker for example or if they want to filter the traffic. It might be easier to provide instructions so you can do so whenever you have the time. I'll get back to you!

Sorry to hear you're having issues. Could you explain what you mean by it moving to a crawl? That error usually occurs when you delete a device from the Device Manager when you still have it added to a feature like the Geo-Filter or Traffic Prioritization for example. If you delete it from these places first before deleting the device on the Device Manager it will prevent the issue happening. Instead of factory resetting to resolve it if you connect the device back to the router in the same way as it was connected previously e.g. 2.4GHz/5GHz or ethernet and give it the same device name and device type that will stop the error appearing. It might be best for you to re-install the firmware so it's a completely fresh installation, possible that it didn't upload correctly. Go to the System Information page and then in the Rapp panel menu ≡ change the retries to 5, reboot from the interface, wait 2 minutes before accessing and it should also happen less.

No not currently unfortunately

Having a look online 2.0mm isn't widely available in the US but yes 2.1 should work so as long as you find one with that maximum then you should be good

Ah that's good to hear, we have made that more sensitive on the R2 so that should make its way over to the XR range as well.

So just to clarify, with the R2 not handling PPPoE the speeds still don't increase? Can you provide a screenshot of your QoS page please?

That's my best guess but I can't be certain until we take PPPoE out of the equation to test if you can get the higher speeds. You'll have to email [email protected] with your order number if you want to return it and we can go from there.

Va bien, nuestra última compilación logró una tasa de aprobación del 88 % en nuestras pruebas, pero el 12 % falló, así que solo queda un poco más por resolver.

Okay so with it setup like that now is the XR applying QoS to upload correctly?

In that case I can put it through as a bug but if it wasn't intended behavior then it's unlikely to be resolved as fast, I'll keep you posted.