Archive 07/10/2020.

Problème avec le TP9 (résolu)

mathiae

Bonjour,

Je n’arrive pas à faire fonctionner le TP9. Vous trouverez ci-dessous une copie (ce qui se passe dans le notebook et ce qui se passe sur le terminal). Cette copie est assez longue.

Cordialement

avec le notebook

Submit an experiment on IoT-LAB

Choose your site (grenoble|lille|strasbourg):

%env SITE=lille

env: SITE=lille

Submit an experiment with two nodes

!iotlab-experiment submit -d 60 -l 2,archi=m3:at86rf231+site=$SITE

{
“id”: 201948
}

Wait for the experiment to be in the Running state:

!iotlab-experiment wait --timeout 30 --cancel-on-timeout

Waiting that experiment 201948 gets in state Running
“Running”

Note: If the command above returns the message Timeout reached, cancelling experiment <exp_id>, try to re-submit your experiment later or try on another site.

Check the nodes allocated to the experiment

!iotlab-experiment get -ni

{
“items”: [
{
“lille”: {
“m3”: “100-101”
}
}
]
}

Radio settings

If you are running this training at the same time as other people on the testbed, it is a good idea to change the default radio configuration to avoid too much collision with others.

Use the following cell to give you random values for channel and PAN ID.

import os,binascii,random

pan_id = binascii.b2a_hex(os.urandom(2)).decode()

channel = random.randint(11, 26)

print(‘Use CHANNEL={}, PAN_ID=0x{}’.format(channel, pan_id))

Use CHANNEL=26, PAN_ID=0x3096

Set environment variables for further use by modifying the values in the cell below with those obtained and run it:

%env CHANNEL=26

%env PAN_ID=0x3096

env: CHANNEL=26
env: PAN_ID=0x3096

Communication between two nodes

Compile the RIOT gnrc_networking example:

%env APP_DIR=…/…/RIOT/examples/gnrc_networking

!make -C $APP_DIR BOARD=iotlab-m3 DEFAULT_CHANNEL=$CHANNEL DEFAULT_PAN_ID=$PAN_ID

env: APP_DIR=…/…/RIOT/examples/gnrc_networking
make: Entering directory ‘/home/jovyan/work/iot-lab-training/riot/RIOT/examples/gnrc_networking’
Building application “gnrc_networking” for “iotlab-m3” with MCU “stm32f1”.

“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/boards/iotlab-m3
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/boards/common/iotlab
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/core
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/cpu/stm32f1
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/cpu/cortexm_common
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/cpu/cortexm_common/periph
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/cpu/stm32_common
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/cpu/stm32_common/periph
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/cpu/stm32f1/periph
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/drivers
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/drivers/at86rf2xx
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/drivers/netdev_ieee802154
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/drivers/periph_common
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/auto_init
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/auto_init/netif
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/div
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/evtimer
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/fmt
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/isrpipe
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/luid
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/crosslayer/inet_csum
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/netapi
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/netif
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/netif/hdr
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/netif/ieee802154
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/netreg
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/icmpv6
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/icmpv6/echo
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/icmpv6/error
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/ipv6
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/ipv6/hdr
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/ipv6/nib
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/ndp
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/sixlowpan
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/sixlowpan/ctx
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/sixlowpan/frag
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/sixlowpan/frag/fb
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/sixlowpan/frag/rb
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/sixlowpan/iphc
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/network_layer/sixlowpan/nd
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/pkt
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/pktbuf
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/pktbuf_static
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/pktdump
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/routing/rpl
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/gnrc/transport_layer/udp
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/link_layer/ieee802154
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/link_layer/l2util
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/netif
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/network_layer/icmpv6
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/network_layer/ipv6/addr
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/network_layer/ipv6/hdr
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/network_layer/sixlowpan
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/net/transport_layer/udp
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/newlib_syscalls_default
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/od
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/pm_layered
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/ps
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/random
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/random/tinymt32
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/shell
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/shell/commands
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/stdio_uart
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/trickle
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/tsrb
“make” -C /home/jovyan/work/iot-lab-training/riot/RIOT/sys/xtimer
text data bss dec hex filename
85956 556 19232 105744 19d10 /home/jovyan/work/iot-lab-training/riot/RIOT/examples/gnrc_networking/bin/iotlab-m3/gnrc_networking.elf
make: Leaving directory ‘/home/jovyan/work/iot-lab-training/riot/RIOT/examples/gnrc_networking’

Then, flash the two nodes with this firmware:

!iotlab-node --flash $APP_DIR/bin/iotlab-m3/gnrc_networking.bin

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

sur le terminal

jovyan@3931d51b9463:~/work/iot-lab-training$ ssh $IOTLAB_LOGIN@lille.iot-lab.info
Linux 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 11:18:23 2020 from 192.168.6.254
    fun26b04a9ef3@lille:~$ nc m3-201948 20000
    m3-201948: forward host lookup failed: Unknown host
    fun26b04a9ef3@lille:~$
PDeguignet

Je pense comprnedre votre pb:

la commande sur le terminal devrait etre nc-m3-100 car 100 est le no de node
par erreur vous avez mis le no de l’experience 201948
il faut donc ouvrir 2 terminaux et se connecter avec nc-m3-100 pour l’un et nc-m3-101 pour l’autre dans cet exemple.
en esperant etre utile…

mathiae

Merci de votre mail, c’est très clair. Je vais essayer à nouveau.