• State Verified Answer
  • Replies 1 reply
  • Subscribers 62 subscribers
  • Views 1160 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 120372
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Reconnect Problem IoT lwIP

Carl

Hi @ all,

I am working with IoT SDK 0.9 and nRF52DK.

I have trouble with the lwIP CoAP client example. Everything works so far, the board is connected and I'm able to ping it via Raspberry Pi from my PC using the boards global IPv6 address.

However, once I disconnect the board (e.g. by link loss or manual disconnect from the raspberry), and connect it again, ping and all other IPv6 communication do not work anymore.

Trying to send CoAP messages results in an internal error (code 3).

I checked the code. After disconnect "connectable_mode_enter()" is called and within "ipv6_medium_connectable_mode_enter()". App log shows no errors, also not during reconnect (IPv6 interface seems to be up).

Only resetting the nRF52DK works.

Any ideas?

Thanks in advance, Carl

  • 0

    Hi,

    If you look in the release notes of the IoT SDK you can read this:

    • Once BLE link is disconnected, lwIP example applications no longer get a global prefix. The only way to start using the examples with the global prefix again is to restart the application.

    You can use the Nordic IPv6 stack instead of the lwIP stack (the ipv6 folder in the SDK, instead of the lwip folder). I tested now, and it works when reconnecting.

Related