Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sun Sep 18, 2011 6:31 Post subject:
Well ... I have not checked in a while, so I was under the impression there was a newer BrainSlayer build. He is the only one who puts out the K24 NEWD2 builds. As it is, I have previously tried the 17201 build and it was problematic for me on my WRT600n. So nothing new to report here. If BS ever decides to put out a newer version, I will try it. But not before then. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Joined: 16 Dec 2009 Posts: 83 Location: Florence (ITALY)
Posted: Mon Sep 19, 2011 9:08 Post subject:
shimh wrote:
The issue is with the firmware itself. My WRT600N has the same issue without optware. Now I understand why when every time it happens, power cycle would deal with it, as the router stuck in shut down process, and booting up is good.
EXACT! the router stops in shutdown sequence... It's not a boot problem. In fact powering off and powering on there isn't any problem.
I hope in a nearly future build realease to test.
thank you shimhand and crashfly for testing and interesting!
Close, but not quite. I use the wrt610 version of that same firmware. The WRT610 is the only 2.4 kernel version put out by Brainslayer that has the NEWD2 drivers (wireless) in it. Those drivers are have said to have better performance.
[snippage]
---------
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2
Not to hijack this (aging) thread... (still, it IS about WRT600N). I'm curious if you're still using the WRT610N mega build in BS's 2012/18767 branch in your WRT600N, or are you actually using the build right above it?
i.e. is BrainSlayer now including the NEWD2 drivers in that WRT600N mega build?
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Wed Mar 21, 2012 18:00 Post subject:
Darr247 wrote:
Not to hijack this (aging) thread... (still, it IS about WRT600N). I'm curious if you're still using the WRT610N mega build in BS's 2012/18767 branch in your WRT600N, or are you actually using the build right above it?
i.e. is BrainSlayer now including the NEWD2 drivers in that WRT600N mega build?
Thanks.
I will "always" be using the WRT610n BS builds on my router. As far as I know, that is the *only* K24 build that has the NEWD2 drivers. When updating my router build, I will usually update my profile information too. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sun May 06, 2012 20:40 Post subject:
I have actually gone to a WRT610n that has been upgraded to an E3000. It works quite well for me.
As for your questions about it, on the most recent builds (17000 and on), my "major" problem with my WRT600n has been getting an IP address from the WAN side of the router. It may not affect most people who have their router tied to a cable modem or something similar. In my setup, my router is DMZed behind an ATT 2wire Uverse router. On a reboot of the WRT600n, my computer will get an IP address from the 2wire router and essentially lose all connectivity due to the internal network having a different IP scheme. To get around the issue, I have had to release and reacquire an IP address after the WRT600n has fully booted.
It is not a 'show stopping' problem, but it is annoying to say the least. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
runny a little flakey from my end. Primary use is a router. radios turned off unable to get vpn smooth from wan side locked up twice on me.
My Lan thorughtput file transfer was 60mps from win7 box and pushed 90 from a samba box
going back to 14929 to see if it is me or the router.
I hope all is well in the communnity. Any other experiances with builds on the wrt600n v1.1 would be appriciated. Thanks again crashfly for your contributions.
Joined: 23 Jan 2008 Posts: 50 Location: Ulm, Germany
Posted: Wed Jan 02, 2013 3:25 Post subject:
Hi...
I've got a question about the original problem which has been discussed in this thread: I still experience the problem with all of my four Linksys WRT600N (three of them are v1.1, one is the first version). They are all acting as client bridges and are running BS build 19519 (with NEWD2). I've applied the image which is made for the WRT610N to get the newer drivers and kernel 2.4.
Rebooting leads to unreachable devices from time to time which means that it does not happen always. Whenever the problem occurs, the Power LED of the affected router will be flashing. Power-Cycling the router always helps in this situation.
Does anybody have a solution to the problem in the meantime?
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Wed Jan 02, 2013 18:21 Post subject:
Steffen M. wrote:
Rebooting leads to unreachable devices from time to time which means that it does not happen always. Whenever the problem occurs, the Power LED of the affected router will be flashing. Power-Cycling the router always helps in this situation.
The problem with 'randomly' rebooting routers can be any number of things. If the router loses its settings at the same time, that is usually a problem with nvram filling up. If the router is under "heavy" load at the time it reboots, it could be heat and/or power issues.
One final thing to note is that some builds can be problematic for routers also causing reboots.
As it is, I do not use the client bridge settings and therefore do not know how that would affect the stability of the router. Others would have more experience with that. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Joined: 23 Jan 2008 Posts: 50 Location: Ulm, Germany
Posted: Fri Jan 04, 2013 2:52 Post subject:
crashfly wrote:
Steffen M. wrote:
Rebooting leads to unreachable devices from time to time which means that it does not happen always. Whenever the problem occurs, the Power LED of the affected router will be flashing. Power-Cycling the router always helps in this situation.
The problem with 'randomly' rebooting routers can be any number of things. If the router loses its settings at the same time, that is usually a problem with nvram filling up. If the router is under "heavy" load at the time it reboots, it could be heat and/or power issues.
Thank you very much for your reply, crashfly!
Nevertheless, it seems that I've stated my problem not clearly enough: My WRT600Ns are not rebooting on their own. Instead, they are running absolutely stable. The problem I encountered after upgrading from build 14896 to 19519 is the following one: If I reboot any of them manually (using the "reboot" command at the router's command line), it will occasionally happen that they do not come up again. The Power LED is flashing in this case. After power-cycling, an affected WRT600N boots up absolutely fine.
It rather seems that it is stuck in the shutdown process - exactly as it is described, discussed and analyzed in this thread.
The problem occurs with at least these two DD-WRT version:
- DD-WRT v24-sp2 (07/20/12) mega - build 19519
- DD-WRT v24-sp2 (12/31/12) mega - build 20453
I use Brainslayer's builds with Kernel 2.4 and the new drivers NEWD2 which can be found in the images for the WRT610N.
All of my affected routers are WRT600Ns (both, the original version and version 1.1).
Any help or any hints to a fix will be highly appreciated!
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Fri Jan 04, 2013 4:35 Post subject:
Steffen M. wrote:
It rather seems that it is stuck in the shutdown process - exactly as it is described, discussed and analyzed in this thread.
Unfortunately, if you cannot determine what the "fix" for this is on your own, you will likely not get any help from the developers. They are more interested in everything else than actually fixing most bugs.
Likely the only way to test for problems is to use the serial console on that router. But for an 'occasional' problem, the work for attaching a serial console to that device may not be worth it. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Joined: 24 Oct 2009 Posts: 319 Location: Buenos Aires-Argentina, End of World and new Pope's home.
Posted: Sat Jan 05, 2013 1:06 Post subject:
Hi crashfly since 2,5 years my 600n is on mega-build 14853M NEWD-2 Eko, is it kernel 2.4? if so, did you tested it? is it similar to yours 2.4 kernel 2.4 610n firm?
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sat Jan 05, 2013 22:25 Post subject:
I typically use the more recent editions. The last one I was using for the WRT600n was build 18767. As it was, I did not seem to ever run into the 'rebooting' or 'shutdown' problems.
Similar? Yes.
The same? No as I used a bit newer firmware build. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Sorry to bring this up but I was just shown this thread by another member, the weird thing is that if you don't change the SSID from 'dd-wrt' reboot works fine, you can even secure it just don't change the name and reboot works.