Netduma Fraser

When that happens it's almost certainly because the rule is invalid or something was missed so I'm sure it can be fixed without a reset

From the Telstra side of things, that shouldn't affect it, can you not reach it from http://mymodem/ or http://192.168.0.1/ ?

Are you changing settings or applying the filter while already on the game or with steam enabled by any chance?

That's just a case of mislocated servers, the Geo-Filter is working because it thinks it's there and so is allowing it. If you could provide any IDs in that situation we can get those corrected with a cloud update and then it'll be more accurate.

Could be PPPoE potentially, do you have another router you can test with to handle that and then connect the R3 to it and see if it triggers properly?

Ah, did you disable DPI in Settings by any chance? Well if it can't detect it then it won't be prioritizing, do you see servers on the Geo-Filter Map with the device added.

Thanks for that, I'll pass it on, most likely we're unable to ping the server (game servers don't generally respond well to pings) and so it's taking the last ping response which is low.

Could you provide a screenshot of what you're seeing please?

Doesn't have to be but the individual services are more likely to become out of date faster, try it and let us know how you get on.

I replied to your topic but it's a temporary traffic prioritization rule so you can still do it but just not with a temporary rule.

By unable to add rules exactly what does that mean? You add it and it doesn't add it, gives an error, adds but doesn't work etc? If they're added but not working can you provide a screenshot of them please and if they won't add can you provide a screenshot of the rule you're trying to make please?

Yes that's correct, you're on the latest beta!

What is the issue you're having when trying to use it on the R3? No specific guide but if you copy the config file and enter it then put in your user/pass it should work. If not post your config file and I can take a look.

Added

That would be very cool, I'll add it to the list!

We've updated the look - priority boost was just a temporary traffic prioritization rule, so while you can't make a temporary rule now you can still achieve the same affect.

He's working on a big update at the moment so it won't be immediate

Please do so from the interface instead, timing can be important from the hardware

Great to hear! I'll come back to you as soon as I hear anything

At this stage I think a factory reset would be best if you could do so from the interface please and check the behavior after that.

Thanks for the kind words!

In some cases maybe, but not even showing on the device view after being added is very odd. They're 100% connected directly to the router, not through another router, AP, switch, extender etc? What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g. R3 in its DMZ, modem/bridge mode

If you follow the process above you should see servers. Other than that the only difference would be a different cloud version, in which case when we do the next update that'll be sorted. It'll be because the server is whitelisted if you can provide the ID we can remove it and that will prevent it.

I suspect because in most cases (you included) you can't actually do anything with that information, it's very unusual your internet provider would adjust routing for you, that's certainly not common practice and the servers won't respond to traditional pings either.

Try upgrading to this one: https://www.dropbox.com/s/mb7hztmwpxnpz2i/XR500-V2.3.2.134-dumaos33-rc10.img?dl=0 then upgrade to 14 after and see if it works please