Netduma Fraser

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/

It will be very hard to diagnose the problem without access and getting the logs. Perhaps leave it disabled for now, see how it runs for a few days, a day could be a fluke/coincedence, a few days would then definitely be a pattern

Can you expand on the Geo-Filter not working exactly? What are your WiFi settings? Access from the WAN has never been an option on the R3. Can you clarify the loop of death? How do you have WiFi set, have you adjusted the settings manually? You may need to experiment with the widths/channels to get the best result. If you could provide the logs for when they disconnect that would be really helpful Do you have Geo-Latency or Ping Assist enabled? Thank you, there are some entries I haven't seen before so this should be helpful Great to hear, thanks for the update!

Change to 40MHz for the width on 2.4GHz, what speed do you get then?

If you could grab the logs from when it happens while DHCP is disabled that may help narrow down the issue more

Are you actually playing on the Wii? You're on a very old firmware that isn't really supported, best to upgrade to this version: https://forum.netduma.com/topic/35821-new-r1-firmware-30207/ which is more current

What about in a different port on the router?

I don't think the router can tell its online properly, do you have BI enabled on the router?

Ah I see, good idea, I'll pass it on!

What do you mean by resetting exactly? Do you still have access to the modem when it happens?

I meant there isn't anything in the logs that indicates an issue. Have you changed anything else in your physical setup or settings wise on your modem etc prior to it not working?

I think that was likely to be a conincedence, with DHCP off you would either have a connection or you wouldn't, it wouldn't affect the quality of the connection. By the looks of it the router thinks it's being attacked when it isn't. Try it again and reboot after you've disabled it and monitor.

Yes I think now would be best to try it with DHCP disabled and see if it continues please, you don't need to set anything else up to use DHCP yet. As you've done the reserved IPs they should all be able to connect just fine.

Check with another ethernet cable, also into a different port on the R3, can it connect then?