So as the title suggests, I have locked myself out of the router.
Using Kamikaze 7.09 on the 2.6 Kernal with X-wrt's web^if installed, I changed LAN and WAN settings. I left the lan at it's default of DCHP with a bridged connection. I then changed it's fallback IP from 192.168.1.1 to 192.168.1.15. Always on subnet 255.255.255.0. I changed the WAN to be set at static 192.168.1.14 with a subnet of 255.255.255.0 I did a soft reboot, followed by a power cycle.
I changed my TCP/IP to static with an ip of 30. Subnet per usual. I set the gateway to 192.168.1.15, restarted network services, and plugged the cat5 into the LAN of the router.
None of the LAN ports respond. I can send all the informatrion I want to them and them will accept it as a live connection. But it's like everything is directed to dev/null. No response to ping, SSH, port 80. Nothing. It just sits there. never times out. Just keeps sucking down information. A glance at the Gnome connection graph shows 500k sent in 5 minutes and 1.5k responded. Nothing but keep-alive packets I assume.
Ok, so I change my gateway to 14 instead of 15 and restarted network services. Power cycle the router and plug the cat5 in the WAN instead. Now I can ping!......but that's all. Port 80, 21, and 22 refuse connections,as any good WAN port on a router with firewall would.
Am I left with nothing but plugging in a serial console cable and flashing the router new via TFTP? It's the WGT634U, so reset button does nothing but produce an excellent epic fail by ensuring the need to open the router and flash via serial connection.
So to summerize since this is in How/TO for a reason. When all you have is the firewalled WAN port, is their a backdoor into the web config or the commend line?
(Last edited by Arch13 on 7 Mar 2008, 15:52)
