Netduma Fraser

If you're trying to do solo games in Destiny then it won't work and that isn't the purpose of the Geo-Filter. Battlefield it somewhat works but due to their matchmaking design the Geo-Filter doesn't historically work well with many of the BF games. We haven't specifically tested Warframe so I couldn't comment on that one. Can you provide a screenshot of your Geo-Filter page please?

Hey, welcome to the forum! We haven't specifically tested the game as far as I'm aware but it should work so yes in theory you would be able to force that server. Yes you can enable/disable the Geo-Filter very easily.

No updates available currently, we'll let people know when its released

No there isn't, they have actively put measures in place to counteract Geo-Filtering - more so people exploiting the way to do this with the game files and we're a byproduct of those measures as well.

Great to hear that! So Traffic Prioritization supersedes Congestion Control/Bandwidth Allocation so if you've made a custom rule that includes the ports they use for the speed test (which it sounds like you may have done) then that is why it seemingly won't adhere to the percentage set. By default the console/game will be prioritized by DumaOS Classified Games so you could just enable that or add with the console service or add ports if you want but not using port 80/443. Then allocation will work as well!

Thanks for the information, the only other thing that could be affecting it would be if you've made a custom Traffic Prioritization rule for the console, have you done that?

Are ALL devices connected to the R2? Are you using PPPoE, VLAN or DHCP identifiers to get a connection? Did you by any chance put the console in the DMZ or make a Traffic Controller rule for it?

Are you rebooting by pulling the power or pressing the button on the back? Try rebooting from 192.168.1.1/adv_index.htm instead

Thanks for that! Yes generally adjusting Congestion Control more will make a bigger difference to lag than Bandwidth Allocation - all Bandwidth Allocation does is allocate bandwidth, that in itself won't really help. When you click save on the right panel also click Update Distribution on the main part. If that doesn't work then set it using the main part and then update and see if it works.

Can you show the top of the page as well please, as well as open Bandwidth Allocation to show that Share excess is disabled. Did you set the allocation using the panel on the right or did you drag it using the main part of the feature? Also gaming won't really use more than 1Mbps so you definitely don't need to be giving that much as it won't get used

You need to use the details that you normally login to the router with

I think your best option at the moment while you wait would be to downgrade to an earlier DumaOS version that you know has been stable for you, you will lose some features but hopefully gain more stability.

Thanks for that, disable IPv6 in LAN and WAN, also disable Port Scan and Syn Flood Protection, reboot the gaming device and see if it works from then on please

I can't specifically see anything in the logs that would hint either way why it's working or not working, that's why I wanted you to test with another router for a long period as nothing appears to change. I can see though that it looks like the DHCP instructions I gave you were done incorrectly, can you provide a screenshot of the LAN Settings page please?

Could you play using your own router for a few days and see if you ever get the issue happening? It seems odd that it works, then it doesn't, then it does without any changes to the router settings so I'm wondering if it's on the game side and happens randomly depending on server load, time of day etc

Alright keep us posted, fingers crossed!

Thanks for the log file, what is the model of the modem/router the R2 is connected to? Also on the R2 set the DHCP lease time to 168 hours and change the range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range, apply, reboot from the interface, wait 2 minutes and see if that helps please.

Si desea velocidades máximas, entonces sí, pero si está de acuerdo con que sean más bajas y aún desea los beneficios de QoS, déjelo habilitado.

Sí, debido a su antigüedad en el hardware que se necesita

Es un enrutador antiguo, por lo que probablemente sea lo máximo que pueda lograr sin deshabilitar QoS

Deshabilite las opciones de protección en la configuración de WAN, ya que eso puede ayudar a aumentar las velocidades

Do keep us posted! It's possible memory is filling up which is why it happened after two weeks, hence would like to see if it happens again roughly after the same amount of time

Interesting, could you give it a factory reset and see whether it occurs again after the same amount of time? This may be related to something we've figured out recently

Glad to hear it's working, hopefully it will stay that way but do keep us posted.

Try the connection to the game then when it fails immediately get the logs from the System Information page and post it here please, hopefully there will be a clue there.