Netduma Fraser

Should be at the top of the page where your device is, delete the device or switch to spectating mode

It really depends on how specific you are about the servers you join. If you're very much focused on just getting the London server then I would suggest the first option. If you're okay with trying to prioritize London but with that accepting you will sometimes get games outside your radius then go for option 2. Having played Fortnite in a few long bursts I would say that generally the servers are very good, even if you connect to EU servers.

I understand that you may not think it is relevant but it is precisely the details that people don't provide that come out later on as being very relevant, not in every case of course but I find it can help cut the time down. There is always a reason for me asking something, perhaps in a specific use case I can provide a workaround that I wouldn't have been able to suggest otherwise. You don't need to go into excruciating detail, what you have provided there is enough thank you. Okay that makes more sense, it's essentially a form of VPN, you're creating a tunnel between you and the game server and so we can't see/influence that traffic. While they're not encrypting the traffic they're still controlling it and bypassing the normal way the router would handle that traffic. That's why BI kicked in, it realised that you were gaming, it just couldn't tell what.

Just a reminder, we don't have total control over the XR range. Do you have Adblocker enabled? In LAN Settings, set the DHCP 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 stops the disconnects.

I've chased the team to try and get this in one of the next cloud updates

How have you set Bandwidth Allocation? If this isn't reset/at the defaults it can affect the speed you receive. Likewise if you have share excess disabled for it then that will definitely affect the speeds. How have you setup Traffic Prioritization? If you've made a custom rule that is too wide in its scope then this could also affect the speed. Disable QoS fully from the Congestion Control menu and check the speeds, what do you get then?

Why is it not an option specifically? The only solutions currently are wait for us to update the Fortnite service which I suspect will be next week or add Gaming as a priority. Alternatively you can just prioritize the whole device that is being played on if gaming would cover more than the one device you want to prioritize.

Did you disable Geo-Latency?

If you want the minimal addition in ping then Simple would actually be better as I believe it averages around +8ms. I would think you would need filtering on for this to work best but having filtering off is definitely the reason it's just showing any server and choosing it as what it believes is the host. If you're selecting the server in game then as long as the Geo-Filter mirrors that then there shouldn't be any issues with filtering enabled. It should be target ping and not added on ping as far as I am aware, does it work that way when filtering is enabled?

No difference really at all, you'll just have to put 1000/1000 as your speeds and operate under the assumption that they are your max speeds through the R3. Presumably you'll want to have the Eero upstream so other devices can benefit from the full speeds and then the R3 behind that with a few devices, in which case QoS won't really be that effective and so you'll be mainly using it for the Geo-Filter I assume which you wouldn't change anything based on speeds

Prioritize Gaming and then it will work that way

The way the filtering works in Fortnite is that it only tries to connect you when it loads in after the pre-game run around lobby and so that's the only time we can block the server so it'll just kick you back. 2 options: Disable the filter and use it to determine where you're being placed and quit if it isn't the server you want - it'll be quicker than letting it kick you What you're unknowingly currently doing is using Geo-Latency. Pros for Geo-Latency is that it can allow games previously unfilterable or games that are hard to filter e.g. Fortnite to potentially become filterable. Cons are that it can still result in games outside your radius, this isn't really the features fault, it's more an issue of the game being so desperate to get you into a game it will put you into one that isn't likely to give you a good experience.

That is giving it high priority, it wasn't able to tell it was Fortnite specifically but knows you're gaming and so is still prioritizing it. We'd need to update the Fortnite server for it to specifically state Fortnite so I'll pass that on. Functionally though the result is the same.

Yes it you had the upstream router handle PPPoE instead of the R3 then that should resolve it

From the logs there is a device at .53, go ahead and disable the DHCP server then and see if the disconnects continue please.

Glad to hear you're happy, you're very welcome!

That's not the intention of the Geo-Filter so it's not something we would be able to help you with. There are also a lot of servers clustered in a singular location so the chances are slim.

Not sure that would be a router specific issue or not but you could try disabling QoS fully to see if that helps

Thanks for your feedback, glad to hear that!

The features like ping assist are in the menu top right of the Geo-Filter page. From there: Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Use Simple instead of Custom radius Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and it should work then. This will ensure games stay within your radius. Also unblock the server you denied - when you deny a server you should wait at least 2 minutes in the lobby or reboot the gaming device so the connection is severed, otherwise you can connect to it again.

Added, it has been temporarily removed

No actually disabling the filtering option/remove the device from the Geo-Filter

I have brought this up with a colleage and will get back to you once I have some more information.

It shouldn't make a difference in theory but we are dealing with an issue that shouldn't be happening in the first place but could you change the LAN IP back to 192.168.1.1 and see if it is better please? Also you do have some devices using IPs within the DHCP range still

It could well be the DHCP lease issue yes, in which case given your unique scenario it wouldn't be very practical to assign reserved IPs to each device I'm guessing. A potential solution could be to enable DHCP on the TPs/take them out of AP mode, assign the TPs reserved IP addresses on the XR outside the DHCP range, then it if it continues disable DHCP on the XR and then see if it continues.