Netduma Fraser

Download the firmware from here: https://support.netduma.com/firmwares/netduma-r2/ and upload it to the router like you normally would when upgrading - Settings > Troubleshooting

You've not mentioned this issue before, could you expand on this please?

My mistake, misread. Does it say in any documentation for the samba/share feature that in order to be used devices have to be connected to the router?

Oh I see, that makes more sense, well you put the share in the DMZ when you needed to put the R3 IP in the DMZ on the Asus, that may be it. Make the change and then see if you can access it when connected to the R3.

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 keep you in the radius then. Disable Mirror Mode, give 2.4/5GHz different names and apply - you'll want to connect to 5GHz specifically for speeds. Use a WiFi analyzer to find the least congested channel and change to that and experiment with the widths to see what gives better results.

The update is just for security updates so you're not missing anything/it's unlikely to fix or have caused the issues experienced. It's a long running issue that does seem to be caused by DHCP renewing. NG suspected it was an issue caused by a Nintendo Wii I think, which I am not sure how they came to that conclusion as I don't think that was being used on any of the routers we provided information for but if any of you have a Nintendo Wii or more likely a Nintendo switch try disconnecting it and see if you get the same issues.

That'll do thanks. Could you check any other device that isn't iOS/MacOS and see whether you experience the same please?

Good job! You should put the R3 WAN IP in the DMZ on your ISP modem/router. You can if you wish then put the PS5 in the DMZ on the R3.

Sounds like you're using PPPoE potentially and the ISP side ended the connection attempt. You'd have to contact them really. I would suggest checking direct to your modem first to see if the same happens.

Added - it has been temporarily removed

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. so really what I'd suggest is 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

I'm not sure if we were planning to or not but I will pass it onto the team so they can take a look

Have you set a static/reserved IP for the media server so it doesn't change? Check if the IP has changed from what you entered on the PC and update it if necessary and set the IP as reserved on the router and that should do it

Factory reset now, it's a big change from the previous version, then setup and see if you get the same issue

Presumably you're just checking the NAT on the game, if you disable the Geo-Filter before booting up the game does it appear open then?

Well I'd be biased and say the R3, I will be honest though and say there have been disconnection issues, not everyone has them by any means and they're largely resolved now but the difference is we control everything so if an issue crops up it's more likely we can fix it

If you haven't done one after upgrading then ideally you would do. If there was a backup system it wouldn't be advised to recover using a backup from a previous firmware. Reboot via the interface, close the interface, wait 4 minutes then access and check

I'd highly recommend upgrading and then you won't need to worry about that

Have you got the R3 in the Asus DMZ? You'll need to do that really I think to have it working properly

If it happens again please grab the logs prior to rebooting

To be brutually honest I don't think it is worth your time to do so. Our devs have looked at the problem before and concluded it wasn't on the DumaOS side of things and passed that information along directly to their development team. So essentially if you were to contact them about it you'd be starting at the very bottom of the totem pole and it may not reach who it needs to to get sorted anyway. Keep us posted!

The second entry isn't related, I wouldn't have thought the first one would be either. Sometimes it may take a few tries for it to connect, I'm not sure how much we've looked at it really

With the XR range these disconnections are something we've reported to NG for years, at this point I don't believe it's our side of things and usually relates to DHCP. I have noticed you've changed your LAN IP, could you change that back to the default and see if it still occurs?

Yeah we know about the lights, that entry isn't related and is harmless. Press the button, you then have a 2 minute window to connect the device, does that work?

There aren't any settings for it on the router but it should work, are you on the latest .540 firmware? https://forum.netduma.com/topic/58012-new-r3-firmware-dumaos-40540/