Netduma Fraser

Great to hear that, thanks for the update, fingers crossed!

Not currently, that's the last one we have to get ready now so hopefully won't be much longer.

Can you provide a whole page (including the web browser) screenshot of what you're seeing please?

Clear your browser cache/cookies, make sure there is no adblocker on the web browser and if there is disable/whitelist it for the interface. Any Anti-Virus/Firewall applications on the PC that isn't the built in Windows firewall make sure the interface is whitelisted if it affects the web. Then in System Information page in the Rapp panel options change the number of retries to 5 and reboot.

As I mentioned that's not the intentional use of the Geo-Filter and so I couldn't tell you how to make it intentionally work.

What game is it that you're playing? If you're referring to Destiny it does also use servers. Go back to pre-beta and see if it still works

That's not the intended use of the Geo-Filter and not how the game will work exactly. You're most likely making a connection through one of the peers to a server which is allowing other people in.

No after applying the firmware, no need to do so before applying it.

Did you do a factory reset after upgrading to the beta as that is advised.

Invite them to your game/party and look at the Geo-Filter with it fully zoomed out, you should see an icon appear on the map, click that (you may need to disable Auto Ping first) and on the ping panel that appears give it a name and click allow. Could you clarify the second part please, what do you mean people are entering your games when they shouldn't be?

You're very welcome, I'll pass it onto the team to get them to apply the fix when possible.

I've copy and pasted the contents for you: Access your Netduma R1 interface Go to >Settings >Miscellaneous Tick ‘Allow remote access to Netduma tech support’ Go to Settings >UPnP and enable the feature if it's not already enabled Go to Settings > Port Forwarding and remove any rules Now verify that everything is working by going to https://www.whatismyip.com/port-scanner/ In the port entry field, type in 7777 and click Scan If the result is 'Open' then you have successfully allowed us to access your router to run the fix. Please notify us of this on the forum here: http://forum.netduma.com/topic/26317-upgrading-your-netduma-r1-to-dumaos-from-a-version-lower-than-1036/ If the result is closed then you have another router on your network which will block our access attempt. Please put your other router into 'modem mode' or 'bridge mode' (if possible). If you cannot see this option, then you will need to put the Netduma R1 into a DMZ on your other router. Please refer to the user manual for your other router for instructions on how to do this. Repeat the port scan step in steps 6 and 7 above to confirm we can now access your router.

You can find it here: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-DumaOS-3-0/XR700-DumaOS-3-0-Beta-Firmware/td-p/2019958/jump-to/first-unread-message

If there are still issues found in the beta then we will continue to fix them until it is at a state where we think a public release is suitable. If you can't wait until the public release then try the beta.

Thanks for that, please make sure you grab the ID and also input it into the form as it gets sent directly to Alex and he may not see it if posted like this.

If it's deemed to be a consistent issue then yes it would be fixed.

As above, try disabling AX and see if it is any better please.

If it's not showing up on Ping Heatmap or the Geo-Filter then it may be offline or mislocated, what ping do you usually get to the Miami server? The icons with the solid white circles are either allowed hosts by you or whitelisted by us and required for authentication and won't impact your game ping. The yellow icons represents blocked connections.

It isn't currently possible but it is something we'll be looking into and implementing at some point. Most changes should be pretty quick to complete. Is there anything you would want to be saved specifically?

@Hammy sorry to hear you're having this issue, could you have a look at the first post here please? That will help us narrow down the cause of the issue https://forum.netduma.com/topic/33667-having-disconnect-issues-please-post-here/#comments

All you need to do is adjust the radius or polygons to just cover Brazil and block any other country like the US that has a lot of servers and you should be able to force them if they're available.

That one is a server misclassified as a peer, if you put the ID in the form we can correct it.

In the Device Manager give your PC the PlayStation device type and then re-add it to the Geo-Filter and select the manual option. For Traffic Prioritization you can use that service and it will prioritize fine.

What PC game are you playing? We may need to re-test the game and re-classify it. If setting it manually works then do that, no harm doing it that way.

Background traffic is just traffic that isn't being prioritized. You only want to prioritize the most important packets e.g. your game packets, if you prioritized more than was necessary then it would give you adverse affects. If your game is being prioritized when you're playing that that's all good.