Posted: Thu Jan 10, 2019 19:45 Post subject: WAP54G 3.1 lockout
Can somehow please help with this? I have a WRT54g v3.1.
Background:
Unit was freshly flashed and now its inaccessible via Web, BUT broadcasts the SSID I specified.
I used ddwrt YEARS ago and haven’t been into much deep w/computing since then…and I suppose my headiness is to blame.
I consent that I did not do adequate research. For example here is a veteran telling me DON'T USE THE ROUTER DATABASE! I did not read that.
After I flashed (and included the command to keep RESET functionality), I went ahead and configured my network. It worked for a while, but after setting my IP and subnet I no longer have access to WebGUI, HOWEVER, the SSID is still up and will let me browse if I plug its single port into the router that actually does DHCP on the LAN (after modem).
So the unit isn’t “bricked” per se, Also wireshark will show me some activity over lan – but the IP in suspicion yields no webGUI by port 80. I say suspicion because I’m still opting to believe that I misplaced the IP (ie, put in one I don’t remember).
30/30/30 does not work.
Are my only options now to use telnet / a jumper reset? Does anyone have any suggestions for finding the lost IP maybe? Its definitely in the range of 192.168.1/2.x if that was my error.. Any genuine effort @ help is appreciated.
I’m asking these questions hoping to get a better understanding of how to proceed I don’t want to run ahead again and do foolishness. But I was looking @ the method here: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=47536
Thanks in advance.
Last edited by 0pom on Wed Jan 16, 2019 16:34; edited 1 time in total
that tiant NO good.
About the last build that works ok on the WAP54G is r36104 ... also does ok as WDS bridge.
well I do have r38240 installed on one WAP54G up couple days but it is used only as a WAP.
I believe I tried to install r36247 on my WAP54G WDS but it would not work at all and after reset it would not do DHCP best I remember.
I suggest you reset and set static IP of 192.168.1.7 on computer or wireless device and see if can access it at 192.168.1.1 that way.
Then maybe install nothing later than r36104....but the old r14929 did work well on them.
Many builds of last year or so -- you must do a power cycle after installing on the WAP54 before you can access it.
Hey thanks very much for the replies gents.
I have tried 30/30/30 reset. Over and over, and after letting the router rest unpowered for a while and trying again, I can confirm that the router is NOT pingable @ 192.168.1.1. I am static: 192.168.1.2
I've found a MAC reading @ 192.167.1.147 - which is probably the IP I set the router to last config.
(thanks for the .bin)
I just tried exactly as you said here:
[quote="mrjcd"]
0pom wrote:
I suggest you reset and set static IP of 192.168.1.7 on computer or wireless device and see if can access it at 192.168.1.1 that way.
Then maybe install nothing later than r36104....but the old r14929 did work well on them.
Many builds of last year or so -- you must do a power cycle after installing on the WAP54 before you can access it.
Posted: Fri Jan 11, 2019 16:25 Post subject: Re: WAP54G 3.1 lockout
0pom wrote:
"WAP54G 3.1 lockout"
Ok. So this guy messed up. Can somehow please help with this? I have a WRT54g v3.1.
First, is it a WAP54G or WRT54G...v3.1??
0pom wrote:
Because this one did not direct properly:
./08-12-10-r14929/broadcom/dd-wrt.v24_micro_generic.bin
The path changed long ago, and wiki's get fixed as they're found. :-/
0pom wrote:
Are my only options now to use telnet / a jumper reset? Does anyone have any suggestions for finding the lost IP maybe?
You can use arp to map the device's LAN MAC to an unused IP (`arp -s {IP} {MAC}).
Can you reach and login via telnet? There have been cases where the GUI can't be accessed or login fails, but telnet/ssh still works. If you can login via telnet, clear the password (find it with `nvram show|grep pass` ...I'm not around a bcm router atm), or just clear the nvram (BS changed this last year, so to be complete run both `erase nvram` and `nvram erase`). _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4