Netduma Fraser

The reason it takes a little longer to block a peer is to prevent people using the router to boot people from a game so it's actually an anti-cheat feature in affect. So as you've mentioned because they're all now misclassified you're succumbing to this anti-cheat measure so as Liam mentioned we will get that sorted and you'll be able to block again more easily. For a peer to be fully blocked the connection to that peer needs to be disconnected for 2 minutes at least, so do as you were doing, quit the game, wait 2 minutes and it will be fully blocked. As for it then taking longer to get games that will be because you're filtering with the radius and then further restricting it with blocking servers in that radius so search times will increase as the amount of available servers decreases, if it's a particular busy time as well then those servers may be full.

Have you tried another provider just in case the services you want block the VPN you're currently using?

Are you forcing a game in your area/region? Are you playing solo or with a group?

Ah, you don't have access to the interface then? They should be able to do that pretty easily for you. While they are at it I would recommend you get that IP put in the modem DMZ as well so you can ensure you get an Open NAT.

Welcome to the forum! 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 more consistently.

With just the power and your PC connected to it (so VM removed from it) and removing the static IP, open command prompt, type ipconfig press enter and then post a screenshot of the results here please.

What is the model of the modem you're using? The easiest way I should think to resolve this would be to set the XR WAN IP as static on the modem if applicable so that it gets it every time

Sometimes modems/routers can be funny about the way they are booted, best thing to do is reboot the modem, wait 2 minutes, then reboot the XR from the interface, wait 2 minutes then access and see if it is working as expected.

Given the PingPlotter results you've provided and that the Ping Test Under Load doesn't show packet loss either then I don't think you are actually getting packet loss and more likely something we would have to look into as to why it is showing that happening. It's always showing right at the end so it could be the test is dropping off to finish and interpreting that as packet loss for example.

That could be why then as 8.8.8.8 is used by Benchmark by default unless it is unavailable and then it would switch to 8.8.4.4, as a test if you switch the DNS to 8.8.8.8 then redo Benchmark does the packet loss go away?

Thank you very much, I see it's forcing you onto 8.8.4.4 rather than 8.8.8.8, could you try that please and provide a screenshot?

Could you provide a full page screenshot of PingPlotter please?

Great, let us know how you get on!

How did you do the factory reset initially? Hold the reset button for 30 seconds, then wait 2 minutes before accessing the interface

I think you may need to do a reboot, then retry or if that doesn't work, a factory reset and then try again. I believe it's got itself into a weird state and can't tell when you've entered VPN details.

Is it still saying no VPN configured when you try to connect?

Could you try with a different server/config (adjust the config to match the template) and try again please?

A latest internal firmware passed at 90% with two important issues being flagged that we're currently working on resolving so it depends how long that takes really, shouldn't be too long and then it should pass at 100% and we can proceed with a release. 450 should follow very closely after the 500.

Are you seeing it every time you run the test? I'd suggest using PingPlotter and see if you see the same packet loss when pinging a more local site

We were already looking at it and it was caused by a complex problem that we were able to fix on a test router so it's looking like that fix will be applied to the next version.

Do you have another adapter with the same output you can try just in case that has become faulty?

Are you seeing the packet loss on the Ping Test or the Ping Test Under Load? The test uses the Google servers so it's not necessarily indicative of overall packet loss but you could just be experiencing it to those servers

I'll have to check with the team regarding this, I know we've received a lot fewer reports of the issue with newer firmware versions. We've pretty much fixed it on the R2 as far as I can tell so should certainly be able to reduce it even further.

Is that the one they gave you as it seems to be using the same DNS and address - if it is then you need to add the listen port option and take the /16 option off the address line and then try again with your keys

Interesting, is it possible you're using the wrong power adapter? It's a fairly generic looking adapter but the voltage etc may be different than what you need. The adapter should read 100-240V, 50-60Hz; Output: 12V, 1000mA - is that what you're using?