WRT54G V2 - Can't access after setting up Client + AP
Posted: Fri Jul 05, 2013 7:04 pm
I have a WRT54G V2 that was successfully running 1.4.7. I attempted to setup Client+AP (like this: http://www.gargoyle-router.com/wiki/dok ... nt_ap_mode). After I saved the settings the power light began flashing and I can't access it any more.
It is pingable at 192.168.1.1 with a TTL of 64 for a period of time (never with TTL of 100) and then that goes down and it is pingable at 192.168.25.1 (the address I setup as LAN IP), still with a TTL of 64. I cannot access the admin pages from either IP, and the wireless is not advertised or accessible. I can't telnet or SSH to either address at any time during the process.
Once the router is pingable at the 25.1 address the power light is a steady fast blink, the DMZ light stays lit and the WLAN is also lit but much dimmer. The LAN light is lit when I connect my cable and flashes when I send commands.
I have tried TFTP-ing new .bin files, since it is pingable. It always fails with a timeout. I never get the ACK from the router for even the first packet. Doesn't seem to matter if I send it right away or wait or push the reset button before or during.
I have not had any luck getting it into management mode or fail safe mode to restore it to firstboot. I have tried setting the eth at half duplex, adding the router mac to the arp table, etc.
It appears that the router is up and running, even pingable on the LAN I setup (though it is not handing out DHCP addresses), but something is hanging it somewhere in the process. I have also tried turning off the other wireless AP that it was supposed to connect to (a mifi) and that doesn't appear to change the process in any way.
I feel like I have tried most everything but thought I would put it out there and just make sure I am not missing something obvious!
Any ideas?
It is pingable at 192.168.1.1 with a TTL of 64 for a period of time (never with TTL of 100) and then that goes down and it is pingable at 192.168.25.1 (the address I setup as LAN IP), still with a TTL of 64. I cannot access the admin pages from either IP, and the wireless is not advertised or accessible. I can't telnet or SSH to either address at any time during the process.
Once the router is pingable at the 25.1 address the power light is a steady fast blink, the DMZ light stays lit and the WLAN is also lit but much dimmer. The LAN light is lit when I connect my cable and flashes when I send commands.
I have tried TFTP-ing new .bin files, since it is pingable. It always fails with a timeout. I never get the ACK from the router for even the first packet. Doesn't seem to matter if I send it right away or wait or push the reset button before or during.
I have not had any luck getting it into management mode or fail safe mode to restore it to firstboot. I have tried setting the eth at half duplex, adding the router mac to the arp table, etc.
It appears that the router is up and running, even pingable on the LAN I setup (though it is not handing out DHCP addresses), but something is hanging it somewhere in the process. I have also tried turning off the other wireless AP that it was supposed to connect to (a mifi) and that doesn't appear to change the process in any way.
I feel like I have tried most everything but thought I would put it out there and just make sure I am not missing something obvious!
Any ideas?