Hi All,

I was wondering if I can get some help and insight on an issue.

I was changing a line using nano in the /etc/config/network file, and then it said the contained an invalid character of some kind. I couldn't think of what, but none the less, I tried to go back and fix it, and now the networking is completely hosed in Kamikaze because the /etc/config/network file is unreadable.

So, what I wanted to know is, how do I go about getting into the router without networking working and fix the /etc/config/network file? Is there a way to use a console connection into it, similar to a Cisco console connected using ethernet to serial or something?

I've tried finding useful info on Google, but no such luck. Thank you in advance for all your help.

Yes, as soon as you have serial working you can use vi or nano to fix it up.
http://wiki.openwrt.org/OpenWrtDocs/Har … sys/WRT54G

A USB-TTL adapter like the Prolific PL-2303 is your best bet.
http://www.nslu2-linux.org/wiki/HowTo/AddASerialPort

Would it be the same kind of connection as a console connection to a regular cisco router? Just hook up the console cable to the com1 port on your computer, then plug the other end into an RJ-45 jack on the router, then go in through the console connection using HyperTerminal or something similar?

The first link you sent mentions what the baud rate for a WRT54GS is, and I'd imagine the WRT54G is similar, however port do I connect it to on the router? One of the LAN ports or the WAN/Internet port? Since the Linksys routers do not have a console port like the Cisco's do.... The link also mentions another link talking about soldering a serial port onto the router motherboard itself, but is that really necessary just to get into it?

The serial port on the other end isn't an issue. I just hooked it to my Dell PowerEdge 750 via the COM1 port and connected with a standard Cisco console cable, and it doesn't seem to be working thus far...

Thanks again for your help.

the console port is internal. you don't need a serial console to fix this though.
http://wiki.openwrt.org/OpenWrtDocs/Troubleshooting - see failsafe mode

connecting an rs232 port to ethernet and vice-versa is dangerous. as is connecting rs232 directly to the router's serial port, which is 3v. the wiki page you read should make this clear though

Ok, now I have went through these steps before, and I didn't get anywhere. Hitting the reset button seems to do absolutely nothing. I have no clue whether I can get into failsafe or not, as I still cannot ping the default of 192.168.1.1. I cleared my arp cache.

According to the document, you press and hold the reset button, and the DMZ light should come on, then go off. That does not happen unless I power cycle the router.

So far, a serial connection is the only way I see of fixing this. Does anyone have any other ideas?

you are misreading the document. you press (or hold, in earlier versions) the reset button at the proper time during startup

Ok, so to understand this, I want to powercycle the router, then while the DMZ light is on during boot up, thats when I want to hold and/or press the reset button?