Archive 07/10/2020.

Adresse IPv6 globale absente et capture de paquets impossible dans TP9

DLRprod

Bonjour ,

j’ai une expérience dont les noeuds sont 100 et 101 et j’utilise le noeud 101 comme routeur de bord.
J’arrive alors à pinguer google depuis le noeud 100 mais ifconfig ne donne aucune adresse IPv6 globale.
Autre chose : aucun paquet n’est capturé dans la 3ème partie du TP

Voici mon code sur chaque terminal:

noeud 100
jovyan@43e9ec33f96a:~/work/iot-lab-training$ ssh $IOTLAB_LOGIN@lille.iot-lab.infoLinux lille 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64
Welcome FIT IoT-LAB users

Charter:

FIT IoT-LAB is shared among several users, so make reasonable use of the platform
Quote FIT IoT-LAB in your scientific papers. Usage of FIT IoT-LAB is free of charge.
In return, you must quote FIT IoT-LAB in your publication if your experiments results
are based on FIT IoT-LAB testbed:
1. Add acknowledgements to FIT IoT-LAB in introduction or conclusion of the publication
2. Add citation to the reference article of FIT IoT-LAB. See details here:
  https://www.iot-lab.info/charter/
3. Send email to admin@iot-lab.info once your publication has been accepted in order
  to update hall of fame:
  https://www.iot-lab.info/publications/

Post your issues on:

the user mailing-list: users@iot-lab.info
or the bug-tracker: https://github.com/iot-lab/iot-lab/issues
Last login: Sat Apr 11 09:03:52 2020 from 192.168.6.254
***********@lille:~$ nc m3-100 20000
ifconfig
ifconfig
Iface 7 HWaddr: 11:15 Channel: 24 Page: 0 NID: 0xb522
Long HWaddr: 0A:55:F7:65:10:6B:11:15
TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4
AUTOACK ACK_REQ CSMA L2-PDU:102 MTU:1280 HL:64 RTR
6LO IPHC
Source address length: 8
Link type: wireless
inet6 addr: fe80::855:f765:106b:1115 scope: link VAL
inet6 group: ff02::2
inet6 group: ff02::1
inet6 group: ff02::1:ff6b:1115
inet6 group: ff02::1a
```
    Statistics for Layer 2
      RX packets 7  bytes 287
      TX packets 7 (Multicast: 7)  bytes 287
      TX succeeded 7 errors 0
    Statistics for IPv6
      RX packets 7  bytes 434
      TX packets 7 (Multicast: 7)  bytes 434
      TX succeeded 7 errors 0
```

ifconfig
ifconfig
Iface 7 HWaddr: 11:15 Channel: 24 Page: 0 NID: 0xb522
Long HWaddr: 0A:55:F7:65:10:6B:11:15
TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4
AUTOACK ACK_REQ CSMA L2-PDU:102 MTU:1280 HL:64 RTR
6LO IPHC
Source address length: 8
Link type: wireless
inet6 addr: fe80::855:f765:106b:1115 scope: link VAL
inet6 group: ff02::2
inet6 group: ff02::1
inet6 group: ff02::1:ff6b:1115
inet6 group: ff02::1a

      Statistics for Layer 2
        RX packets 12  bytes 502
        TX packets 14 (Multicast: 14)  bytes 588
        TX succeeded 14 errors 0
      Statistics for IPv6
        RX packets 12  bytes 754
        TX packets 14 (Multicast: 14)  bytes 882
        TX succeeded 14 errors 0

ping6 2a00:1450:4007:80f::2003
ping6 2a00:1450:4007:80f::2003
12 bytes from 2a00:1450:4007:80f::2003: icmp_seq=0 ttl=51 rssi=-48 dBm time=143.454 ms
12 bytes from 2a00:1450:4007:80f::2003: icmp_seq=1 ttl=51 rssi=-48 dBm time=72.730 ms
12 bytes from 2a00:1450:4007:80f::2003: icmp_seq=2 ttl=51 rssi=-48 dBm time=72.616 ms

— 2a00:1450:4007:80f::2003 PING statistics —
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 72.616/96.266/143.454 ms

ping6 -c 1 2a00:1450:4007:80f::2003
ping6 -c 1 2a00:1450:4007:80f::2003
12 bytes from 2a00:1450:4007:80f::2003: icmp_seq=0 ttl=51 rssi=-49 dBm time=76.854 ms

— 2a00:1450:4007:80f::2003 PING statistics —
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 76.854/76.854/76.854 ms

ping6 -c 1 2a00:1450:4007:80f::2003
ping6 -c 1 2a00:1450:4007:80f::2003
12 bytes from 2a00:1450:4007:80f::2003: icmp_seq=0 ttl=51 rssi=-49 dBm time=69.282 ms

— 2a00:1450:4007:80f::2003 PING statistics —
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 69.282/69.282/69.282 ms

noeud101 (routeur de bord) :
ovyan@43e9ec33f96a:~/work/iot-lab-training$ ssh $IOTLAB_LOGIN@lille.iot-lab.infoLinux lille 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64
Welcome FIT IoT-LAB users

Charter:

FIT IoT-LAB is shared among several users, so make reasonable use of the platform
Quote FIT IoT-LAB in your scientific papers. Usage of FIT IoT-LAB is free of charge.
In return, you must quote FIT IoT-LAB in your publication if your experiments results
are based on FIT IoT-LAB testbed:
1. Add acknowledgements to FIT IoT-LAB in introduction or conclusion of the publication
2. Add citation to the reference article of FIT IoT-LAB. See details here:
  https://www.iot-lab.info/charter/
