Uncle_Steve Posted May 5, 2021 Share Posted May 5, 2021 R2 will intermittently block all WAN connections for both wired and wireless devices. Modem is inaccessible via R2 but still connected to the Internet. Rebooting R2 "fixes" the issue, modem remains up. Normally occurs ever 2-5 days, but can happen several times on the same day. It happens more frequently when QoS is set to "Always", less frequently when set to "Auto-detect" - and from memory, has never crashed when QoS is set to "Off". (E.g. Crashed this morning, 13 hours after moving from Auto-detect to Always on QoS) It also happens more frequently after heavy streaming/downloading - but perhaps that is because I have to change the QoS mode. Log file shows some out of memory issues - possible memory leak on QoS component? Appreciate the help! -- Uncle Steve Link to comment Share on other sites More sharing options...
Netduma Liam Posted May 5, 2021 Share Posted May 5, 2021 Awesome, thanks @Uncle_Steve! You're right, there's a couple things there I want to investigate, I've grabbed your log and removed it from the post for good measure. We're going to dive into this now so I'll get back to you once we've got an update! Link to comment Share on other sites More sharing options...
Netduma Liam Posted May 5, 2021 Share Posted May 5, 2021 @Uncle_Steve How many devices do you have connected roughly, is it a particularly large amount? Do you have any particularly long ethernet cables in use? Or maybe any old cables? Are any of them twisted/bent/kinked at all or running through areas where there may be other noies/interference? I think you've already confirmed this, but do you leave the interface open for long periods of time? Link to comment Share on other sites More sharing options...
Uncle_Steve Posted May 6, 2021 Author Share Posted May 6, 2021 The router has crashed 2 more times this morning - each one having QoS set to "Always". (Logs attached) Wired: 5m Ethernet - Samsung Smart TV 5m Ethernet - Gaming PC 1m Ethernet - Apple Airport Express Wireless: 2x iPhone 2x iPad 4x Macbook pro log-1620297113178.txt log-1620293517510.txt Link to comment Share on other sites More sharing options...
Netduma Liam Posted May 6, 2021 Share Posted May 6, 2021 Sorry to hear that Steve, thanks for the information. I'll pass your logs over to the devs and we'll look into it! Link to comment Share on other sites More sharing options...
Uncle_Steve Posted May 6, 2021 Author Share Posted May 6, 2021 It crashed again. 3rd time today! I've turned QoS off to see if that changes things. log-1620311592343.txt Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted May 6, 2021 Administrators Share Posted May 6, 2021 Okay thank you, do keep us posted! Link to comment Share on other sites More sharing options...
Uncle_Steve Posted May 19, 2021 Author Share Posted May 19, 2021 Router crashed again 3 times this morning - mainly during Zoom/Google Meet calls. Any updates? Link to comment Share on other sites More sharing options...
Netduma Liam Posted May 19, 2021 Share Posted May 19, 2021 17 minutes ago, Uncle_Steve said: Router crashed again 3 times this morning - mainly during Zoom/Google Meet calls. Any updates? Sorry to hear that, I'll chase this one up with the devs and see where we are with it. Link to comment Share on other sites More sharing options...
Uncle_Steve Posted May 20, 2021 Author Share Posted May 20, 2021 Crashed 8 times yesterday and again this morning with QoS set to disabled. On this morning's crash my wired PC (which was off at the time) was unable to get an IP address when I started it up though it detected it as a gateway (but unable to access the console). My laptop (which was on at the time of the "crash") was able to get into the console. So it looks like DHCP had locked-out. Have reverted back to v0.123 with QoS disabled and it's been fine so far. log-1621503254154.txt Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted May 20, 2021 Administrators Share Posted May 20, 2021 So that log file is prior to a reboot so while the issue was on going? That kernel gap is huge, next time if possible, order the Memory (P) column to show the highest first Link to comment Share on other sites More sharing options...
Uncle_Steve Posted May 21, 2021 Author Share Posted May 21, 2021 Yes, both of those are whilst the issue was ongoing (prior to a reboot). Link to comment Share on other sites More sharing options...
Netduma Liam Posted May 21, 2021 Share Posted May 21, 2021 Just now, Uncle_Steve said: Yes, both of those are whilst the issue was ongoing (prior to a reboot). Thanks for this, I'll make the devs aware! Link to comment Share on other sites More sharing options...
Uncle_Steve Posted June 2, 2021 Author Share Posted June 2, 2021 NOTE: Running an Old version Version: v3.0.123 Another incidence of the same crash. No internet / WAN connection. Console was still accessible (even by WiFi) but CPU at nearly 100% on all 4 cores. QoS set to “Never”. Lasted a lot longer between crashes than when using “Always” or “Auto-Enable”. (A week vs. Hours or days respectively) Logs seem to indicate an out of memory fault. And I know the CPU-issue was fixed in a later release (0.179?)... log-1622661449440.txt Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted June 2, 2021 Administrators Share Posted June 2, 2021 We're actively utilizing a router we can reproduce this on and connecting the information we need, it's been very hard to tell what the cause is so we've created background tools that will help us narrow this down, hopefully won't be too much longer. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.