probleme squeezeplug raspberry

[Arnaud]

ok ça, c'est bon.
Est-ce que depuis ton Rpi, tu peux faire un ping de ta centrale Calaos ?
# ping adresse_ip_calaos
et idem depuis le NAS (toujours en ssh)

[thierry]

lorsque je fais le ping du rpi vers la centrale cela donne ça :

id=3R2M49ARYWK6C
Last login: Fri Jun 20 22:19:28 2014 from thierry-pc
root@squeezeplug:~# ping 10.0.0.123
PING 10.0.0.123 (10.0.0.123) 56(84) bytes of data.
64 bytes from 10.0.0.123: icmp_req=1 ttl=255 time=3.51 ms
64 bytes from 10.0.0.123: icmp_req=2 ttl=255 time=1.58 ms
64 bytes from 10.0.0.123: icmp_req=3 ttl=255 time=1.65 ms
64 bytes from 10.0.0.123: icmp_req=4 ttl=255 time=1.57 ms
64 bytes from 10.0.0.123: icmp_req=5 ttl=255 time=1.57 ms
64 bytes from 10.0.0.123: icmp_req=6 ttl=255 time=1.61 ms
64 bytes from 10.0.0.123: icmp_req=7 ttl=255 time=1.56 ms
64 bytes from 10.0.0.123: icmp_req=8 ttl=255 time=1.55 ms
64 bytes from 10.0.0.123: icmp_req=9 ttl=255 time=1.56 ms
64 bytes from 10.0.0.123: icmp_req=10 ttl=255 time=1.59 ms
64 bytes from 10.0.0.123: icmp_req=11 ttl=255 time=1.60 ms
64 bytes from 10.0.0.123: icmp_req=12 ttl=255 time=1.53 ms
64 bytes from 10.0.0.123: icmp_req=13 ttl=255 time=1.51 ms
64 bytes from 10.0.0.123: icmp_req=14 ttl=255 time=1.54 ms
64 bytes from 10.0.0.123: icmp_req=15 ttl=255 time=1.53 ms
64 bytes from 10.0.0.123: icmp_req=16 ttl=255 time=1.57 ms
64 bytes from 10.0.0.123: icmp_req=17 ttl=255 time=1.51 ms
64 bytes from 10.0.0.123: icmp_req=18 ttl=255 time=1.61 ms
64 bytes from 10.0.0.123: icmp_req=19 ttl=255 time=1.62 ms
64 bytes from 10.0.0.123: icmp_req=20 ttl=255 time=1.55 ms
64 bytes from 10.0.0.123: icmp_req=21 ttl=255 time=1.50 ms
64 bytes from 10.0.0.123: icmp_req=22 ttl=255 time=1.59 ms
64 bytes from 10.0.0.123: icmp_req=23 ttl=255 time=1.60 ms
64 bytes from 10.0.0.123: icmp_req=24 ttl=255 time=1.96 ms
64 bytes from 10.0.0.123: icmp_req=25 ttl=255 time=1.56 ms
64 bytes from 10.0.0.123: icmp_req=26 ttl=255 time=1.50 ms
64 bytes from 10.0.0.123: icmp_req=27 ttl=255 time=1.55 ms
64 bytes from 10.0.0.123: icmp_req=28 ttl=255 time=1.65 ms
64 bytes from 10.0.0.123: icmp_req=29 ttl=255 time=1.53 ms
64 bytes from 10.0.0.123: icmp_req=30 ttl=255 time=1.54 ms
64 bytes from 10.0.0.123: icmp_req=31 ttl=255 time=1.54 ms
64 bytes from 10.0.0.123: icmp_req=32 ttl=255 time=1.61 ms
64 bytes from 10.0.0.123: icmp_req=33 ttl=255 time=1.50 ms
64 bytes from 10.0.0.123: icmp_req=34 ttl=255 time=1.58 ms
64 bytes from 10.0.0.123: icmp_req=35 ttl=255 time=1.60 ms
64 bytes from 10.0.0.123: icmp_req=36 ttl=255 time=1.59 ms
64 bytes from 10.0.0.123: icmp_req=37 ttl=255 time=1.61 ms
64 bytes from 10.0.0.123: icmp_req=38 ttl=255 time=1.62 ms
64 bytes from 10.0.0.123: icmp_req=39 ttl=255 time=1.58 ms
64 bytes from 10.0.0.123: icmp_req=40 ttl=255 time=1.49 ms
64 bytes from 10.0.0.123: icmp_req=41 ttl=255 time=1.60 ms
64 bytes from 10.0.0.123: icmp_req=42 ttl=255 time=1.61 ms
64 bytes from 10.0.0.123: icmp_req=43 ttl=255 time=1.62 ms
64 bytes from 10.0.0.123: icmp_req=44 ttl=255 time=1.60 ms

et ça continue encore.
je n'arrive pas a faire le ping depuis le nas, pourtant j'ai activé le SSH et le pare feu autorise le port 22.

[Arnaud]

Oui, c'est un ping sans fin, il faut un faire control-c pour l'arreter. Le but est juste de voir si ça réponse (ici oui). Si tu fais un ping sur 10.0.0.200 ça doit probablement fonctionner également. A vérifier.

Là, ya pas de raison que ça ne fonctionne pas.