Connecting LAN IPv6 with thread IPv6

[pieter....@basalte.be]

Hi,

I think this should be simple enough, but I can't get it to work.

How can I allow LAN devices in the same network as the border router with IPv6, to send requests to Thread devices? Should this work automagically or are additional services like radvd required to advertise a route?

Also following the guide at https://openthread.io/guides/border-router/external-commissioning?comm=ot-commissioner I get

# ot-ctl netdataregister

Error 35: InvalidCommand

Communication between thread devices works fine.

My interfaces on the border router are

# ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

    link/ether f8:dc:7a:45:ff:a2 brd ff:ff:ff:ff:ff:ff

    inet 192.168.86.234/24 brd 192.168.86.255 scope global eth0

       valid_lft forever preferred_lft forever

    inet6 2a02:1812:2c16:7e00:fadc:7aff:fe45:ffa2/64 scope global dynamic mngtmpaddr

       valid_lft 40656sec preferred_lft 11856sec

    inet6 fe80::fadc:7aff:fe45:ffa2/64 scope link

       valid_lft forever preferred_lft forever

3: wpan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 500

    link/void

    inet6 fd11:22::1a1a:a6db:cf84:2ea8/64 scope global

       valid_lft forever preferred_lft forever

    inet6 fd62:72ac:688:c709:0:ff:fe00:fc00/64 scope global

       valid_lft forever preferred_lft forever

    inet6 fd62:72ac:688:c709:0:ff:fe00:f000/64 scope global

       valid_lft forever preferred_lft forever

    inet6 fd62:72ac:688:c709:c46a:422f:b9a4:5e45/64 scope global

       valid_lft forever preferred_lft forever

    inet6 fe80::58ed:4c75:b306:12c2/64 scope link

       valid_lft forever preferred_lft forever

Thanks,

Pieter

[Jonathan Hui]

The most automatic way is to have OpenThread Border Router send ICMPv6 Router Advertisements on the Wi-Fi interface, with a Route Information Option containing a IPv6 prefix assigned to the Thread network. This will all Wi-Fi devices to route traffic to the Thread network.

Alternatively, you can manually configure IPv6 routes as mentioned in a prior thread.

The `netdataregister` command was recently changed to `netdata register`, since we added a `netdata` subcommand - see src/cli/README_NETDATA.md.

Hope that helps.

--

Jonathan Hui

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/1f1a25ba-3388-49d3-9bd5-0f8d25be6c25n%40googlegroups.com.

[Pieter De Gendt]

Hi Jonathan,

Thanks for the fast response.

Would the advertisements work the same on a wired interface as on the wireless? Is the on-mesh prefix added to the thread network that has to be advertised or a new ULA prefix?

How would the linux kernel know how to route message received on eth0 to wpan0?

Thanks,

Pieter

---

From: Jonathan Hui <jon...@google.com>
Sent: Wednesday 28 October 2020 04:28
To: Pieter De Gendt <pieter....@basalte.be>
Cc: openthread-users <openthre...@googlegroups.com>
Subject: Re: Connecting LAN IPv6 with thread IPv6

 

[Pieter De Gendt]

Hi Jonathan,

I'm not sure why, but my posts get deleted on the google groups conversation?

Also, is bridging interfaces eth0 (LAN) and wpan0 (THREAD) a bad idea?

Thanks,

Pieter

---

From: Pieter De Gendt <pieter....@basalte.be>
Sent: Wednesday 28 October 2020 09:03
To: Jonathan Hui <jon...@google.com>

[Jonathan Hui]

On Wed, Oct 28, 2020 at 1:03 AM Pieter De Gendt <pieter....@basalte.be> wrote:

Would the advertisements work the same on a wired interface as on the wireless?

ICMPv6 Router Advertisements may be used the same way over either Ethernet or Wi-Fi based links.

 

Is the on-mesh prefix added to the thread network that has to be advertised or a new ULA prefix?

Any on-mesh prefix (except the mesh-local prefix) may be advertised in the ICMPv6 Router Advertisement. The on-mesh prefix can be a ULA or globally-routable prefix.

How would the linux kernel know how to route message received on eth0 to wpan0?

The wpan0 interface should be configured with the IPv6 prefix(es). The output of ifconfig should show a list of IPv6 addresses assigned to the interface with "/64" indicating the prefix.

[Jonathan Hui]

On Wed, Oct 28, 2020 at 12:08 PM pieter....@basalte.be <pieter....@basalte.be> wrote:

I would assume this works the same for a wired LAN? The prefix to advertise, is it the same as with the  ot-ctl prefix add fd11:22::/64 pasor command? 

Wouldn't it make sense to add this scenario to the documentation, I think it would help a lot of people?

Yes, we are hoping to publish a network configuration guide for this. At the same time, we are also looking to implement this functionality so that it happens automatically.

--

Jonathan Hui

 

[pieter....@basalte.be]

That sounds great!

I managed to get it working on an IPv6 capable LAN network by running radvd daemon on the border router with the following config:

interface eth0 {

    AdvSendAdvert on;

    AdvDefaultPreference low;

    route fd11:22::/64 {

        AdvRoutePreference high;

        AdvRouteLifetime 3600;

    };

};

Is there a way to discover the thread nodes from the LAN part with this route? 

Thanks,

Pieter

[pieter....@basalte.be]

I do have to add the prefix each time I reboot, is there a way to configure/persist this?

[Jonathan Hui]

On Thu, Oct 29, 2020 at 8:55 AM pieter....@basalte.be <pieter....@basalte.be> wrote:

I do have to add the prefix each time I reboot, is there a way to configure/persist this?

OpenThread does not provide this directly. You could have a script that runs after boot to configure the prefix.

--

Jonathan Hui