[riot-devel] Border-router and multicast

Martine Lenders mail at martine-lenders.eu
Thu May 12 13:34:15 CEST 2016


Hi Baptiste,
yeah in that case multicast seems like the best thing to go. But how about
using an actual global address then: (ff:1e::1 e.g.; 10 flag =
non-permanent, e scope = global). With the hint by Kaspar I was able to get
the pings through the interface, but apparently the border router does not
forward the address.
Will investigate.

Cheers,
Martine

2016-05-12 11:39 GMT+02:00 Baptiste Clenet <bapclenet at gmail.com>:

> Hi,
>
> Martine, what I want:
> My set up:
> |Linux + RIOT BORDER ROUTER|
>
> |RIOT gnrc_networking A|
> |RIOT gnrc_networking B|
> |RIOT gnrc_networking C|
> |RIOT gnrc_networking D|
>
> I run a program on Linux which sends some UDP data to A B C D nodes.
> I want to use multicast in my program instead of one board by one bard
> Is it clearer?
>
> Cheers,
>
> 2016-05-11 21:55 GMT+02:00 Kaspar Schleiser <kaspar at schleiser.de>:
> > Hey,
> >
> > On 05/11/2016 09:42 PM, Martine Lenders wrote:
> >> (2) I'm not sure you add multicast routing entries this way in Linux.
> >
> > You don't. If really desired, you have to use the "local" routing table.
> >
> > # ip -6 route list table local
> >
> > Kaspar
> > _______________________________________________
> > devel mailing list
> > devel at riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> --
> Baptiste
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20160512/689550db/attachment.html>


More information about the devel mailing list