Netduma Fraser

Thanks for trying, 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 see if it works then please.

I've written the steps for you here: Go to chrome://net-internals/#hsts in the web browser Enter 192.168.1.1 in the "Delete domain security policies" box & click delete Access the router interface: http://192.168.1.1 Does the Geo-Filter page then work? As you're having an issue it is a troubleshooting step and so not the norm, whether it is an issue with your browser or not I don't know yet. Are you using Armor? You should have seen this come up in the Setup Wizard, did you enable this?

No unfortunately not, you still have to upgrade manually for the moment. Not at all, it's a fair question and that's what I'm here for to answer any questions you have!

So if you follow the guide to prevent the router interface 192.168.1.1 from using HTTPS that will get you sorted

That's quite an old version, the latest public release is here: https://forum.netduma.com/topic/39522-new-r2-firmware-32453/ Alternatively you can sign up for Early Access and once approved try even newer firmware: https://forum.netduma.com/topic/39415-introducing-early-access/

Double check Chrome isn't forcing a HTTPS connection to the interface, then force a connection using HTTP instead https://howchoo.com/chrome/stop-chrome-from-automatically-redirecting-https and see if that resolves it

You can sign up here: https://forum.netduma.com/topic/39415-introducing-early-access/ and once approved we'll add you to the beta but yes it's basically open!

Welcome to the forum! What web browser are you using to access the interface? Are you using Armor by chance? If you click ok on the error can you continue to use the Geo-Filter?

Hit detection is a hard one as it doesn't have any stats and we can only go on improving the stats like ping, packet loss etc. It's especially difficult if you have a good ping but bad hit detection as it's not necessarily anything on your side. People try throttling, experimenting with different ports for Traffic Prioritization and adjusting their MTU so might be worth a look.

You can give it ago, just keep in mind with the suggestion from Liam, it will limit the other devices to their allocation

It's not a huge spike and it could just be your connection to Google so I don't think it's worth mentioning really, they will very likely tell you it's within normal parameters.

Making a lot of good progress, a lot of things to whitelist basically, should be finished on Monday

That does look pretty good, unfortunately it does look like your base connection does spike every so often as well, it's not super high but you may notice this in game, you can see this reflected in Ping Under Load as well which is why you won't be able to get it flat.

Ping Under Load at that rating would indicate that QoS needs to be fine tuned some more. It's best to start with a high value for Congestion Control, say 95% then do a test, decrease by 10%, test, decrease by 10% etc, until you get to a value that is pretty good and then try 5% either side of that value to see if it can be improved. It's important to note that Download & Upload on Congestion Control don't have to be the same value and that you may have a better experience with differing values. What is the model of your ISP modem/router? Are ALL devices connected to the R2?

We're testing a new version currently so shouldn't be too long now

Best to use it without the Geo-Filter for the moment until we can get that sorted.

Try forcing servers slightly further away, if that doesn't help see if you can record and example so we can see what is happening

Great thanks, we did find a server that was blocked that should be whitelisted but it's still not working so will require some more testing.

The team are currently looking into it, just to double check, is it a PC you're playing on?

The DHCP range should be set to start at .100 for example and then the reserved IPs should be outside of that range such as .2 - .99 however you want to do it but the reserved IPs have to be outside the range you set to work

I'll get that added to our roadmap, thanks for the suggestions!

It may be that Opera is forcing a connection to the interface using HTTPS so if you can disable that then it may then work on Opera

¿Es lo mismo en los otros puertos también?

We're actually working on integrating Ping Heatmap and the Geo-Filter together to make an overall better, more optimized experience!

Yes it would be via a firmware update