This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Setting up LwM2M server with nrf IOT SDK

Hi,

I have a nordic chip (nrf2832) and I am trying to use it as a LWM2M client and register it to a LWM2M Server. I want to achieve this: developer.nordicsemi.com/.../LWM2M_client.svg

I have already done the steps described in developer.nordicsemi.com/.../a00089.html

root@raspberrypi:/home/pi# ping6 -I bt0 ff02::1 PING ff02::1(ff02::1) from fe80::ba27:ebff:fed7:2a95 bt0: 56 data bytes 64 bytes from fe80::ba27:ebff:fed7:2a95: icmp_seq=1 ttl=64 time=0.162 ms 64 bytes from fe80::206:99ff:feea:bb16: icmp_seq=1 ttl=64 time=186 ms (DUP!)

I am now stuck in the steps described in developer.nordicsemi.com/.../a00082.html

According to the steps, I should give these commands:

ifconfig bt0 add 2001:db8::1/64 ifconfig bt0 add 2001:db8::2/64

It also says that the commands assume that the bt0 interface is already up running.

My understanding is that 2001:db8::1/64 is the IPV6 address of bootstrap server and 2001:db8::2 is the IPv& address of management server, right? However, bt0 interface is on the raspberry pi and NOT the server running Leshan server, right?

So where exactly do I run 'ifconfig bt0 add 2001:db8::1/64' and 'ifconfig bt0 add 2001:db8::2/64'? Raspberry Pi or ubuntu machine?

  • Hi, We've spent an entire day on this and we haven't get this to work :(

    I added interfaces on the RasPi sudo ifconfig eth0 add 2001:db81::1 sudo ifconfig bt0 add 2001:db82::1

    Strangely enough I can ping 2001:db82::1 from my laptop but not 2001:db81::1 which is the actual router address. From the RasPi I can ping other PCs connected to the LAN which is great. On the RasPi I run tcpdump and I can actually see the bootstrap request coming and directed to the right address, but they are not forwarded apparently. I feel like it's a routing problem... so maybe this helps? sudo ip route add 2001:db81::/64 dev eth0.. but it didn't

  • We got it working here... Everything Ole mentioned is correct, but we needed to do a few additional steps. I'll write them here for future reference.

    Firstly, having a look at the diagram here helped a lot: teamarin.net/.../

    As per that, we needed to add the gateway addresses on the rasPi manually: sudo ifconfig eth0 add 2001:db81::1/64 sudo ifconfig bt0 add 2001:db82::1/64

    Then, we also needed to add routes on the rasPi (not sure why this wasn't automatically added): sudo ip route add 2001:db81::/64 dev eth0 sudo ip route add 2001:db82::/64 dev bt0 sudo ip route add default dev eth0

    After this, we were able to see bootstrap message from nRF to our bootstrap server. We're still having version issues, the bootstrapping server complains, but we're looking into it.

  • Good that you figured it out :) I guess the reason the route was not automatically added from the radvd config was the same reason that the btx interfaces could not be added automatically, infocenter.nordicsemi.com/.../iot_sdk_user_guides_radvd.html

Related