Skip to content
This repository was archived by the owner on Apr 24, 2019. It is now read-only.
This repository was archived by the owner on Apr 24, 2019. It is now read-only.

Network problems with 7 or more clients connected to the mbed Device Connector #266

@rspelta

Description

@rspelta

Description

  • Type: Bug?

With seven or more clients connected to the mbed Device Connector some of them are not listed temporally or disappear until I reset the client.

We are using mbed-os-example-client for 10 boards, 3 of them are NUCLEO_F429ZI+X-NUCLEO-IDS01A4 boards and the others are sensor-node boards (it's a new kind of board, we are developing on it, @MarceloSalazar knows it).
The border router uses the nanostack-border-route repository and it is a NUCLEO_F429ZI+X-NUCLEO-IDS01A4, it uses a ethernet cable connected to the internet router (with enabled 6to4 tunneling). The mesh is via Spirit, we have worked with Wolfgang (@betzw) in order to have the spirit driver stable.

The NUCLEO_F429ZI boards use the lastest commit of the repositories, the sensor-node board come from the versions:

mbed-os-sensor-node (5f27acc)
|- easy-connect (6fb5842becae)
| |- atmel-rf-driver (57f22763f4d3)
| |- esp8266-driver (4ed87bf7fe37)
| | - ESP8266\ATParser (269f14532b98) | |- mcr20a-rf-driver (d8810e105d7d) | - stm-spirit1-rf-driver (ac7a4f477222)
|- mbed-client (f8f0fc8b9321)
| |- mbed-client-c (c739b8cbcc57)
| |- mbed-client-classic (f673b8b60779)
| - mbed-client-mbed-tls (7e1b6d815038) |- mbed-os (ed4febefdede) - pal (4e46c0ea8706)

Every client has its security.h file and a different MAC address.
We have done this test:

  1. turn on the border router and wait until it is ready
  2. turn on one client
  3. wait to see it is connected to the mbed connector website and try to request information via API console
  4. go to point 2

here you can read the trace of the border router:
https://pastebin.com/ti8U3HgS

From the sniffer seems that the lost clients (I mean who disappear from the mbed connector list) continue to communicate with the border router. We don't have information about how the nanostack works so we have problem to get a better idea what is going on.

To try to understand what happen we have:

  • a "sniffer" node in order to see the "frames on the air"
  • the console of the border router (attacched the log of the border, the trace is minimal we didn't turn it off completely)
  • the console of the nodes (just to know if it is registered to the mbed connector the first time)

Our goal is to have more than 10 boards connected to the mbed Device Connector.
What can we do?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions