OpenWrt Forum Archive

Topic: Possible FailSafe problem on mt7620

The content of this topic has been archived on 20 Jan 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

The WMR-300 works fine with OpenWRT.
Still having the serial interface plugged in, I decided to try the FailSafe...

The two ways to trigger the FS work, either [f] ENTER from console, or pressing AOSS button when the UDP beacon packet is received (PC). And everything seems to be ok.

- failsafe -


BusyBox v1.22.1 (2014-09-21 11:14:01 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

ash: can't access tty; job control turned off
  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 BARRIER BREAKER (14.07, r42625)
 -----------------------------------------------------
  * 1/2 oz Galliano         Pour all ingredients into
  * 4 oz cold Coffee        an irish coffee mug filled
  * 1 1/2 oz Dark Rum       with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
 -----------------------------------------------------
root@(none):/# 

However for some reason the ping/telnet... from PC to 192.168.1.1 (router) times out. The other way around neither

root@(none):/# ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2): 56 data bytes
^C^C^C

and the ^C (working usually in serial console) cannot stop the ping.
Wireshark (PC) shows that in this case, ping router->PC, the router emits an ARP request

router : Who has 192.168.1.2 (PC), tell 192.168.1.1 (router)

and the PC replies immediately

PC: my MAC-addr is ....

but it seems the frames don't go to the router, since  1 second later, the router sends again the same ARP query.

Note that when *not* in Failsafe mode, the interface and network exchanges work ok.

The swconfig command shows that the link is UP and autoneg worked

root@(none):/# swconfig dev mt7530 show
Global attributes:
    enable_vlan: 1
... Port 4:
    pvid: 1
    link: port:4 link:up speed:100baseT full-duplex 

and ifconfig (router) also seems satisfied

root@(none):/# ifconfig
eth0      Link encap:Ethernet  HWaddr DC:FB:02:xx:xx:xx  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:793 (793.0 B)  TX bytes:1043 (1.0 KiB)
          Interrupt:5 

The PC also cannot get ARP replies (since its ARP queries don't go through) so the ARP cache is <incomplete> for 192.168.1.1.
Its ifconfig is

[MB root@dell ~]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 74:86:7a:yy:yy:yy  
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:83 errors:0 dropped:0 overruns:0 frame:0
          TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7278 (7.2 KB)  TX bytes:9862 (9.8 KB)
          Interrupt:18 

It seems a kind of firewall prevents the packets to go to the router (or, I assume, the router blocks incoming packets, since the PC iptables is totally OFF, and anyway it would be opened for outgoing).

Or maybe I missed something?

(Last edited by *++p on 25 Jan 2015, 10:36)

The discussion might have continued from here.