I did a mistake while configuring dhcp and vlans so my device is unreachable.
I boot into failsafe mode and try to telnet 192.168.1.1 it says "Connecting To 192.168.1.1...Could not open connection to the host, on port 23: C
onnect failed"
What could i do before I throw it through the window.
Thanx

EDIT: Forgot to say after entering failsafe mode it responds ping but not telnet (nor ssh nor http : quite logic )

(Last edited by patamou on 16 Feb 2007, 14:22)

Hi patamou, I have the exact same problem.

I was running DD-WRT, and after I upgraded to X-WRT 0.9, the Ethernet-ports wouldn't work (some mess with ports and vlans in the nvram, I believe). Only br0, Eth2 and lo0 came up in ifconfig. While trying to get the nvram-settings right, so that the wired ports would be in vlan2 -I somehow screwed up and got stuck. Now I can't get in by wireless or by wired. =/

And now when I go into failsafe, I can ping it -but telnet (or anything else, for that matter) doesn't respond.
This is a WRT54G v1.1
_And_ the boot_wait turned itself off too, for some reason?! So now I can't re-flash it either. My computer-port doesn't come up fast enough. I might borrow a switch tomorrow and try again.

But in your (the reader's) experience, is this screwed-up-nvram-settings-problem solvable by simply reflashing stock/openwrt/dd-wrt firmware via tftp or should I just start looking for parts for a JTAG-cable?

Thanks,
Treq

(Last edited by Treq on 18 Feb 2007, 20:37)

I am having the same Problem.

I need to go to failsafe, and I also get the "Entering Failsafe!" message from the router.  I flushed my ARP Cache and Dns cache.  I am able to ping the router, but no telnet.

Can anyone help at this ??  Is the failsafe broken in 0.9 ???

I found out (using nmap) that when in failsafe mode the device has only the 25 port open (SMTP ????). should'i report this as a bug?
Does anyone can help for this?
Thanx for future answers ;p

Hi patamou,

What happens when you telnet to port 25 on your router? What do you arrive at? Would be nice if it was the telnet-server simply running on the wrong port.

If this is not the case, then I am going to try to flash the dead router with RC6, then use the failsafe on that one to change my screwed up nvram variables, and then flash back to RC9.

Might work for you too.

Treq

I got the same reply as normal telnet port. I've tried to flash with a rc6, a rc6 micron and a rc5 but tftp transfer didn't start in any case.(tried all methods found in docs & forum as start tftp before/after plugging in,...)
Thanx

Patamou (who will go back cry'ing in a dark corner )

I reported it here: https://dev.openwrt.org/ticket/1372

Don't panic :-) JTAG isn't the best way to solve your problem!

Get an old mobile phone serial interface cable and a soldering iron, and use the CFE to fix the problem. Check  http://wiki.openwrt.org/OpenWrtDocs/Har … sys/WRT54G and http://www.nslu2-linux.org/wiki/HowTo/AddASerialPort for more information.

Cheers
/T

haha :-(

Try this on a WL-HDD!! You have to solder and buy ICs and so on .... only because there is no properly working failsafe in this thing :mad::mad::mad:

Dadaniel, you got me wrong :-)

There is no question that the fail-safe mode has to be fixed (however, it is very likely that a patch to the diag module I posted earlier would fix the problem).

Using the serial port doesn't require advanced electronics skills, since you can use a mobile phone cable that already has all the necessary interface electronics. Building a buffered JTAG cable is a different story ;-)

I mentioned the serial interface/CFE option with the WRT54GL in mind. The WL-HDD doesn't even have a serial interface. You'll have to be a little bit more inventive ;-)

Cheers
/T

I've run into the same problem on my WRT54GL. I upgraded from the stock firmware to X-Wrt (version from a couple of days ago, I think 2560) and everything was fine, until I rebooted the router. After that, somehow the MAC cloning did not work, although the NVRAM var seemed to be OK. The router simply didn't get the IP from my ISP. I may have done some changes to VLANs (it was late and I was tired, yes, I know, I should've gone to bed instead), but nothing helped - the router actually became inaccessible. I decided to TFTP in the morning (today), but it does not work. It is quite possible that it's because the moment I unplug the router, Windoze report that net cable has been unplugged and by the time they recover when I plug the router, I miss the window of opportunity.

I decided to try to enter failsafe and held the reset button and DMZ light started flashing. However, while ping works, telnet does not. Any and all advice will be very appreciated.

I have made progress and maybe this info can come handy to others as well.

The problem seems to be in the X-Wrt kernel. After digging out an old laptop and realizing that the PCMCIA card/interface is not reset once the cable is pulled out, I have successfully TFTP-ed the latest vanilla OpenWrt and the router came back alive. On 54GL, the right time to hit enter to start TFTP transfer is the moment right after all 5 LAN LEDs have flashed.

I'm busy with some other stuff, so I won't set up things just now, but if anyone needs any further info, do not hesitate to contact me.