Netduma Fraser

Thanks for that, although given you've rebooted and the error isn't present it won't indicate anything unfortunately. How often does it seem to occur? Is there any pattern you can see as to when it happens e.g. after a few days, when changing a specific setting or using lots of bandwidth etc

Hold the reset button for 30 seconds, release, wait 2 minutes then access, go through the wizard then see if it is working. A factory reset is a good idea after an update as it removes any remnants from the previous version that may linger and cause issues.

Did you do a proper factory reset after the update? I know you said you reset but do you mean a factory reset or a reboot?

By WAN IP in this case we mean your public IP address, so if the IP is the same as what you gave us we'll use that, otherwise the forum provides us with your IP so we can use that instead. I think it's just a case of us checking the logs each time it happens to see if there are any indications. However, one of your last points could be it, you said you had disabled all DNS settings on the R2, do you mean you unticked Use Upsteam DNS and didn't enter any manual ones? If so that could be a reason - DNS is important and so it should be set one way or another.

Thanks for letting us know, Liam has been off sick the last few days so I'll get him to look at it when he is back. It's likely the WAN IP of the R2 has changed since it has been off and so the DMZ on the modem is invalid, double check the IP then put it in the DMZ again on the modem and you should get an Open NAT.

The router on it's own won't cause issues like that, more likely settings need to be altered. Make a new topic with your setup details and screenshots of the settings you're using and we can advise from there.

Thanks, you too!

As it's late and the weekend now (based in the UK) Liam won't be able to check this until Monday so go ahead and reset it so you have normal internet and we'll still have the info

No worries about that, as we've enabled remote logging we'll have detailed logs on our end, I'll pass it on for Liam to have a look.

Just toggle Filtering Mode off on the Geo-Filter page

Disable the Geo-Filter as we haven't tested that game at all, then it should work just fine

Unplug the router from power for 10 minutes, plug in, wait 2 minutes, attempt access, if it doesn't work hold the reset button for 30 seconds, then wait 2 minutes before accessing the interface

Is that using the default credentials: Username: admin Password: password

Bem-vindo ao fórum! Reproduzimos o problema e o transmiti à equipe para dar uma olhada, espero que seja um problema de nuvem que possamos corrigir rapidamente sem uma atualização de firmware.

Did you do a factory reset after the upgrade? If not please do so and see whether that resolves the disconnects. We have reproduced the location issue and I've passed it onto the team to have a look at.

Gaming requires very little bandwidth, you don't need to assign much to it - I would assign more to streaming, don't forget about Congestion Control as well - that will prevent your game lagging while streaming

Congestion Control you can experiment with, we always suggest starting at 70%. Based on this: https://stream.twitch.tv/encoding/ you need 3000-6000Kbps (3-6Mbps) upload to stream between 720p - 1080p quality. So for example if you have 10Mbps upload you would assign 30 - 60% to the streaming device.

@BulCongestion Control applies to the entire network to prevent local congestion so I would recommend still having that enabled but you could disable Traffic Prioritization and that will stop the game being prioritized. You could also assign bandwidth to the streaming device via Bandwidth Allocation - have a look at what Twitch recommend for upload depending on what quality you're going to stream and then assign the necessary bandwidth.

That would be very cool! With designs like that you are relying on the internal antennae and not being able to move them could result in poorer WiFi performance. Maybe in the future! Awesome but the copyright lawsuits that follow it would not be 😂

Welcome to the forum! Did you factory reset after installing .134? If not please do so and see if that resolves the issue.

My 2cents on that would be that generally routers are kept in corners or out of sight so spending more money on the design of something makes less sense than putting that money into the internals or software.

It'll be something we'll have to look into then, for the moment you'll have to manually reconnect it.

Just to confirm, are you saying the same thing happens when you just do a normal reboot from the interface?

How do you restart it, by the interface, button or unplugging the router? Setup the VPN so it is connected, reboot from the interface, wait 2 minutes and then see if it is still connected. If it is, see if it is connected when you next turn it on.

I mean how long do you leave it off, did you leave it off for 6 hours before the issue and then 8 hours and the issue started for example