Posted: Sat Nov 08, 2014 2:59 Post subject: WRT610N v1 unstable
I'm using this build right now: DD-WRT v24-sp2 (12/24/10) mega - build 15962
When I leave the house, I usually turn off the extension outlet where the PSU of my router is connected to. My PSU is an ASUS PSU that has a 2A output rating.
The problem I'm having is that randomly the 2.4GHz signal of the unit is not detected and I have the erase the nvram and restore from backup to fix it. This happened already many times and I really don't know the problem. I reckon that this was a problem with the initial releases of this unit but the build I have is pretty recent.
I have a WRT610N v1 and used it as my main router for years. The best build of ddwrt I found was v24 K2.4 23919 Mega. Everything worked and it was very reliable. I didn't power it off the way you do but anytime it was rebooted it worked correctly.
If you are confident flashing a newer build then here is the link,
I am confident in flashing different builds, yes. But my problem is not after the reboot, it is during operation. Right now, if I don't erase the nvram and restore from config the 2.4GHz doesn't come back even after several reboots. I'm not sure if it is the side effect of how I turn on and off the router but is there even another way? Cutting the power is the only way to turn it off.
Is that the latest build that this router can handle?
No there are much later builds but the one I mentioned works perfectly on my unit. I use both wireless bands at the same time and have a loads of devices connected. Last count I had over round 20 live at any time.
The build you are using is pretty old and if these issues are random I'd try another build.
I moved to 23919 build because I needed a version with the heartbleed bug patched. 23919 was the first version that was.
It's a good build, I could not find anything that didnt work as it should.
If you are having to erase nvram and reconfigure you could also try backing up your config and simply restoring it as you need too. Saves time.
Ok, how about the other newer builds have you tried them? I hope another person could chime in to share their experience with different builds also. The more the merrier
You are not supposed to restore from a backup save if you are flashing different build.
I'm not sure where you got that information from. We're not doing that. Did you read the whole thread? I'm using the backup to restore when the issue is happening and this is using the SAME build.
Sorry, I just wanted to make sure, since the thread mentions at least 3 or 4 different builds.
No need to get pissy. _________________ I am far from a guru, I'm barely a novice.
Sorry, I just wanted to make sure, since the thread mentions at least 3 or 4 different builds.
No need to get pissy.
I'm not pissy at all, this is the limitation of text-based communication, you wouldn't know my true expression on what I said. I was just saying. Thanks for the information though. I hope we can get more information on the issue.
At a family members home they have a 610v1 that a renter connects to and I have been running BS K24 build 20548 (01/24/13) mega for almost 2 years without any issues (610v1 in use for over 4 years). The 610v1 connects to the main router (E3000) via 5Ghz radio and the renter has access to the 2.4Ghz radio. I consider the 610v1 a great router. I bought another 610v1 for backup for the family.
The stock power supply isn't used. They have a 12V 5A power brick on a UPS. _________________ Home Network on Telus 1Gb PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r53562 Std k4.9
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r54517 Std
E3000 - Station Bridge - DDWRT r49626 Mega K4.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r54517 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
You are not supposed to restore from a backup save if you are flashing different build.
I'm using the backup to restore when the issue is happening and this is using the SAME build.
Don't. You reintroduce the problem if it is in Nvram variables. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
You are not supposed to restore from a backup save if you are flashing different build.
I'm using the backup to restore when the issue is happening and this is using the SAME build.
Don't. You reintroduce the problem if it is in Nvram variables.
Yeah, I understand that and I already tried the route of doing a hard reset (note 1 of peacock) and reconfiguring the settings manually to no avail so I've already isolated that it is not an NVRAM variable. Any more ideas?
