Modify

Opened 6 years ago

Last modified 4 years ago

#10456 reopened defect

Failsafe not working on r29237

Reported by: anonymous Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Trunk
Keywords: failsafe Cc:

Description

Installed snapshot of bleeding edge, r29237 and when entering into failsafe mode on TL-WR703N it won't accept connections and, apparently, it won't get any ip (at least on 192.168.1.0/24 and 192.168.0.0/24). I know it's on failsafe mode because led blinks fast.

Attachments (0)

Change History (14)

comment:1 Changed 6 years ago by anonymous

It's like if ethernet was dead. Any suggestions? I would very much appreciate if i didn't have to use a jtag or so. thanks

comment:2 follow-up: Changed 6 years ago by caog

originally #10430, but now it's in snapshot, also #10436 is probably same.

comment:3 in reply to: ↑ 2 Changed 6 years ago by mindless

Replying to caog:

originally #10430, but now it's in snapshot, also #10436 is probably same.

So i guess there's no chance rather than serial console, right?

comment:4 Changed 6 years ago by juhosg

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in r29274.

comment:5 Changed 6 years ago by valent.turkovic@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

I just checked out revision 29288 and build wr703 firmware, and cant get failsafe mode to work.

I had previously installed 2 months older image and failsafe worked on it. Ethernet works but failsafe is not working.

comment:6 Changed 6 years ago by jow

And did you also run make target/linux/clean ? Did you use a fresh .config ?

comment:7 follow-up: Changed 6 years ago by anonymous

svn checkout svn://svn.openwrt.org/openwrt/trunk/
cd trunk
./scripts/feeds update -a
./scripts/feeds install -a
make defconfig
make prereq
make menuconfig

in menus choose ar7xx and wr703n as model, and now I'm buiding new firmware:
make -j 3

with fresh .config, I deleted whole previous trunk folder before downloading this latest one.

Am I doing something wrong?

comment:8 in reply to: ↑ 7 Changed 6 years ago by juhosg

  • Resolution set to worksforme
  • Status changed from reopened to closed

Replying to anonymous:

Am I doing something wrong?

Maybe, although I don't see any obvious mistake in your steps. However it is working with my own build, and it is working with the snapshot image as well.

[juhosg@idared openwrt]$ telnet 192.168.1.1
Trying 192.168.1.1...
Connected to 192.168.1.1 (192.168.1.1).
Escape character is '^]'.

 === IMPORTANT ============================
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
 ------------------------------------------


BusyBox v1.19.3 (2011-11-21 23:19:22 MST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 ATTITUDE ADJUSTMENT (bleeding edge, r29289) ----------
  * 1/4 oz Vodka      Pour all ingredients into mixing
  * 1/4 oz Gin        tin with ice, strain into glass.
  * 1/4 oz Amaretto
  * 1/4 oz Triple sec
  * 1/4 oz Peach schnapps
  * 1/4 oz Sour mix
  * 1 splash Cranberry juice
 -----------------------------------------------------
root@(none):/# dmesg | grep ^Linux
Linux version 2.6.39.4 (openwrt@OpenWRTBuild) (gcc version 4.5.4 20110808 (prerelease) (Linaro GCC 4.5-2011.08) ) #1 Tue Nov 22 10:36:01 MST 2011
root@(none):/#                   

comment:9 Changed 6 years ago by p.titera@…

  • Resolution worksforme deleted
  • Status changed from closed to reopened

But then on WR941NDv3 and r29352 it's not working. I've bricked my new router when I did one stupid configuration error :(

When I do tcpdump when starting the router, I see message indicating that button should be pressed sent from 192.168.1.1 (from prom preinit/30_failsafe_wait) so interface gets IP for a moment (no answer to pings at that time too).

But something is strange tcpdump is complaining about truncated packet:

[root@www ~]# tcpdump -s0 -XX -e -n -i eth0 net 192.168.1.0/24
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
01:11:31.458615 f4:ec:38:c7:dd:40 > Broadcast, ethertype IPv4 (0x0800), length 1039: truncated-ip - 4 bytes missing! 192.168.1.1.52522 > 192.168.1.255.4919: UDP, length 1001
        0x0000:  ffff ffff ffff f4ec 38c7 dd40 0800 4500  ........8..@..E.
        0x0010:  0405 0000 4000 4011 b297 c0a8 0101 c0a8  ....@.@.........
        0x0020:  01ff cd2a 1337 03f1 09d4 dead 506c 6561  ...*.7......Plea
        0x0030:  7365 2070 7265 7373 2062 7574 746f 6e20  se.press.button.
        0x0040:  6e6f 7720 746f 2065 6e74 6572 2066 6169  now.to.enter.fai
        0x0050:  6c73 6166 6500 0000 0000 0000 0000 0000  lsafe...........
        0x0060:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0070:  0000 0000 0000 0000 0000 0000 0000 0000  ................

        0x03e0:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x03f0:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0400:  00                                       .

When I press button, LED will start flasshing rapidly, but I do not get any response from router.

I see several problems here. Why is the packet truncated? and Why is actualy LONGER than it should be (netmsg should send only 1001 bytes in packet). It seems to me that there is something funny with network setup when in failsafe mode for these routers.

Is there any chance for bringing the router back to live or is it serial line time for me?

Petr

comment:10 Changed 6 years ago by anonymous

I made a mistake in my network config and had to use fail safe. At first it didn't work. I plugged in the router and pressed the reset button for 60 seconds. Then nothing more happened.

What I found I had to do was

  1. Connect everything
  2. Press reset button
  3. When the led starts blinking, let go of button.

Now the led should start blinking very fast.

comment:11 Changed 6 years ago by nbd

  • Resolution set to worksforme
  • Status changed from reopened to closed

works for me in current versions

comment:12 Changed 5 years ago by vadim@…

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Seems i have bricked my router when added
" echo 1 >/sys/kernel/debug/ieee80211/phy0/ath9k/disable_ani" to the init.rc

For me failsafe also not working (Attitude Adjustment 12.09-rc1 on TP-Link WR941ND v3)
I have message "Please press button now to enter failsafe" in my tcpdump from 192.168.1.1, and when i press QSS button or reset, my SYS LED start blinking very fast, But no message that indicated failsafe booting. And 192.168.1.1 is not pingable.

Also tried method from the last comment, but unfortunately reset button does nothing if router already started. Tried to put network cable into LAN(1-4), and WAN port, nothing happens.

comment:13 Changed 5 years ago by anonymous

Not working here aswell, just bricked my router with configs, ill use serial to unbrick

comment:14 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as reopened .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.