Netduma Fraser

You can try disabling the protection options in troubleshooting settings, that may boost the speeds slightly but it's unlikely to be significant. In terms of the bufferbloat it's possible you'd need different Congestion Control values for IPv6 vs without

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 Upgrade to the DumaOS 4 beta and try with Geo-Latency that might give you better results - let me know if you want access

I've chased them again hopefully they will get to it soon

The DHCP lease is something for NG, it's been around a long time, it's unlikely they'll resolve it now tbh. DPIclass we're looking into currently, hopefully it'll just be a cloud fix

I haven't used VM for awhile now so I couldn't say, I know they have new hubs out now so it's probably better than it was

Check the map when that happens, do you see anything blocked? If so allow it, does that let you in then?

That's a local IP, we don't need that, I can see IPv6 again, did you re-enable IPv6 or are you not posting from a device connected to the router? They won't be able to connect unless you follow the steps I provided exactly. If you absolutely did then your IP changed so we'll need you to post here again from a device connected to the router so we can get the latest IP address.

The team have connected and have asked that you forget the wifi on each device and then re-connect again and see if you continue having the same issues please

They tried to connect but were not able to, your IP may have changed, can you post here again asap please?

Great thank you, I've passed on the details and they'll get to it as soon as they can, hopefully today but maybe tomorrow. Just keep the setup as you have it currently.

So if you're on the very latest R3 Early Access version then now there is a feature called Behavioral Identification which basically means even though it doesn't know what game you're playing it can tell you're playing a game and will then prioritize it. The other option is to just prioritize the device you're playing on

Thanks for your feedback, not really the place for it but I appreciate it none the less, we wish you the best!

I've literally been getting the same thing, I've already passed it over to a colleague to have a look

Added

The main router being in bridge mode is good, it provides a direct line to the internet for the R3. As long as it is all setup still for tomorrow then we should be able to connect.

Added

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 Keep LAN disabled on the R3 and WAN enabled then check after a reboot please

It's a DDoS attack essentially, without knowing the source IP we can't tell where it came from. If you were playing a game at the time it was likely an opponent on the opposite team for example

You'll need to perform all those instructions which includes disabling IPv6 and then if/once you've done that, posting here from a device connected to the R3. Right now I'm still seeing an IPv6 address so they wouldn't be able to connect.

Added but it has been temporarily removed

Added

Follow these steps exactly: If your ISP modem/router has WiFi, set it up so that it is in bridge or modem mode, you can also use the DMZ. Copy the WAN IP from the R3 (found in Settings > WAN) and enter it into the DMZ function on the ISP modem/router. Disable IPv6 in LAN/WAN on the R3 and enable remote support in Settings > Troubleshooting. Then post back here from a device connected to the R3 when you've done that and we'll attempt to connect. I can see you're still using IPv6 currently which means you haven't follow those instructions properly yet.

That is just so we can get a dev to remote in next week to look at the issue. Making those changes themselves won't fix the issue. Also I can see you still have IPv6 enabled.

That doesn't make any sense really, even in your above screenshot all those servers were allowed in your radius - what firmware version are you on with the R1? If you disable Congestion Control/QoS fully does it continue?

Added but it has been temporarily removed