Netduma Fraser

Just over 2 weeks

Are you checking the ping in game or somewhere else? 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. Are ALL devices connected to the R3?

It was the right IP we were using, the same one you provided but we still can't access. Is everything done from the above? Do you know if you have a CG-NAT?

That is really helpful thank you!

We weren't able to access, could you double check everything please: Also make sure you don't have a device in the R2 DMZ. Please also PM your public IP address.

It doesn't work like that, Ping Optimizer runs tests to see what Congestion Control values would work best to keep your ping as low as possible, if you accept the results it will then change the Congestion Control percentages for you. However, you can manually adjust Congestion Control yourself but it does not impact the Ping Optimizer test results and it doesn't take your changes to the percentages into account at all.

Not an authentication server then no, do you have the ID for it? Then I can check its location. If you disable Geo Latency filtering won't work at all for Fortnite

I appreciate you're frustrated but posts like this doesn't make it any faster or allow me to give you any more information. I'm sure you would rather we take our time getting it right rather than rushing out an update that could cause you more issues. If you're having problems do make a topic and I'll be happy to help you.

What do you mean you can't select your game on the map exactly? If you've added your console and set your location/radius on the map then all you need to do is search for a game on CoD and the Geo-Filter will filter for you, forcing a server within your radius

Brilliant to hear that, thanks for the update!

Is this with Geo-Latency on or off? With it on it should work just fine. With it off you would need to add your friends to your allow list, have you done this?

Either rebooting the PC or waiting 5-10 minutes off the game should then allow it to go back to normal. If you reconnect too quickly those old connections you made haven't fully severed yet and so it still tries to connect you to the previous areas.

There isn't necessarily a best firmware for bufferbloat/hit detection. Bufferbloat is based on your settings. The high CPU issue would likely impact your game though so would suggest going on to .41 for that reason. If it's at 100% constantly then makes sense that if you keep it like that for a long time it will wear out faster.

Reboot the modem, wait 2 minutes then reboot the R3, wait 2 minutes and see if you get internet then. Otherwise, do you know if you require PPPoE/VLAN to get internet?

Glad you got it all working, let us know if you have any other questions!

This might be related to your NAT issue where your PC changed IP address, I think I said to give it a reserved IP, once you do that and delete any other devices from the Device Manager that appear as your PC so you just have the one with the reserved IP see if it then works better

Thank you for the report, I think I'm seeing a few other people report something similar so I will pass it onto the team

We can try that, if it's inaccessible though it's likely DumaOS isn't running properly and so may not be able to access. Also the point of doing it before the issue is so that we get more information as they're enhanced logs, I'm not sure if this would work backwards

Set a reserved IP for it in Settings > DHCP and that'll prevent the PC doing that again

Yes that's correct, once you confirm I can have the team try to enable it tomorrow. Thanks for the vid, I will pass that on!

At 0 Ping Assist would be off traditionally, so I wonder if it's making it behave weirdly, try it with 10-35, does it work better then? I know the servers are a bit worse at the moment due to season 2 so give it a try at a less populated time perhaps and see if it is more consistent.

Try this: Quit the application/game/client completely including from the System Tray Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager (if on PC) Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter with the manual option Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client Then see if it works better.

That may be how you feel and I appreciate that, you know that development is fluid and can take longer than expected. Not everyone feels that way though. I think there will be an update out this month, I'd be very surprised if there wasn't.

Glad to hear you were able to get it sorted, thanks for the update!

Okay but not prior? Could you check the IP on the R3 and the IP in the DMZ on the ISP router? If this is happening once or twice a week if could be the ISP router renewing IPs and therefore giving the R3 a different IP