R2 - Disconnects from Internet/ Wired Connection

[[email protected]]

Hi - I've been asked to start a new topic about my issue which was originally posted 5/2/21. I was unaware of any response on it until a comment was made today and I was notified.

Anyway, here's my situation with as much detail as I can provide. I ordered my R2 in Nov. 2020 and it arrived around March 2021 as I recall. I connected it and all seemed fine. Then, randomly, the router would not allow me access to the internet. I would get a DNS error (browser states could not locate DNS). In troubleshooting, I did the whole unplug, let it sit, restart it, reset it, etc. It would work for a little while and then the same thing would happen - no internet.

At this point, the router is essentially a paper weight, unusable for me. I recently tried to use it again. I plugged it in and connected it. It initially worked, and then 4-6 hours later I was disconnected again. I've checked cables, etc. I have fine internet using the cable company provided modem and separate router. Here are other details.

• Latest firmware is installed
• I've tried the following configurations
  • Modem > NetDuma > Netgear 8 Hub > PC (I have separate wireless as the NetDuma doesn't cover our home. As such, wifi is disabled on it and it's just a router) I have 3 Netgear hubs in the home that all trace back to the NetDuma in this configuration. The wifi (operating off one of the Netgear 8 port hubs) is an Orbi RBR750 with a router and two satellite connections.
  • Modem > Cable Company router (no wifi) > NetDuma>Netgear 8 Hub, etc. (same as above).
  • My current configuration is Modem>Cable Company Router>Hubs (with the Orbi system as noted above). I have no issues with dropped internet. As such, I suspect it's an issue with the R2 or the R2 is doing something the cable company doesn't like and they are blocking it. The cable company has advise they do not/can't support 3rd part routers.

I have the log of the most recent connection/disconnect if it's useful. I'm not uploading it as I don't know what it contains and/or if this is a secure place to share that data. Let me know if I should upload it.

Thanks,

Travis

[Netduma Liam]

Hey Travis, thanks for posting a new topic.

To clarify, a new firmware has been released between your original post and now, so make sure you're running that (3.0.394) and also make sure you've factory reset the R2 since installing it.

After that, I'd first suggest going to Network Settings -> LAN -> DHCP and set the lease time to 168 hours. After this, change the minimum DHCP range value to .50.

Below that, go through the table of your devices and reserve an IP address for each one. Assign them IPs between the range of .2 and .49, such that they're outside of the DHCP pool.

Once done, save settings and reboot the R2 from the three-dot menu in the top right of the interface.

With regards to the log file, if you captured it after having to reboot the R2, I'm afraid it won't contain any useful information as the logs are cleared when power is lost.

[[email protected]]

I updated firmware last week when I decided to give it another go, so it's the latest as of March 10.

I had previously increased the lease time, but did not do it again after the firmware reset. I'll do that again. 

Re assigning IP addresses, which should be my focus. In today's world of IoT, there are MANY devices that run on our network. I frankly wouldn't have time to assign them all.

Re the log file, I saved it when the device lost connection again, after the new firmware update. So it won't have the prior logs, but whatever happened this go round should be included.

[Netduma Fraser]

Reserving the IP addresses is a pain but it can help, increasing the DHCP lease hours should reduce the issue to once a week if that's the cause and the reservations would fix it more permanently. We do have a new version coming soon which has a lot of fixes and improvements so that will help as well. Do provide the log and we can double check.

[[email protected]]

Log file attached.

log-1646883690730.txt

[Netduma Fraser]

Thanks for the log, there doesn't seem to be anything that I can see that would have caused it. When the disconnect happens is it after changing a setting or just completely randomly, doesn't seem to be any pattern to it? For example, does it happen when you're using a lot of bandwidth, downloading, streaming etc?

[[email protected]]

No rhyme or reason. It's happened during a zoom call as well as after sitting idle for 2-3 hours.

 

Also, I've done as instructed. Now I have no access to the internet even after resetting everything. Even tested direct from the laptop to the cable modem I'm doing a hard power reset right now. Is it possible the cable company doesn't like the R2 and is doing something on their end to throttle/disconnect me?

[[email protected]]

Reset is complete. No internet still. Current testing config is cable modem > R2 > Laptop. 

 

Laptop can access DumoOS for configuring. Under Network status I see a WAN IP 23.xxx.xxx.xxx which is consistent with my isp. Note that it was previously showing disconnected prior to the hard reset on everything on the network. 

Laptop IP matches what I set in Duma OS. 

Travis

[Netduma Fraser]

If you set devices to have a certain IP and didn't give them the one they already had then you will need to reboot the devices for them to get the new IP and get internet and then you should be good.

[[email protected]]

That was done in the reset of everything hard wired on the network. The test system right now is only 3 devices... Cable modem, R2, Laptop. No internet. 

[[email protected]]

So, I've taken the R2 out of the signal line again and everything is working fine. Reset Modem and Cable Company router. Current config is Cable Modem > Cable Router > Laptop. Internet is fine. This leads me to believe there is a issue with the router that has existed since I got it. What solutions do we have? Is there direct trouble shooting you can do by connecting directly to it? LMK what my options are please.

Travis

[Netduma Fraser]

I've sent you a PM, please check that and see if it helps.