zombiefaace Posted April 8, 2021 Share Posted April 8, 2021 Having an issue with the R2 that I don't have with my previous router at all. Several devices will randomly cut out and cannot renew DHCP without either A.) rebooting the device, or B.) rebooting the router itself. This issue does not occur when I use my old router, and it's only about 3 out of the 13 devices I have. Oddly I have not experienced this issue at all on my gaming PC which is online 24/7/365 either mining cryptocurrency or gaming. Here's everything I've done so far: Computer loses network connection Run ipconfig /release, ipconfig /flushdns, ipconfig /renew ipconfig /renew states it can't get an IP from DHCP Reboot computer, if that doesn't work, reboot router Have changed LAN cables on all 3 devices with brand new LAN cables Have downloaded and installed the latest drivers for the NIC on the 2 PC's affected Windows 10 is fully up to date on the latest version and security patches WiFi devices do not seem to be affected at all. Gaming wired PC is not affected at all IP's are static assigned to devices inside the NetDuma R2 interface Have not tried static assigning IP's on the devices themselves. Prefer not to do it this way Streaming PC that was affected seems to not experience the issue anymore, but hard to tell as it's mostly off until I go live, so only online a few hours a day at most Gaming PC is never affected, and usually used to do all reboots and checks through the GUI of the router interface. When Security Cams and 1 PC are affected I can see them in the Device Manager part of the GUI constantly jumping back and forth between offline and online. Setting 100Mbps/1000Mbps full duplex on any PC seems to actually cause this issue (with the exception being the gaming PC) so for now devices are set to auto negotiation Currently have the router plugged into the modem with the modem configured in bridge mode so that the router gets the external IP + DMZ 1 24 port switch is plugged into the router. Have tried all devices behind the switch with each individual port on the router, issue occurs regardless of port on router used. Have tried devices plugged directly into router (doing that right now) At this point I'm at my wits end, I've tried moving everything completely over to the switch so only 1 cable comes out of the R2 router, I've tried updating drivers and swapping cables to no luck, as soon as I move everything back over to my ASUS RT-AC68U all the issues stop completely. Hoping it's just a firmware bug, currently running the latest firmware version 3.0.205, can't see how it'd be anything else just to it being localized to only 3 devices, can provide hardware specs (to the best of my ability) of each device if needed. Thanks for your time Link to comment Share on other sites More sharing options...
Netduma Liam Posted April 9, 2021 Share Posted April 9, 2021 Welcome to the forum! Sorry to hear thank, thank you for the great detail! As you're able to access the interface when this happens, we may be able to see some useful information in the logs about it. Next time it happens, could you please go to System Information and save the log file before restarting anything or getting the devices back online? Could you also please just clarify exactly which devices are experiencing this issue? Your streaming PC (though not recently) and two security cameras? Are there any others devices affected? zombiefaace 1 Link to comment Share on other sites More sharing options...
zombiefaace Posted April 9, 2021 Author Share Posted April 9, 2021 I can absolutely pull the log file, just curious how long does the log file record data for? Is there a limit? Sometimes this will happen with a device when I'm at work, and well, work is 45 miles from home Link to comment Share on other sites More sharing options...
Netduma Liam Posted April 9, 2021 Share Posted April 9, 2021 Awesome, thank you. Logs go back about 12 hours approximately, so hopefully you'll be able to capture something! It would be ideal if you could estimate what time approximately the connections dropped, but I can appreciate that may be difficult. zombiefaace 1 Link to comment Share on other sites More sharing options...
zombiefaace Posted April 9, 2021 Author Share Posted April 9, 2021 Thanks! Next question, how would I upload the logs? Just need me to copy and paste in a text file and upload into the thread? Link to comment Share on other sites More sharing options...
zombiefaace Posted April 9, 2021 Author Share Posted April 9, 2021 Nevermind that, I found out how to download the logs, here's something I found in the logs (not sure this would be related) I'm trying to get someone at home to turn on 1 PC right now to see if I can get it to have the issue Fri Apr 9 06:49:46 2021 user.info com.netdumasoftware.neighwatch: DHCP new event. Fri Apr 9 06:49:46 2021 user.info com.netdumasoftware.neighwatch: DHCP new lease allocated. Fri Apr 9 06:49:49 2021 daemon.err cli.lua[2914]: Command failed: Not found Fri Apr 9 06:49:50 2021 daemon.err cli.lua[2914]: Command failed: Not found Fri Apr 9 06:49:51 2021 daemon.err cli.lua[2914]: Command failed: Not found Fri Apr 9 06:49:51 2021 daemon.err cli.lua[2914]: Command failed: Not found Fri Apr 9 06:49:51 2021 daemon.err cli.lua[2914]: Command failed: Not found Fri Apr 9 06:50:00 2021 cron.err crond[1401]: USER root pid 4697 cmd echo 3 > /proc/sys/vm/drop_caches Also, I don't know why, but it looks like it's spamming a new IP check for the DHCP lease every 5 or so minutes on the WAN, is this normal? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted April 9, 2021 Administrators Share Posted April 9, 2021 Do you have a pure modem or modem/router? If the latter I would suggest setting a static/reserved IP for the R2 and that could help if that's the issue. Link to comment Share on other sites More sharing options...
zombiefaace Posted April 9, 2021 Author Share Posted April 9, 2021 5 hours ago, Netduma Fraser said: Do you have a pure modem or modem/router? If the latter I would suggest setting a static/reserved IP for the R2 and that could help if that's the issue. It's not a Pure, it's an Arris, but the router is set in bridge mode with the modem, so that it's automatically DMZ'd and the modem is essentially a dumb switch, I'd rather not double NAT if possible. Even with that I don't see how that'd be related so I have no issues accessing the internet, just issues with 3 devices randomly disconnecting and losing local IP's from the R2 itself. Link to comment Share on other sites More sharing options...
zombiefaace Posted April 10, 2021 Author Share Posted April 10, 2021 13 hours ago, Netduma Liam said: Welcome to the forum! Sorry to hear thank, thank you for the great detail! As you're able to access the interface when this happens, we may be able to see some useful information in the logs about it. Next time it happens, could you please go to System Information and save the log file before restarting anything or getting the devices back online? Could you also please just clarify exactly which devices are experiencing this issue? Your streaming PC (though not recently) and two security cameras? Are there any others devices affected? Ok so my next reply I'm going to post the log, I hope you don't mind but I used Notepad ++ to scrub my public IP address from the log file for security/safety reasons, not too concerned about internal IP's/PC names. I did see the bouncing back and forth from offline to online behavior in the router GUI and can confirm it in the logs as shown here Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.337485] mtk_soc_eth 1e100000.ethernet eth0: gsw irq, link status reg=0x20080008 Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.352910] mtk_soc_eth 1e100000.ethernet eth0: MAC0: control=0x56330 status=0xb Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.367961] mtk_soc_eth 1e100000.ethernet eth0: MAC1: control=0x56330 status=0xb Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.383011] mtk_soc_eth 1e100000.ethernet eth0: MAC2: control=0x56330 status=0x0 Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.398060] mtk_soc_eth 1e100000.ethernet eth0: MAC3: control=0x56330 status=0x0 Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.412939] mtk_soc_eth 1e100000.ethernet eth0: port 3 link down Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.425052] mtk_soc_eth 1e100000.ethernet eth0: MAC4: control=0x56330 status=0xb Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.440104] mtk_soc_eth 1e100000.ethernet eth0: MAC5: control=0x5e30b status=0xb Fri Apr 9 18:40:10 2021 kern.info kernel: [65918.455153] mtk_soc_eth 1e100000.ethernet eth0: MAC6: control=0x5e30b status=0xb Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.755732] mtk_soc_eth 1e100000.ethernet eth0: gsw irq, link status reg=0x80008 Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.770635] mtk_soc_eth 1e100000.ethernet eth0: MAC0: control=0x56330 status=0xb Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.785689] mtk_soc_eth 1e100000.ethernet eth0: MAC1: control=0x56330 status=0xb Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.800744] mtk_soc_eth 1e100000.ethernet eth0: MAC2: control=0x56330 status=0x0 Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.815796] mtk_soc_eth 1e100000.ethernet eth0: MAC3: control=0x56330 status=0x3 Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.830675] mtk_soc_eth 1e100000.ethernet eth0: port 3 link up Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.842442] mtk_soc_eth 1e100000.ethernet eth0: MAC4: control=0x56330 status=0xb Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.857492] mtk_soc_eth 1e100000.ethernet eth0: MAC5: control=0x5e30b status=0xb Fri Apr 9 18:40:12 2021 kern.info kernel: [65920.872542] mtk_soc_eth 1e100000.ethernet eth0: MAC6: control=0x5e30b status=0xb Fri Apr 9 18:40:13 2021 kern.info kernel: [65921.856482] mtk_soc_eth 1e100000.ethernet eth0: gsw irq, link status reg=0x80008 Fri Apr 9 18:40:13 2021 kern.info kernel: [65921.871404] mtk_soc_eth 1e100000.ethernet eth0: MAC0: control=0x56330 status=0xb Fri Apr 9 18:40:13 2021 kern.info kernel: [65921.886475] mtk_soc_eth 1e100000.ethernet eth0: MAC1: control=0x56330 status=0xb Fri Apr 9 18:40:13 2021 kern.info kernel: [65921.901532] mtk_soc_eth 1e100000.ethernet eth0: MAC2: control=0x56330 status=0x0 Fri Apr 9 18:40:13 2021 kern.info kernel: [65921.916584] mtk_soc_eth 1e100000.ethernet eth0: MAC3: control=0x56330 status=0x0 Fri Apr 9 18:40:13 2021 kern.info kernel: [65921.931462] mtk_soc_eth 1e100000.ethernet eth0: port 3 link down I did have an issue with this PC being offline last night, but alas it was before I read your comment and I ended up doing several reboots of both the PC and the router, so I didn't get a chance to record that data. For another test I went ahead and put this PC (named evilinside2 in the logs) on a static IP on the system itself instead of assigning it from the router. Not sure if this is what this snipet of code is referring too or not. Fri Apr 9 19:01:55 2021 user.info com.netdumasoftware.neighwatch: DHCP new event. Fri Apr 9 19:01:55 2021 user.info com.netdumasoftware.neighwatch: DHCP lease change. Fri Apr 9 19:01:55 2021 daemon.err miniupnpd[2525]: try_sendto failed to send 12 packets Fri Apr 9 19:01:57 2021 daemon.err cli.lua[2914]: Command failed: Not found Fri Apr 9 19:02:25 2021 daemon.err miniupnpd[2525]: try_sendto failed to send 12 packets Fri Apr 9 19:02:40 2021 daemon.err odhcp6c[7030]: Failed to send DHCPV6 message to ff02::1:2 (Address not available) Fri Apr 9 19:02:55 2021 daemon.err miniupnpd[2525]: try_sendto failed to send 12 packets Fri Apr 9 19:03:20 2021 daemon.info dnsmasq-dhcp[9415]: DHCPREQUEST(br-lan) 192.168.1.150 60:45:cb:9a:3a:6e Fri Apr 9 19:03:20 2021 daemon.info dnsmasq-dhcp[9415]: DHCPACK(br-lan) 192.168.1.150 60:45:cb:9a:3a:6e evilinside2 Fri Apr 9 19:03:25 2021 daemon.err miniupnpd[2525]: try_sendto failed to send 12 packets Fri Apr 9 19:03:29 2021 daemon.info dnsmasq-dhcp[9415]: DHCPRELEASE(br-lan) 192.168.1.150 60:45:cb:9a:3a:6e Fri Apr 9 19:03:29 2021 user.notice com.netdumasoftware.neighwatch: Unknown DHCP event 'remove' Fri Apr 9 19:03:33 2021 daemon.info dnsmasq-dhcp[9415]: DHCPDISCOVER(br-lan) 192.168.1.150 60:45:cb:9a:3a:6e Fri Apr 9 19:03:33 2021 daemon.info dnsmasq-dhcp[9415]: DHCPOFFER(br-lan) 192.168.1.150 60:45:cb:9a:3a:6e Fri Apr 9 19:03:33 2021 daemon.info dnsmasq-dhcp[9415]: DHCPREQUEST(br-lan) 192.168.1.150 60:45:cb:9a:3a:6e Fri Apr 9 19:03:33 2021 daemon.info dnsmasq-dhcp[9415]: DHCPACK(br-lan) 192.168.1.150 60:45:cb:9a:3a:6e evilinside2 Thanks for all your help so far! Link to comment Share on other sites More sharing options...
zombiefaace Posted April 10, 2021 Author Share Posted April 10, 2021 As requested here is a copy of my log file with my public IP address scrubbed. Please let me know if you need anything else log-1618019597453-N++.txt Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted April 10, 2021 Administrators Share Posted April 10, 2021 If you took it out of bridge mode and used the DMZ instead you wouldn't get a double NAT. Thank you for the logs. On the affected PC, as a test can you disable flow control on the ethernet adapter then reboot the device and see whether the issue continues on that device please? Link to comment Share on other sites More sharing options...
zombiefaace Posted April 11, 2021 Author Share Posted April 11, 2021 5 hours ago, Netduma Fraser said: If you took it out of bridge mode and used the DMZ instead you wouldn't get a double NAT. Thank you for the logs. On the affected PC, as a test can you disable flow control on the ethernet adapter then reboot the device and see whether the issue continues on that device please? Enabling bridge mode disables all DHCP and routing functions of the modem and automatically puts the R2 into DMZ mode, thus why I had to remove the public IP from the logs as it's assigned directly to the R2's WAN port, this is not a double NAT. As far as the flow control I've gone ahead and disabled it on 1 of the 3 devices that are affected to see if this will affect anything for this device while the other 2 are still operating normally with no changes. May take a while to experience this issue as this isn't something that always happens daily, will continue monitoring the logs and report back anything that happens or any changes. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted April 11, 2021 Administrators Share Posted April 11, 2021 Yeah I know, I was just responding to you not wanting to take it out of bridge and have a double NAT. Okay great thanks very much, if that works then we may need to disable this on the R2 so the other 2 devices can be fixed as well, we can probably get a dev to remote in and change this on your router specifically. Lets see what happens. zombiefaace 1 Link to comment Share on other sites More sharing options...
zombiefaace Posted April 11, 2021 Author Share Posted April 11, 2021 8 hours ago, Netduma Fraser said: Yeah I know, I was just responding to you not wanting to take it out of bridge and have a double NAT. Okay great thanks very much, if that works then we may need to disable this on the R2 so the other 2 devices can be fixed as well, we can probably get a dev to remote in and change this on your router specifically. Lets see what happens. Sure no problem, I'll try to keep the streaming PC on as much as possible even if I'm not using it to see if it will happen a little faster, unfortunately it has RGB RAM that I can't change the color of (known issue with the current BIOS, waiting on an update) so I won't be able to keep it on over night as it's in my room and quite bright, but in the mean time I can ping -t the streaming PC the whole time to see if there are any recorded drops, I'll have it output to a txt file so I can check it over time and see about what time it occurs for the log file time stamp Netduma Fraser 1 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now