Netduma Fraser

As above, I didn't realize you were solely using 5GHz on the Guest WiFi network - you would need to enable the "Allow guests to see each other and access my local network" and then you should be able to access the interface but you don't need to use the Guest WiFi overall. Disabling Smart Connect then gives you a 2.4 & 5GHz network that you can choose between, it will automatically name them differently like the above picture, with Smart Connect they're combined into one network and the router will intelligently switch a device between 2.4/5GHz based on their needs.

Great to hear that, thanks for the update!

You didn't provide much information of what the actual issue was, what do you mean it keeps searching outside, the game won't allow a connection from inside the radius? Try this: Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager (if on PC) Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter with the manual option Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client Then see if it works.

Are you using a WiFi extender or access point or mesh, anything like that at all? Interesting, if you disable the Guest Network does that then allow you to access the interface if you disable Smart Connect via 5GHz?

We don't have any specific recommendations, as long as it can handle the speeds you have and has any options you need it will do the job

Yeah I understand that, a few things before you decide if you want to do either of them. Could you connect via 2.4GHz, access the interface and go to the System Information page and look at the logs. Then connect a device to 5GHz and attempt to connect to the interface, then download the log from the log menu and upload it here please. Hopefully that'll show something that I can then work from or get a dev to take a look at. Enable Smart Connect which will combine 2.4/5GHz into one WiFi network, connect a 2.4GHz device and access the interface and go to the Device Manager, then on another device, run a speed test or a download, something that requires fast speeds, this should make it use 5GHz, you can then confirm this on the Device Manager from the 2.4GHz device. Once you've confirmed this then try accessing the interface on the 5GHz device, does it work?

Thank you, we'll take a look!

Your ping is much higher above using the modem rather than the router, maybe you're getting lag compensated, try playing with QoS completely disabled on the R2 and maybe with a stream running in the background and see if it is better

It's a really weird issue, I can't find any reason for it, a test actually, if you change the R2 MAC address to be the same as your PC for example, does it work then?

I'm checking with him right now and will get back to you as soon as he gives me some info

There are no changes from Netgear in this build so Plex and the version it was on previously will be the same on this version and work the same.

I'm not saying it definitely will fix it but newer firmware brings improvements/fixes and better stability overall and the version mentioned is two iterations higher than yours. I don't think I've seen anyone have this issue before or if they have it's rare, there isn't anything specific to 5GHz that I can think of that would prevent local access. Due to there being no real settings that would affect this I would suggest a factory reset as that's the last kind of reset, by upgrading to the beta though you could get away with not doing that although I would recommend it after the update if you were to do so but it's not a neccessity.

No worries, it can be a bit confusing with the names!

What is the model of the modem/router the R2 is connected to? How is that setup bridge/modem mode or with the R2 in its DMZ? Do you have this issue when connected to the modem? Unplug the router from power for 10 minutes, plug in, then wait 2 minutes before accessing, does it continue to happen?

Hello, welcome to the forum! If you believe there to be a mislocated server please provide the ID of the server and we can take a look. If you want to force a specific server you'll need to reduce your radius to exclude everything else.

As long as you follow the steps including the one if you're having trouble if needed it would be fine. Yes it is a beta but it has been tested by users since May so yes you may have some issues but it's generally quite stable, you're already having an issue which we're having trouble identifying a solution for.

It's important to know what conditions the above tests were done with, even with a local site there are a few spikes there, I think it is the routing to the servers really. Do you get the same issue if you're connected directly to the modem?

I'm hoping if you do the above and allow the server that it will then always allow you to connect

Okay nothing in the logs then that explains it, when you factory reset and it's working, add the console to the Geo-Filter and check for servers appearing when it allows you in, then add that to the allow list and see if it continues working after that

Are you connected to the console via WiFi or ethernet?

Yes that's all disabled so let's see how it goes now!

There is no update on the ticket so far, the dev on it is not available at the moment, I've left them a message and will get back to you when I know more.

Could you try the beta and see whether you get the same issue? https://forum.netduma.com/topic/51611-new-xr500-beta-firmware-33535/

Was the above with streams/downloads being used as well or just on a quiet network?

Okay interesting, that probably is happening because you have no QoS active so everything is fighting each other. Could you re-enable QoS, then completely disable Traffic Prioritization, any rules you've added there and DumaOS Classified Games and see whether either issue returns please?