Setting up LwM2M server with nrf IOT SDK

RE: Setting up LwM2M server with nrf IOT SDK

Ole Bauck — Mon, 08 Aug 2016 09:13:04 GMT

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

RE: Setting up LwM2M server with nrf IOT SDK

arjunkamath1 — Mon, 08 Aug 2016 06:17:10 GMT

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.

RE: Setting up LwM2M server with nrf IOT SDK

arjunkamath1 — Thu, 04 Aug 2016 14:12:11 GMT

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

RE: Setting up LwM2M server with nrf IOT SDK

arjunkamath1 — Thu, 04 Aug 2016 06:04:41 GMT

Alright, this makes so much more sense. Thanks :) At least I understood something correctly. I'll try this out and hopefully it will work. Also, is there a way to find out the exact Leshan and IoT SDK versions used in this.. this will help in debugging.

RE: Setting up LwM2M server with nrf IOT SDK

Ole Bauck — Wed, 03 Aug 2016 14:56:23 GMT

Yes you should run the ifconfig eth0 add 2001:db81::1/64 and ifconfig eth0 add 2001:db81::2/64 on the ubuntu server. This is because the bootstrap server and the leshan server use the same port (DTLS for security).

I did not actually try it out (which is why there are errors) so I don't know if the problem is the Leshan version.

You need to add the route::/0 {}; to the radvd config to route between the interfaces, good catch ;)

I will update my answer with the correct info.

RE: Setting up LwM2M server with nrf IOT SDK

arjunkamath1 — Wed, 03 Aug 2016 12:27:27 GMT

teamarin.net/.../ has a similar configuration right? Doesn't the " route::/0 {}; " part add the routes between interfaces?

RE: Setting up LwM2M server with nrf IOT SDK

arjunkamath1 — Wed, 03 Aug 2016 09:40:38 GMT

Hi Ole,

Thanks for the response. Actually, we first tried with bootstrap and management server on the RasPi and we managed to get something to the bootstrap server. There was an error, and we felt that this was since we used a recent version of Leshan and something have probably changed. Can you let us know which release of Leshan worked for you?

Secondly, regarding your configuration above, I have some questions. Firstly, here's a picture of the configuration as I understand: www.imageno.com/mfm8iqo3lximpic.html. With this the nrf1 will get a IP from 2001:db82::/64 and the ubuntu server gets an IP from 2001:db81::/64

Now, should I run ifconfig eth0 add 2001:db8::1/64 and ifconfig eth0 add 2001:db8::2/64 on the ubuntu server? Shouldn't the IPs belong to the subnet 2001:db81::/64 or am I missing something?

Don't I also need to add routes on the RasPi?

RE: Setting up LwM2M server with nrf IOT SDK

Ole Bauck — Tue, 02 Aug 2016 15:47:08 GMT

EDIT 2016:08:03: Changed the radvd config and the address in the interfaces added on the server side according to comments from this date.

The example is using a linux machine with a Bluetooth dongle running the servers.

If you want a raspberry pi to do the BLE routing and another machine running the servers, it gets a bit more complicated. I suggest that you try the example on one machine first, before trying to do it with raspberry pi as the router.

2001:db8::1 is the address of the bootstrap server and 2001:db8::2 is the address of the Leshan server.

If you want to do it on two machines this is what you have to do:

Create two addresses for the two servers on Ethernet interface (on the device hosting the servers): ifconfig eth0 add 2001:db81::1/64 ifconfig eth0 add 2001:db81::2/64
Configure radvd to distribute a prefix on the Ethernet interface (and change bt0 to avoid conflict):

See here.

interface eth0
{
    AdvSendAdvert on;
    prefix 2001:db81::/64
    {
        AdvOnLink on;
        AdvAutonomous on;
        AdvRouterAddr on;
    };

    route ::/0
    {
    };
};

interface bt0
{
    AdvSendAdvert on;
    prefix 2001:db82::/64
    {
        AdvOnLink off;
        AdvAutonomous on;
        AdvRouterAddr on;
    };
};

When adding an interface to bt0 you have to choose something other than 2001:db8::1/64 or 2001:db8::2/64.