Re: [riot-devel] Border-router and multicast
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@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Border-router and multicast
Hi again,
2016-05-11 21:42 GMT+02:00 Martine Lenders :
> Hi Baptist,
>
> First of all, sorry for the late reply.
>
> 2016-05-11 10:05 GMT+02:00 Baptiste Clenet :
>
>> Ok Martine,
>>
>> In the start_network.sh, create_tap(), you route
>> ip route add ${PREFIX} via fe80::2 dev ${TAP}
>> Ok so if I want multicast, I should add
>> ip route add ff04::1/64 via fe80::2 dev ${TAP}
>> But it does not work
>
>
> This doesn't surprise me at all: (1) multicast addresses don't have
> prefixes as unicast addresses have so adding with /64 doesn't make much
> sense. (2) I'm not sure you add multicast routing entries this way in
> Linux. Maybe Alex can give us a hint here.
>
> Fact is: when I ping to ff04::1 from Linux (`ping6 -I tap0 ff04::1`) there
> isn't even any ping traffic going over the tap interface (checked with
> wireshark). So it really seems to be some kind of routing problem.
>
Pinging ff04::1 from the border router itself worked by the way.
Baptiste, what was it you originally wanted to do? Maybe we can find
another solution.
Cheers,
Martine
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Border-router and multicast
Hi Baptist,
First of all, sorry for the late reply.
2016-05-11 10:05 GMT+02:00 Baptiste Clenet :
> Ok Martine,
>
> In the start_network.sh, create_tap(), you route
> ip route add ${PREFIX} via fe80::2 dev ${TAP}
> Ok so if I want multicast, I should add
> ip route add ff04::1/64 via fe80::2 dev ${TAP}
> But it does not work
This doesn't surprise me at all: (1) multicast addresses don't have
prefixes as unicast addresses have so adding with /64 doesn't make much
sense. (2) I'm not sure you add multicast routing entries this way in
Linux. Maybe Alex can give us a hint here.
Fact is: when I ping to ff04::1 from Linux (`ping6 -I tap0 ff04::1`) there
isn't even any ping traffic going over the tap interface (checked with
wireshark). So it really seems to be some kind of routing problem.
Cheers,
Martine
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Unifying the interfaces of the digest functions
Just created a pull request for it. https://github.com/RIOT-OS/RIOT/pull/5430 On Mit, 2016-05-11 at 12:31 +0200, Emmanuel Baccelli wrote: > On Wed, May 11, 2016 at 12:26 PM, Oleg Hahm wrote: > > > > > Hi Matthias! > > > > On Wed, May 11, 2016 at 12:12:42PM +0200, Mathias Tausig wrote: > > > > > > The interafces used by the cryptographic digest functions sha256, sha1 > > and md5 > > > > > > (xx_init, xx_update, xx_final) are very inconsistent at the moment. > > > Would a patch which would consolidate this situation be desirable? > > Anything that makes the API more consistent is desirable! Please go ahead! > > > > +1 > > > > > > Cheers, > > Oleg > > -- > > if(ct<0) > > ct=2;/* Shit happens.. */ > > linux-2.6.6/drivers/net/wan/z85230.c > > > > ___ > > devel mailing list > > devel@riot-os.org > > https://lists.riot-os.org/mailman/listinfo/devel > > > > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel signature.asc Description: This is a digitally signed message part ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Unifying the interfaces of the digest functions
On Wed, May 11, 2016 at 12:26 PM, Oleg Hahm wrote: > Hi Matthias! > > On Wed, May 11, 2016 at 12:12:42PM +0200, Mathias Tausig wrote: > > The interafces used by the cryptographic digest functions sha256, sha1 > and md5 > > (xx_init, xx_update, xx_final) are very inconsistent at the moment. > > Would a patch which would consolidate this situation be desirable? > > Anything that makes the API more consistent is desirable! Please go ahead! > > +1 > Cheers, > Oleg > -- > if(ct<0) > ct=2;/* Shit happens.. */ > linux-2.6.6/drivers/net/wan/z85230.c > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Unifying the interfaces of the digest functions
Hi Matthias! On Wed, May 11, 2016 at 12:12:42PM +0200, Mathias Tausig wrote: > The interafces used by the cryptographic digest functions sha256, sha1 and md5 > (xx_init, xx_update, xx_final) are very inconsistent at the moment. > Would a patch which would consolidate this situation be desirable? Anything that makes the API more consistent is desirable! Please go ahead! Cheers, Oleg -- if(ct<0) ct=2;/* Shit happens.. */ linux-2.6.6/drivers/net/wan/z85230.c signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Unifying the interfaces of the digest functions
Hy! The interafces used by the cryptographic digest functions sha256, sha1 and md5 (xx_init, xx_update, xx_final) are very inconsistent at the moment. Would a patch which would consolidate this situation be desirable? cheers Mathias signature.asc Description: This is a digitally signed message part ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] SAMR21: Event
Hi, Has anyone tried to use Event peripheral on samr21? p401/1204 http://www.mouser.com/ds/2/36/Atmel-42223-SAM-R21_Datasheet-604417.pdf Cheers, -- Baptiste ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Border-router and multicast
Ok Martine,
In the start_network.sh, create_tap(), you route
ip route add ${PREFIX} via fe80::2 dev ${TAP}
Ok so if I want multicast, I should add
ip route add ff04::1/64 via fe80::2 dev ${TAP}
But it does not work
2016-05-10 19:32 GMT+02:00 Martine Lenders :
> Sorry, was (and still am) otherwise occupied. Will look into it tonight,
> tomorrow at the latest though.
>
> Regards,
> Martine
>
> 2016-05-10 18:05 GMT+02:00 Baptiste Clenet :
>>
>> Ok Martine, Have you found any solution yet?
>>
>> 2016-05-10 9:48 GMT+02:00 Martine Lenders :
>> > Hi Baptiste,
>> > since IEEE 802.15.4 itself is not a multicast medium (it only supports
>> > broadcast), and we don't have MLD implemented at this point (which
>> > configures routers for multicast), multicast is indeed tricky at the
>> > moment.
>> > Let me try something out and I come back to you.
>> >
>> > Cheers,
>> > Martine
>> >
>> > 2016-05-10 9:03 GMT+02:00 Baptiste Clenet :
>> >>
>> >> Thanks Alex for your answer.
>> >>
>> >> 2016-05-09 19:07 GMT+02:00 Alexander Aring :
>> >> > Hi,
>> >> >
>> >> > On Mon, May 09, 2016 at 06:20:48PM +0200, Baptiste Clenet wrote:
>> >> >> 2016-05-09 16:44 GMT+02:00 Alexander Aring :
>> >> >> > On Mon, May 09, 2016 at 04:24:34PM +0200, Baptiste Clenet wrote:
>> >> >> >> Hi Martine,
>> >> >> >> Thank you for the answer.
>> >> >> >> Ok ff04::1 is also a multicast address so I add it to every board
>> >> >> >> with
>> >> >> >> gnrc_networking and I should be able to ping them with this
>> >> >> >> multicast
>> >> >> >> address.
>> >> >> >> Shouldn't I use:
>> >> >> >> ifconfig 7 add multicast ff04::1
>> >> >> >> ?
>> >> >> >>
>> >> >> >> I'm missing something here, could give me an explanation please:
>> >> >> >> Before, I had a transceiver plugged on my linux so I was able to
>> >> >> >> ping
>> >> >> >> my board directly using fe80::address so I was able to use the
>> >> >> >> local
>> >> >> >> multicast address ff02::1, now that I use border router, I'm
>> >> >> >> using a
>> >> >> >> prefix 2001::db8 (why? and why documentation prefix?) Why can't I
>> >> >> >> use
>> >> >> >> fe80 as before?
>> >> >> >
>> >> >> > because link-local ff80::/10 will not be routed, between lowpan
>> >> >> > and
>> >> >> > ethernet interface, so far I know.
>> >> >>
>> >> >> ff80? You meant fe80? I was able to do ping with fe80 and lowpan0.
>> >> >
>> >> > Sorry, I think I misunderstood here something completely.
>> >> >
>> >> > Your setup what is it?
>> >> >
>> >> > Linux (802.15.4/6LoWPAN) <-> RIOT
>> >> >
>> >> I used this and I was able to ping6 -I lowpan0 fe80:: but now I use
>> >> second
>> >> one
>> >>
>> >> > or
>> >> >
>> >> > Linux -> TAP (ethernet) <-> RIOT BORDER ROUTER <-> RIOT
>> >>
>> >> Now my setup is like this, yes and so what you explain make sense for
>> >> the RIOT border router, they do what you explain but with RIOT instead
>> >> of Linux :)
>> >>
>> >> My last question is how to send multicast information from Linux to my
>> >> local network? What Martine tell me to try did not work
>> >>
>> >> >
>> >> > You say something with lowpan0 then I think it's the first one, but I
>> >> > am
>> >> > not sure now and confused. :-)
>> >> >
>> >> > It's a important information, if it's the second one then better
>> >> > completely ignore what I said before, because I don't know how this
>> >> > works exactly.
>> >> >
>> >> > - Alex
>> >> > ___
>> >> > devel mailing list
>> >> > devel@riot-os.org
>> >> > https://lists.riot-os.org/mailman/listinfo/devel
>> >>
>> >>
>> >>
>> >> --
>> >> Baptiste
>> >> ___
>> >> devel mailing list
>> >> devel@riot-os.org
>> >> https://lists.riot-os.org/mailman/listinfo/devel
>> >
>> >
>> >
>> > ___
>> > devel mailing list
>> > devel@riot-os.org
>> > https://lists.riot-os.org/mailman/listinfo/devel
>> >
>>
>>
>>
>> --
>> Baptiste
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
--
Baptiste
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
