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] Unifying the interfaces of the digest functions
On Wed, May 11, 2016 at 12:26 PM, Oleg Hahmwrote: > 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
[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