Netduma Fraser

At 100% it is essentially off, you have to lower it to activate it.

When you're kicked to the lobby and can no longer connect back with filtering mode please look at the map, do you see anything blocked? If so please ping it and provide us with the ID

Okay so to clarify: No Geo-Filter/Spectating Mode = Can game no problem without being kicked back to the lobby? Geo-Filter in Filtering Mode = 1 game works, then kicked to lobby, flush cloud, allowed back to the lobby and then one game allowed and repeat Is that correct? R-App loading should be at a decent speed. Have you done a factory reset since updating to DumaOS? If so have you cleared your browser cache/cookies? They should speed it up. You can still put the same VPN Settings into the router that you did with the original firmware. If you're not sure how to do so let me know what you're wanting to achieve and I can help.

What do you find slow about it? We actually designed it to be MORE user friendly, what don't you find user friendly about it? I'm not sure if that is completely related to the Geo-Filter as I have experienced this many times when testing through ISP hub. We released a cloud update this week for Apex, flush the cloud, does it improve your experience then?

Okay so that could indicate fluctuations on your base ping. Possible that could be a congested time for the ISP, try again at a later time and see if you get the same thing.

How was the test done Ali? Was it with nothing happening on the network or was it saturated? QoS or not? During peak times?

I've chased the team for you to get the fix sent

Don't do that checker it gives you no information, keep persisting with PingPlotter and gather logs from the sky hub as well, they might have connection statistics too

Sorry to hear that. I'd just try and gather as much evidence if you can as possible to show them. Does it happen at peak times or all the time?

I see it's direct from the Sky router, were devices using the internet? If so then that's likely what caused it with no QoS to prevent it. Repeat the test on DumaOS and it should be better!

The red chunks are indicative of packet loss. Though it looks by the focus time that you changed it to 1 second is that correct? Leave it on the default settings as the 1 second focus can give false results like that

Yes you're on the latest, no need to worry. Welcome to the forum!

You're on DumaOS already? If so that is the latest firmware

I've just chased Joseph so will hopefully get back to you soon.

We'll try again next week

To login it's admin / password

Okay thank you, we won't be able to check until 10-6pm GMT during the week. Interesting, do you have the R1 in the 4G router's DMZ? Are you able to put the 4G router in modem mode?

Everyone but second paragraph specific to henris

I've chased the team again to check this. As we're admins we see the IP attached to your post. If you could post from home that'd be really helpful so we can check the right one. It sounds like your DHCP server is not configured properly, have you changed its settings?

I'm not sure on that, when they check again if it doesn't work they should provide some more information on next steps

Thanks, hopefully they'll check again soon. Also it's not a good idea to reveal your public IP so no need to provide screenshots etc

Your IP has been changing a bit, don't do the test on a phone as it may be using the cellular network. Do so on a PC so you can double check the ports and we get the correct IP.

No worries, we'll get an email over to you, likely tomorrow!

Hey, welcome to the forum! To bridge you should be bridging it to the Netduma's WAN IP (this is the IP the TP-Link has given it) so you can find it on the TP Link and in the Netduma's Device Manager. You should NOT be using the 192.168.88.1 IP as it won't work. If Bridge mode still doesn't work then I would put the R1 (using same IP) into the TP Link DMZ. Please also make sure you have remote support enabled in the R1's Miscellaneous settings.

Hopefully before then!