[Babel-users] Communication broken on reboot/interface restart

[Jeremy Dierx]

Thank you Juliusz for your help.

Le jeudi 19 décembre 2013 à 18:35 +0100, Juliusz Chroboczek a écrit :
> > ping 192.168.13.1 => ok
> 
> Jeremy,
> 
> You're showing us the configuration when everything is working fine,
> right?

yes

>   Could you please show us the output of the following commands
> on *both* machines, after a reboot, when connectivity is lost?
> 
>  - iwconfig ra0

On server 192.168.13.101 :

ra0       Ralink STA  ESSID:"redmesh13"  Nickname:"RT2870STA"
          Mode:Ad-Hoc  Frequency=5.24 GHz  Cell: DA:3B:5A:12:D1:AC   
          Bit Rate=270 Mb/s   
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=100/100  Signal level:-47 dBm  Noise level:-61
dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


On Rpi 192.168.13.1 after down/up interface or reboot, connection lost :

ra0       Ralink STA  ESSID:"redmesh13"  Nickname:"RT2870STA"
          Mode:Ad-Hoc  Frequency=5.24 GHz  Cell: B2:CE:17:57:F0:CA   
          Bit Rate=270 Mb/s   
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=100/100  Signal level:-51 dBm  Noise level:-64
dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0



>  - ifconfig ra0


On server 192.168.13.101 :

ra0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.13.101  netmask 255.255.255.255  broadcast 0.0.0.0
        inet6 fe80::a86:3bff:fef9:8f97  prefixlen 64  scopeid 0x20<link>
        ether 08:86:3b:f9:8f:97  txqueuelen 1000  (Ethernet)
        RX packets 5497  bytes 646896 (631.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1120  bytes 166399 (162.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

On Rpi 192.168.13.1 after down/up interface or reboot, connection lost :

ra0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.13.1  netmask 255.255.255.255  broadcast 0.0.0.0
        inet6 fe80::a86:3bff:fef9:8f98  prefixlen 64  scopeid 0x20<link>
        ether 08:86:3b:f9:8f:98  txqueuelen 1000  (Ethernet)
        RX packets 4992  bytes 663389 (647.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 543  bytes 63484 (61.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


>  - ip route show


On server 192.168.13.101 :

default via 192.168.1.254 dev eth0 
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.70 
192.168.1.75 via 192.168.13.1 dev ra0  proto 42 onlink 
192.168.13.1 via 192.168.13.1 dev ra0  proto 42 onlink

On Rpi 192.168.13.1 after down/up interface or reboot, connection lost :

default via 192.168.1.254 dev eth0 
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.75 
192.168.1.70 via 192.168.13.101 dev ra0  proto 42 onlink 
192.168.13.101 via 192.168.13.101 dev ra0  proto 42 onlink


> 
> In particular, please check that the cell number (BSSID) is the same
> on both nodes.

Yes after reboot or down/up interface, Cell and Essid are the same on
both nodes.


I have some news :

When I down/up interface or reboot, if I set at least 10 times the wifi
config :
for i in {1..10}; do /usr/bin/iwconfig %i mode Ad-Hoc channel ${channel}
essid "${essid}" && sleep 0.5; done

…the  connection comes back… done!

???


Jeremy.

-- 
Jérémy Dierx
Microfilms SA - Service R&D