Netduma Fraser

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 ?

For a console you just need to add it to the Geo-Filter with the manual option then you can filter the game. Traffic Prioritization will automatically prioritize the game but if you want to manually add a rule you can use the Games Console service as you're playing on a console. It's best not to use the web browser on a mobile as it won't be fully optimized, you can use the DumaOS app on your app store instead if you want to use mobile. What is the model of the modem/router the R2 is connected to and how did you connect it to the router exactly? Could you provide a screenshot of the Device Manager table view please?

Vaya a la página Información del sistema y luego en el menú del panel Rapp ≡ cambie los reintentos a 5, reinicie desde la interfaz, espere 2 minutos antes de acceder y vea si funciona, por favor.

Putting the R2 in its DMZ wouldn't cause any devices connected to the R2 to be open to the internet, the R2 has a firewall so it is safe to do so, try with that and see if IPv6 then works

By cascade do you mean you've put the R2 in the AX DMZ as I can't see a specific cascade option on their manual

Traffic uses ports so in order to allow people to prioritize literally anything that's why we allow people to prioritize ports. Services such as Games Console is an easy way for the end user to prioritize a group of ports that a games consoles uses.

Not quite, having IPv6 enabled on LAN would give devices local IPv6 addresses like you get with IPv4 192.168.77.100 for example. IPv6 was designed to deal with the shortage of IPv4 addresses but on your local network you're not going to have that problem so this can be disabled, a local IPv6 address isn't required for a public IPv6 address, as long as WAN is enabled then each device will use the public IPv6 address.

QoS/Traffic Prioritization doesn't open ports, it just prioritizes traffic, UPnP, Port Forwarding/Triggering/DMZ are the only settings where the status of a port is changed. This can happen if you're already on a game for example and it's actively prioritizing, it can still prioritize when disabled until that connection is severed. It won't be an issue on SmartQoS though.

Cela s'est-il produit lorsque vous avez resynchronisé le cloud ? Si c'est le cas, attendez une minute, puis actualisez la page et il l'aura fait avec succès

You only need to have it enabled for the WAN, you can disable it on LAN