Posted: Wed Oct 12, 2022 17:39 Post subject: Reviving LINKSYS WRT150N
I have just been looking at an old LINKSYS WRT150N which I thought I may be able to use to extend my LAN.
I was unable to logon to the unit initially, but to my surprise I found that I had installed DD-WRT v24-sp2 on it at some time (long ago...).
The web server won't allow access even though httpd is running. Access was only allowed via telnet, sshd isn't running.
How should configure the system? And is there a file manager such as MC available, or could one be installled? Alternatively could I mount the device via NFS or somesuch?
I'm not sure how httpd is started. According to ps it is running httpd -p 80 and I can't close it with kill -9.
I've been unable to reset, and trying to connect via SSH results in connection refused, not surprising since SSHD isn't running.
I must have been able to login to the web interface at some time, but that may have been 10 years ago. Not sure what I can do at the moment and don't know my way around the system enough to work out how to fix things. How is httpd started?
If telnet works, you should be able to do an erase nvram && reboot considering the build you are currently on - it is nvram erase && reboot on current versions. That should clear username/password. Wasn't the original default webUI username admin prior to being changed to root? The password should apply to all access methods (webUI, telnet, ssh). _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
If telnet works, you should be able to do an erase nvram && reboot considering the build you are currently on - it is nvram erase && reboot on current versions. That should clear username/password. Wasn't the original default webUI username admin prior to being changed to root? The password should apply to all access methods (webUI, telnet, ssh).
Thanks, but 'nvram erase && reboot' didn't make any difference. I can still telnet as before, but webUI is not accessible even though 'httpd -p 80' is running.
uname -a shows I'm running 'DD-WRT 2.4.37 #4021'.
I notice that a process called 'resetbutton' is running. What does this do?
If you read what I wrote correctly, you would know that the command to reset via telnet/ssh on your current build is 'erase nvram'. resetbutton process is polling the hardware reset button on the router. If you press the reset button for ~10 seconds while router is running, it should reset the router. One thing I guess was overlooked: Are you accessing webUI via http://router.ip.address.here (i.e. http://192.168.1.1) or is it defaulting to https:// ? _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
If you read what I wrote correctly, you would know that the command to reset via telnet/ssh on your current build is 'erase nvram'. resetbutton process is polling the hardware reset button on the router. If you press the reset button for ~10 seconds while router is running, it should reset the router. One thing I guess was overlooked: Are you accessing webUI via http://router.ip.address.here (i.e. http://192.168.1.1) or is it defaulting to https:// ?
I finally managed to revive my router as explained in:-
I had one of those routers for a time around 4 years ago what I discovered is that the CPU in the device is so slow (I think it's only 100Mhz) that the newer builds are -very- sluggish on it.
I finally ended up reverting it back to stock firmware and it found a home as a wireless access point in a small out of the way office that only a few people ever used. As far as I know it's still there in operation. (that client got bought out a year ago)
Yours is running OK with whatever decades old dd-wrt build you have on it - if you want to walk it forward to a newer build I would do it a year at a time and stop when it starts slowing down.
I had one of those routers for a time around 4 years ago what I discovered is that the CPU in the device is so slow (I think it's only 100Mhz) that the newer builds are -very- sluggish on it.
Max capable 300MHz, clocked down to 264MHz in this router.
Yours is running OK with whatever decades old dd-wrt build you have on it - if you want to walk it forward to a newer build I would do it a year at a time and stop when it starts slowing down.
Is there any program I can run to objectively show that it is slowing down?
