Netduma Fraser

I believe it may be due to a cloud update we put out, I will be getting the team to revert this on Tuesday (holiday on Monday in England) and that should resolve it. You should still be able to use the Geo-Filter though, you can click the pin icon to place your location on the map. Just to double check though, is the internet port on the router connected to the modem and not the LAN port?

Creo que puede deberse a una actualización de la nube que lanzamos, haré que el equipo revierta esto el martes (lunes festivo en Inglaterra) y eso debería resolverlo. Sin embargo, aún debería poder usar el Geo-Filter.

Added!

C'est lié au cloud je pense donc on verra si le changement de mardi résout le problème

You'll need to put Ping Assist to 0 to stop any games outside your radius, then it should work better

If you enable Traffic Prio before the game/console is on does it then correctly throttle when you're on the game?

Just a thought but when you enable Traffic Prioritization and QoS isn't throttling properly, is that when you're already on a game?

Interesting, could you double check if Firefox is forcing HTTPS: https://support.mozilla.org/en-US/kb/https-only-prefs#w_enabledisable-https-only-mode and if it is then disable it and see if it behaves more consistently?

I think we're removing the profiles aspect which is why it isn't working specifically, you don't need it though, it just increases/decreases the radius size. I believe the Ping Heatmap issue is due to a cloud update we did which I'm getting the team to revert on Tuesday but the Geo-Filter should still work fine - looks like it's working as expected in the screenshot.

Cree una regla de controlador de tráfico para permitir todo el tráfico a la consola, ¿funciona mejor entonces?

Yes the speed test, so the device added to Traffic Prio is a PlayStation? Have you made any Traffic Controller rules for the PC you're using or DMZ etc?

If it's a cloud issue most people will have the issue, we'll get it reverted on Tuesday and see if that resolves it

Ahh, I think I may know what is going on, is the device you have set in Traffic Prioritization the one you're doing the test on?

Es posible que publiquemos una mala actualización de la nube, haré que el equipo la revierta el martes para ver si eso lo resuelve.

Je pense qu'il est possible que nous ayons publié une mauvaise mise à jour du cloud, donc je vais demander à l'équipe de revenir à la version précédente mardi pour voir si cela aide.

It's possible we've put out a bad cloud update so I'm going to get the team to revert to the previous version on Tuesday to see if that helps.

Thanks for this, I'm going to pass it onto a dev to take a look at. It's also possible we've put out a bad cloud update so I'm going to get the team to revert to the previous version on Tuesday to see if that helps.

You have Early Access so try the firmware there and see if that resolves it for you

Which firmware is the R2 on currently?

Okay that's alright then, while connected via ethernet, disable WiFi radios entirely from the Advanced WiFi settings, reboot the router from the interface, wait 2 minutes, access, enable WiFi radios, apply, reboot from the interface, wait 2 minutes then see if they appear and if it's more stable from then on. If you could grab the log from the System Information page that may provide some insight on what is happening. You can use the R1 but it hasn't had an update in years and of course the hardware isn't as good as the 1000.

When you got to a website it either connects via HTTPS (secured) or HTTP (unsecured), using HTTPS to access the interface https://192.168.1.1 instead of http://192.168.1.1 can cause issues so make sure you use the http URL but before that go to chrome://net-internals/#hsts in your web browser via the URL by and at the bottom enter the IP and delete, then try the HTTP url.

Typical haha! Are you accessing the interface using HTTPS? Some browsers force it and that can cause the type of error

Are you using Armor by any chance? Do you have a browser based Adblocker enabled? Firmware isn't too far away from what I've been told.

Great to hear that, thanks for the update!

Ce n'est pas une erreur en tant que telle, il suffit de dire que l'application prend un peu plus de temps que d'habitude. Utilisez-vous Armure ? Accédez-vous en HTTPS ?