3. Send email to admin@iot-lab.info once your publication has been accepted in order
  to update hall of fame:
  https://www.iot-lab.info/publications/

Post your issues on:

the user mailing-list: users@iot-lab.info
or the bug-tracker: https://github.com/iot-lab/iot-lab/issues
Last login: Sun Apr 12 08:21:36 2020 from 192.168.6.254
****************@lille:~$ nc m3-101 20000

********** mise en place du routeur de bord *********************

~}!uhcp_client(): no reply received
~~}!uhcp_client():P@~^C

funa8d7b22f8a@lille:~$ ip addr show | grep tap
funa8d7b22f8a@lille:~$ ip -6 route
2001:660:4403:47f::/64 dev ens3 proto kernel metric 256 pref medium
fe80::/64 dev ens3 proto kernel metric 256 pref medium
fe80::/64 dev ens7 proto kernel metric 256 pref medium
default via 2001:660:4403:47f:ff:: dev ens3 metric 1024 pref medium

*****************@lille:~$ sudo ethos_uhcpd.py m3-101 tap0 2001:660:4403:0480::1/64net.ipv6.conf.tap0.forwarding = 1
net.ipv6.conf.tap0.accept_ra = 0
Switch from ‘root’ to ‘funa8d7b22f8a’
Joining IPv6 multicast group…
entering loop…
Switch from ‘root’ to ‘funa8d7b22f8a’
----> ethos: sending hello.
----> ethos: activating serial pass through.
----> ethos: hello reply received
uhcp_client(): no reply received
uhcp_client(): sending REQ…
got packet from fe80::219:acff:fe40:25fa port 12345
got packet from fe80::2421:21ff:fe7f:7101 port 49451
uhcp: push from fe80::2421:21ff:fe7f:7101:49451 prefix=2001:660:4403:480::/64
gnrc_uhcpc: uhcp_handle_prefix(): configured new prefix 2001:660:4403:480:28ac:f965:106b:1115/64
uhcp_client(): sending REQ…

terminal de capture :
ovyan@43e9ec33f96a:~/work/iot-lab-training$ ssh $IOTLAB_LOGIN@lille.iot-lab.infoLinux lille 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64
Welcome FIT IoT-LAB users

Charter:

FIT IoT-LAB is shared among several users, so make reasonable use of the platform
Quote FIT IoT-LAB in your scientific papers. Usage of FIT IoT-LAB is free of charge.
In return, you must quote FIT IoT-LAB in your publication if your experiments results
are based on FIT IoT-LAB testbed:
1. Add acknowledgements to FIT IoT-LAB in introduction or conclusion of the publication
2. Add citation to the reference article of FIT IoT-LAB. See details here:
  https://www.iot-lab.info/charter/
3. Send email to admin@iot-lab.info once your publication has been accepted in order
  to update hall of fame:
  https://www.iot-lab.info/publications/

Post your issues on:

the user mailing-list: users@iot-lab.info
or the bug-tracker: https://github.com/iot-lab/iot-lab/issues
Last login: Sun Apr 12 08:31:40 2020 from 192.168.6.254

**************@lille:~$ sniffer_aggregator -r -d -o - | tshark -V -i - > sniffer.pcap
Capturing on ‘Standard input’
1586673605.365088;Aggregator started
^C
1586673670.367997;0 packets captured
1586673670.368547;Stopping
***************@lille:~$

fsaintma

Bonjour @DLRprod
J’avoue qu’avec vos traces j’ai du mal a comprendre ce qui se passe.
Par contre si votre setup est m3-101 (Border Router=BR) et le noeud m3-100 qui communique avec le BR en radio & qui peut faire un ping6 sur l’internet globale (2a00:1450:4007:80f::2003) alors il a forcement une adresse IPv6 globale.
Il peut se passer un peu de temps avant que le noeud m3-100 recupere son @IPv6 globale avec le Neighbor Discovery Protocol entre lui & le BR.Avez-vous fait le ifconfig apres le ping6 ?
Pour la partie sniffer il faut bien activer le monitoring avec les commandes de creation et d’update de profile. Avez vous fait les commandes ?
Cordialement.

DLRprod

Bonjour,

concernant l’adresse IPv6 globale , j’ai réussi à la faire apparaître. Pourtant , j’ai l’impression d’avoir procédé exactement comme les fois précédentes…Mystère donc!

Concernant les commandes de création et d’update de profile, je n’arrive pas à créer un nouveau profile. voilà le code que j’ai :

!iotlab-profile addm3 -n sniff -sniffer -channels $CHANNEL

HTTP Error 500:
{“code”:500,“message”:“Profile sniff already exist”}

!iotlab-node --update-profile sniff -e $SITE,m3,$BR_ID

{
“0”: [
“m3-100.lille.iot-lab.info”
]
}

Merci de toute aide.

fsaintma

Ok @DLRprod le probleme pour le sniffing c’est que vous aviez deja cree un profile. Ce profile est definit pour un channel (random) donné au debut du notebook. Ce n’est donc pas sur que vous soyez sur le bon channel. Le plus simple est peut etre de changer le nom du profile dans la commande (option -n) pour en creer un autre. Par exemple si vous obtenez le channel 11.
Dans le notebook:
!iotlab-profile addm3 -n sniffer_11 -sniffer -channels 11
!iotlab-node --update-profile sniffer_11 -e $SITE,m3,$BR_ID
Attention il faut bien que les deux firmwares soient compiles avec cette valeur de channel.
Apres vous lancez le sniffer_aggregator et executez un ping6 du noeud derriere le BR pour capturer des traces et generer du traffic.
Cordialement.