I hope when folks are saying the term "REBOOT" they are talking about an actual REBOOT and not something else that may be very similar.
These threads get so mangled and confused when folks start using a common term for every issue they have.
I'm not pointing a finger but the importance of accuracy when describing your issues can't be ignored.
If the info is accurate the issue will be resolved much faster.
The implied term "REBOOT" that has been said is regards to the router actually rebooting due to it having a critical crash of the software. (common terms are kernel panic due to backend is a flavor of linux).
Wireless devices get confused when the 2.4GHz and 5GHz SSID is the same. I always use a different one for each. This is not a fault of the router firmware. Can use the same passphrase. I like have different so that I know for sure the device will always use the same wireless, 2.4 or 5.
yeah, I learned that recently actually. I mean, right now I only have mine set to the default dd-wrt for all adapters, because I'm focusing on the reboots rather than attempting to get my wireless working.
My issues with wireless are even with the networks being named and secured differently(different ssid, different password)
We're on about a day now, and no reboots! definitely seems that disabling SFE makes a huge difference. I don't know if it's the -cause- of the issue, but it certainly doesn't help matters.
I'm going to give it another day to be safe, then I'll start poking at my wireless to see if I can get a stable setup going. I'm at the point now where I'm going to try every single possible variation of wireless settings xD
gonna take hours.
Joined: 18 Aug 2009 Posts: 597 Location: Antigua/Seattle
Posted: Mon Jul 24, 2017 3:04 Post subject:
rds2017 wrote:
aairon wrote:
I hope when folks are saying the term "REBOOT" they are talking about an actual REBOOT and not something else that may be very similar.
These threads get so mangled and confused when folks start using a common term for every issue they have.
I'm not pointing a finger but the importance of accuracy when describing your issues can't be ignored.
If the info is accurate the issue will be resolved much faster.
The implied term "REBOOT" that has been said is regards to the router actually rebooting due to it having a critical crash of the software. (common terms are kernel panic due to backend is a flavor of linux).
I hope you can bare with me here I'm not real clear about what you said so maybe you can tell me if my assumption when spoken about on these threads of a reboot is incorrect and maybe I have to reassess my thinking about what folks are talking about.
I have been under the assumption that a reboot is anytime the base firmware cycles through the BOOT CODE in the firmware (Caused by ANYTHING from code errors or intentional, in this case unintentional)), many times followed by some familiar LED activity changing colors and evidence that Temp files are gone.
So am I wrong The sooner I know the better off I am. Thanks for your input I think it's painfully obvious I know very little about Linux.
Joined: 30 May 2017 Posts: 3 Location: Portland, OR
Posted: Mon Jul 24, 2017 6:16 Post subject:
135 pages into this thread, and still counting Thanks for all the great work. My router seemed doomed, initially, but it has been running pretty good now for, what, a few months?
There is, though, the occasional hickup. Tonight I fell the need to reboot (lost WAN connection), then again an hour later, then seemingly the router not coming up anymore, so that I unplugged and plugged back in the power.
As a software developer, I'm a pretty technical user, but Linux networking isn't my strength. And I could use some pointers in troubleshooting this. More specifically: in being ready to troubleshoot this when it happens again.
I've enabled the syslog, but what other tools should I have ready to go, and what information should I capture before rebooting? (If I get a chance.)
Maybe there's some steps described in one of the 134 previous pages, feel free to point me there.
Much appreciated, Sander. _________________ Owner of a Linksys WRT3200ACM
135 pages into this thread, and still counting Thanks for all the great work. My router seemed doomed, initially, but it has been running pretty good now for, what, a few months?
There is, though, the occasional hickup. Tonight I fell the need to reboot (lost WAN connection), then again an hour later, then seemingly the router not coming up anymore, so that I unplugged and plugged back in the power.
As a software developer, I'm a pretty technical user, but Linux networking isn't my strength. And I could use some pointers in troubleshooting this. More specifically: in being ready to troubleshoot this when it happens again.
I've enabled the syslog, but what other tools should I have ready to go, and what information should I capture before rebooting? (If I get a chance.)
Maybe there's some steps described in one of the 134 previous pages, feel free to point me there.
Much appreciated, Sander.
Assuming you are running the latest release r32753, the first thing you should try out is disable Shortcut Forwarding Engine under Setup>>Basic Setup>>Optional Settings.
Joined: 30 May 2017 Posts: 3 Location: Portland, OR
Posted: Mon Jul 24, 2017 6:56 Post subject:
ad19 wrote:
Assuming you are running the latest release r32753, the first thing you should try out is disable Shortcut Forwarding Engine under Setup>>Basic Setup>>Optional Settings.
Uh-oh, missed that one. I am still on r32670. I searched back in the forum, is this the "deleted build"? I don't know where to find it.
The r32670 has only the following entries under Optional Settings:
Router Name
Hostname
Domain Name
MTU
STP _________________ Owner of a Linksys WRT3200ACM
Assuming you are running the latest release r32753, the first thing you should try out is disable Shortcut Forwarding Engine under Setup>>Basic Setup>>Optional Settings.
Uh-oh, missed that one. I am still on r32670. I searched back in the forum, is this the "deleted build"? I don't know where to find it.
The r32670 has only the following entries under Optional Settings:
Thanks. Updated the router. That does have the "Shortcut Forwarding Engine". Disabled now. What does that do? _________________ Owner of a Linksys WRT3200ACM
Thanks. Updated the router. That does have the "Shortcut Forwarding Engine". Disabled now. What does that do?
Those who have disabled it have found the firmware to be running better, without reboots. The previous versions did not have this switch.
You should check if you are stable now.
Back to R32597 because policy based routing (OpenVPN) remains broken for me. It has been broken since the update following R32597.
Since I appear to be the only one reporting this issue, will someone who is using policy based routing please check your devices to determine if they are displaying the IP address associated with your VPN service.
For me policy based routing works perfectly with R32597 and prior updates. I am not using a restored configuration and the NVRAM is cleared prior to each update.
Borrowed a friends WRT3200 and installed R32670 and R32753. Policy based routing did not work on either of those builds, but did work properly with R32597. Policy based routing stopped working about the same time the current reboot issue began.
Back to R32597 because policy based routing (OpenVPN) remains broken for me. It has been broken since the update following R32597.
Since I appear to be the only one reporting this issue, will someone who is using policy based routing please check your devices to determine if they are displaying the IP address associated with your VPN service.
For me policy based routing works perfectly with R32597 and prior updates. I am not using a restored configuration and the NVRAM is cleared prior to each update.
Borrowed a friends WRT3200 and installed R32670 and R32753. Policy based routing did not work on either of those builds, but did work properly with R32597. Policy based routing stopped working about the same time the current reboot issue began.
SFE is known to break QOS.
I think policy based routing would also suffer problems, since SFE is trying to bypass most of the normal kernel routing and processing, to achieve the maximum speed.
