Jump to content

Random WAN/Internet disconnects


qBlix
 Share

Recommended Posts

Hey Support,

I started having random lag spikes in games (about a week ago) -- after troubleshooting a bit it seems like it may be the R2 router.

At first, I thought it was Spectrum but speeds on the modem show above 900+ Mbps.

Speeds on the Connection Benchmark show at 400Mpbs but with QoS at the actual speeds, I show I'm getting the speeds I pay for on speed tests sites if the connection doesn't randomly drop causing the test to fail. (I don't care about speed but more about the connection quality)

On the modem, the WAN side appears to be stable no disconnects, and things just work.
Wan internet:
Spectrum Gig COAX (920 DOWN / 40 UP)

I have pinged the following on loop for testing.

Loopback IP (<1ms -- no drops)
Internal IP: 10.0.92.1 (<1ms response -- no drops)
Public IP (<1ms response -- no drops)
Ping to 8.8.8.8 (~20ms -- drops occur here and there with R2 logging ***daemon.err cfront bottomch[8349]: Reloading interface IPs***)
Ping to google.com (~20ms -- drops occur here and there with R2 logging ***daemon.err cfront bottomch[8349]: Reloading interface IPs***)

I've tried:
Troubleshooting with ISP confirming the speeds and signal levels are strong
Just to be on the safe side - Modem, Uplink cables, etc. have been replaced except for the R2
Different DNS settings although pings prove this isn't a DNS issue
Adjusting QoS setting (On -- Fully disabled)
WAN and LAN (IPv6 on or off)
Disabling WAN protections
Rule to allow prioritized traffic on all ports going to the computer I'm utilizing
Hard resetting R2 (on the last 3 firmware currently on R2 3.3.280) and configuring again from scratch as basic as possible LAN default QoS settings and testing
Disconnects are not computer specific and happen at the same time on all LAN devices

Every time the disconnects happen I see the following in the logs: (attached .txt file with longer log)
Fri Apr  7 19:06:41 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:06:34 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:06:27 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:06:21 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:06:17 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:06:11 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:06:02 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:59 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:47 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:42 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:36 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:33 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:28 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:21 2023 daemon.notice miniupnpd[15014]: Listening for NAT-PMP/PCP traffic on port 5351
Fri Apr  7 19:05:21 2023 daemon.notice miniupnpd[15014]: HTTP listening on port 5000
Fri Apr  7 19:05:21 2023 daemon.notice miniupnpd[14462]: shutting down MiniUPnPd
Fri Apr  7 19:05:20 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:20 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:10 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:07 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:02 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:05:00 2023 kern.info kernel: [16815.959056] ash (14589): drop_caches: 3
Fri Apr  7 19:05:00 2023 cron.err crond[2907]: USER root pid 14589 cmd echo 3 > /proc/sys/vm/drop_caches
Fri Apr  7 19:04:57 2023 daemon.notice miniupnpd[14462]: Listening for NAT-PMP/PCP traffic on port 5351
Fri Apr  7 19:04:57 2023 daemon.notice miniupnpd[14462]: HTTP listening on port 5000
Fri Apr  7 19:04:57 2023 daemon.notice miniupnpd[13770]: shutting down MiniUPnPd
Fri Apr  7 19:04:56 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs
Fri Apr  7 19:04:56 2023 daemon.err cfront bottomch[8349]: Reloading interface IPs

I've spent hours going through forums and my issues are still present. Would someone be able to assist any further?

Thank you in advance!

DumaOS.png

pings.png

log-1680912540686.txt

Link to comment
Share on other sites

  • Administrators

Welcome to the forum!

Sorry to hear you're having this issue, what is the model of the modem/router the R2 is connected to? Looks like rather than spikes its that you're timing out, do you have another ethernet cable you can try to connect the R2 to the modem with to see if it still occurs?

Link to comment
Share on other sites

It looks like it may be port 1 and port 4 on the R2 causing issues.
I had a camera system and climate control on the port 2-3
PC and AP on 1 and 4

I bought a PoE switch and was able to switch everything including AP to the switch for now things seem a bit more stable.

Link to comment
Share on other sites

Yeah, it's very odd that ports 1 and 4 are both having issues on the R2. This started happening about a week ago after the most recent firmware update. I tried different firmware but the same thing still happens now even after hard resetting.

The modem is a HiTron DOCSIS EN2251-RES Cable Modem.

Link to comment
Share on other sites

  • Administrators

If you sign up to Early Access https://forum.netduma.com/topic/39415-introducing-early-access/ you could try the firmware there, it's different than what you're using currently so if you're not happy with that change, you could downgrade but might be worth a try to at least to see if it is somehow firmware related

 

Link to comment
Share on other sites

So the time out's have been solved but there seems to be a weird jitter issue still.

We use a few chromecast's in the house for a while now. I've noticed that Disney+ takes up a lot of bandwidth.

 

It will randomly spike up the download speed and every time it spikes it will cause random jitter. It seems to be consistent at around 15-second intervals

Link to comment
Share on other sites

  • Administrators
32 minutes ago, qBlix said:

So the time out's have been solved but there seems to be a weird jitter issue still.

We use a few chromecast's in the house for a while now. I've noticed that Disney+ takes up a lot of bandwidth.

It will randomly spike up the download speed and every time it spikes it will cause random jitter. It seems to be consistent at around 15-second intervals

Good progress! Is that with Download reduced using Congestion Control as well?

Link to comment
Share on other sites

Correct, the speeds are set to that of the provider 920/40

 

The QoS is set to download to 50% currently and it doesn't seem to have an effect. Regardless of the setting when Disney+ is on it seems to add latency to the network.

Link to comment
Share on other sites

  • Administrators
55 minutes ago, qBlix said:

Correct, the speeds are set to that of the provider 920/40

 

The QoS is set to download to 50% currently and it doesn't seem to have an effect. Regardless of the setting when Disney+ is on it seems to add latency to the network.

Have you disabled Media as that default setting will prioritize Disney+

Link to comment
Share on other sites

How would you go about disabling the media prioritization?

 

I've lowered media and it doesn't seem to affect it.

Currently, have 3 prio rules set.

1. Default "DumaOS Classified Games"

2. Work from home

3. Custom rule to my computer prioritizing all ports

Link to comment
Share on other sites

  • Administrators

Click on the yellow star on the right to unprioritize it, sounds like you may have done so already, you could have Gaming and Work from Home enabled, prioritizing all ports to a device shouldn't be necessary

Link to comment
Share on other sites

I'm not seeing a yellow star to unprioritize "Media". 

 

What I did do was disabled all prioritization rules and I used Valorant as an example.

Created a new rule for my computer with the "Valorant" game selected.

 

I didn't see any change in jitter with those changes above.

Limited Media to 5 Mbps and noticed some differences; a lot less lag although still randomly present but then we are unable to use TV streaming while playing games and such.

 

Although with pings I'm not getting any more WAN drops (time outs).

There are still errors in the logs it seems when I'm seeing the jitter.

 

Log:

Sun Apr  9 18:48:00 2023 daemon.notice miniupnpd[23737]: Listening for NAT-PMP/PCP traffic on port 5351
Sun Apr  9 18:48:00 2023 daemon.notice miniupnpd[23737]: HTTP listening on port 5000
Sun Apr  9 18:47:59 2023 daemon.notice miniupnpd[23451]: shutting down MiniUPnPd
Sun Apr  9 18:47:59 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:59 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:56 2023 daemon.notice miniupnpd[23451]: Listening for NAT-PMP/PCP traffic on port 5351
Sun Apr  9 18:47:56 2023 daemon.notice miniupnpd[23451]: HTTP listening on port 5000
Sun Apr  9 18:47:56 2023 daemon.notice miniupnpd[22685]: shutting down MiniUPnPd
Sun Apr  9 18:47:55 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:55 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:52 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:41 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:34 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:31 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:23 2023 daemon.err ctwatch[2744]: Reloading interface IPs
Sun Apr  9 18:47:20 2023 daemon.notice miniupnpd[22685]: Listening for NAT-PMP/PCP traffic on port 5351
Sun Apr  9 18:47:20 2023 daemon.notice miniupnpd[22685]: HTTP listening on port 5000
Sun Apr  9 18:47:20 2023 daemon.notice miniupnpd[22396]: shutting down MiniUPnPd

 

 

 

Link to comment
Share on other sites

  • Administrators

Thanks for that, looks like you've updated to the Early Access version that we actually posted as a public firmware update recently which is fine. 

Reset Bandwidth Allocation completely, then It's best to start with a high value for Congestion Control, say 95% then do a Connection Benchmark test, decrease by 10%, test, decrease by 10% etc, until you get to a value that is pretty good for Ping Under Load (as close to the Ping test values) and then try 5% either side of that value to see if it can be improved. It's important to note that Download & Upload on Congestion Control don't have to be the same value and that you may have a better experience with differing values. See if that eliminates the issues you're having once it's been fine tuned.

Link to comment
Share on other sites

Even after optimizing something is still weird about it.

The upload is skyrocketing randomly. I plug in my old Nighthawk R8000 and everything is fine.

 

I'm going to try to reset it with the pinhole for the 5th time after replacing all the cables again from Saturday.

connection benchamark after.png

connection benchamark before.png

Link to comment
Share on other sites

Hello @Netduma Fraser I happened to look at Ops logs.. He is actually suffering from UPNP starting and shutting down over and over.. The same issue that was found with me.. We might need to get an update on this issue from the Dev that was checking this out..  If you look closely at his log he downloaded you will see the pattern arise in his logs..  Specially towards the end of his log..

Figured Id point that out.

Thanks!

Zippy.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...