Re: [riot-devel] Updating micro-ecc

[Oleg Hahm]

Hi Mathias!

On Mon, Mar 07, 2016 at 11:14:14AM +, Tausig Mathias wrote:
> Currently, the package uses a patch which removes all the random number
> generation code from micro-ecc and substitutes it for invocation to the hwrng
> interface.
> Wouldn't it be more straight-forward, to just plug the hwrng intefrface into
> micro-ecc directly (via the uECC_set_rng function), instead of making big
> alterations?

This goes pretty much in the direction of
https://github.com/RIOT-OS/RIOT/issues/2407, right?

Cheers,
Oleg
-- 
printk("%s: TDR is ga-ga (status %04x)\n", ...);
linux-2.6.6/drivers/net/eexpress.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] wrong checksum

[malo]

Hello,

no need to blame the kernel here, as I wrote in prev post I have had wrong
csums on the outgoing packets as well.
Thanks for pointing me at unitests for inet_csums - they were failing all
on my platform/compiler.

the problem was in inet_csum_slice, where

 csum += (*buf << 8) + *(buf + 1);

turned to signed math.

change to

csum += (uint16_t)...

solves the problem.

btw: do you run inet_csums unitest for some 16bits platform? to find out if
is platform or compiler specific.

thanks for all the help
wbr
malo



On 8 March 2016 at 09:25, Alexander Aring  wrote:

> Hi,
>
> On Mon, Mar 07, 2016 at 09:08:01PM +0100, Martine Lenders wrote:
> > Hi Malo,
> > did you check if everything is coming out right out of 6LoWPAN IPHC
> > and/or fragmentation (check with a sniffer)? Sometimes older 6LoWPAN
> > implementations have wrong datagram sizes and do weird stuff in the
> > IPHC header (don't want to discredit your work though Alexander; up
> > until now it seemed fine ^^").
> >
>
> this wasn't me. The not working parts was copy from contiki from
> the old maintainers.
>
> btw: We don't have currently a stable strategy, that means we don't fix
> things into stable. It's just too difficult, because the most patches
> are "rework xy".
>
> So please use the lastest greatest kernel, the RPi has meanwhile a good
> mainline support, so you could use [0] which I recommend.
>
> - Alex
>
> [0]
> http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/
> ___
> 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] Another milestone

[Kaspar Schleiser]

Hey,

On 03/08/2016 03:59 PM, Oleg Hahm wrote:
> I've just noticed that the RIOT community reached another milestone: until
> today 100 different people have contributed to this great project [1].
> Pretty amazing!

Another one: Oleg just opened the 5000th pull request [1]!

Kaspar
[1] https://github.com/RIOT-OS/RIOT/pull/5000
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Bridge border router and 6LowPan interfaces

[Baptiste Clenet]

@Kaspar, @Daniel?
I think I'm close to make it work but I think I miss something about
bridge and network here.

2016-03-07 17:19 GMT+01:00 Baptiste Clenet :
> @kaspar, @Daniel I'm goint to try to sum up:
>
> Node A (border router on samr21):
> Iface 5: inet6 addr: fe80::585a:4b52:7476:b996
>> ifconfig 6 add affe::2(Is that necessary then?)
>> ncache add 6 affe::1
>> ifconfig 6 add dead::585a:4b52:7476:b996
>
> 2016-03-07 17:10:09,884 - INFO # > ifconfig
> 2016-03-07 17:10:09,889 - INFO # Iface  5   HWaddr: 39:96  Channel: 26
>  Page: 0  NID: 0x23
> 2016-03-07 17:10:09,894 - INFO #Long HWaddr: 
> 5a:5a:4b:52:74:76:b9:96
> 2016-03-07 17:10:09,903 - INFO #TX-Power: 0dBm  State:
> IDLE  max. Retrans.: 3  CSMA Retries: 4
> 2016-03-07 17:10:09,913 - INFO #AUTOACK  CSMA  MTU:1280
> HL:64  6LO  RTR  IPHC
> 2016-03-07 17:10:09,916 - INFO #Source address length: 8
> 2016-03-07 17:10:09,918 - INFO #Link type: wireless
> 2016-03-07 17:10:09,924 - INFO #inet6 addr: ff02::1/128
> scope: local [multicast]
> 2016-03-07 17:10:09,931 - INFO #inet6 addr:
> fe80::585a:4b52:7476:b996/64  scope: local
> 2016-03-07 17:10:09,936 - INFO #inet6 addr:
> ff02::1:ff76:b996/128  scope: local [multicast]
> 2016-03-07 17:10:09,938 - INFO # Iface  6
> 2016-03-07 17:10:09,939 - INFO #
> 2016-03-07 17:10:09,943 - INFO #MTU:1280  HL:64  RTR  RTR_ADV
> 2016-03-07 17:10:09,945 - INFO #Link type: wired
> 2016-03-07 17:10:09,951 - INFO #inet6 addr: ff02::1/128
> scope: local [multicast]
> 2016-03-07 17:10:09,956 - INFO #inet6 addr: ff02::2/128
> scope: local [multicast]
> 2016-03-07 17:10:09,962 - INFO #inet6 addr:
> dead::585a:4b52:7476:b996/64  scope: global
> 2016-03-07 17:10:09,969 - INFO #inet6 addr:
> ff02::1:ff00:2/128  scope: local [multicast]
> 2016-03-07 17:10:09,974 - INFO #inet6 addr:
> ff02::1:ff76:b996/128  scope: local [multicast]
> 2016-03-07 17:10:09,978 - INFO #inet6 addr: affe::2/64
> scope: global
>
>
>
> Node B (gnrc_networking on samr21):
> 2016-03-07 17:09:28,005 - INFO # > ifconfig
> 2016-03-07 17:09:28,010 - INFO # Iface  7   HWaddr: 52:be  Channel: 26
>  Page: 0  NID: 0x23
> 2016-03-07 17:09:28,014 - INFO #Long HWaddr: 
> 5a:5a:45:5f:0d:d7:52:be
> 2016-03-07 17:09:28,021 - INFO #TX-Power: 0dBm  State:
> IDLE  max. Retrans.: 3  CSMA Retries: 4
> 2016-03-07 17:09:28,029 - INFO #AUTOACK  CSMA  MTU:1280
> HL:64  6LO  RTR  IPHC
> 2016-03-07 17:09:28,031 - INFO #Source address length: 8
> 2016-03-07 17:09:28,032 - INFO #Link type: wireless
> 2016-03-07 17:09:28,037 - INFO #inet6 addr: ff02::1/128
> scope: local [multicast]
> 2016-03-07 17:09:28,043 - INFO #inet6 addr:
> fe80::585a:455f:dd7:52be/64  scope: local
> 2016-03-07 17:09:28,050 - INFO #inet6 addr:
> ff02::1:ffd7:52be/128  scope: local [multicast]
>
>
>
> Linux:
> /RIOT/dist/tools/tunslip$ sudo ./tunslip6 affe::1/64 -t tun0 -s /dev/ttyUSB0
> SLIP started on ``/dev/ttyUSB0''
> opened tun device ``/dev/tun0''
> ifconfig tun0 inet `hostname` up
> ifconfig tun0 add affe::1/64
> ifconfig tun0 add fe80::0:0:0:1/64
> ifconfig tun0
>
> tun0  Link encap:UNSPEC  HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>   inet adr:127.0.1.1  P-t-P:127.0.1.1  Masque:255.255.255.255
>   adr inet6: fe80::1/64 Scope:Lien
>   adr inet6: affe::1/64 Scope:Global
>   UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>   Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 lg file transmission:500
>   Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)
>
> Instead of adding a route, I want to try to ping beforehand:
> ping6 -I tun0 affe::2ACK
> ping6 -I tun0 affe::585a:455f:dd7:52be NACK
> ping6 -I tun0 dead::585a:455f:dd7:52be   NACK
> ping6 -I tun0 fe80::585a:455f:dd7:52beNACK
>
> Which one should be ok?
>
> 2016-03-07 11:48 GMT+01:00 Kaspar Schleiser :
>> Hey,
>>
>> On 03/07/2016 11:29 AM, Daniel Krebs wrote:
>>> I guess what you're trying to achieve is the common use case of the
>>> border router AFAIK.
>>
>> Yes. Guess we need more documentation / FAQ for this.
>>
>>> Did you try to setup an "affe::x"-style address on
>>> node B? I'm still not too familiar with IPv6 terms, but I think that
>>> those fe80:: addresses are in a local scope and therefore not forwarded
>>> by a router, while the "affe::x" addresses are global.
>>>
>>> Node B:
>>> # ifconfig 7 add affe::3
>>> # udp server start 
>> No, that won't work. 6lowpan expects addresses to be based on a node's
>> eui64.
>>
>> @babtiste, add address "dead::" to node A 6lowpan interface.
>>  must be 

Re: [riot-devel] GSOC inquiry.

[Emmanuel Baccelli]

Hi Om
RIOT is not participating in GSOC this year.
Best,
Emmanuel

On Tue, Mar 8, 2016 at 4:20 PM, Om Shivom Nagpal 
wrote:

> Hi, I am Om Shivom pursuing CSE from PEC University of Technology,
> Chandigarh and I have previously worked on C++ and Python. I am interested
> in contributing to RIOT through GSOC 2016. I need a little guidance on how
> to get started here.
>
> Regards.
>
> ___
> 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] GSOC inquiry.

[Om Shivom Nagpal]

Hi, I am Om Shivom pursuing CSE from PEC University of Technology,
Chandigarh and I have previously worked on C++ and Python. I am interested
in contributing to RIOT through GSOC 2016. I need a little guidance on how
to get started here.

Regards.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Another milestone

[Oleg Hahm]

Dear rebelling IOTlers,

I've just noticed that the RIOT community reached another milestone: until
today 100 different people have contributed to this great project [1].
Pretty amazing!

Cheers,
Oleg

P.S. And congrats for your 1000th commit, Hauke!

[1] https://github.com/RIOT-OS/RIOT/graphs/contributors
-- 
panic("Yeee, unsupported cache architecture.");
linux-2.6.6/arch/mips/mm/cache.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Notification: Biweekly virtual meeting @ Wed Mar 9, 2016 2pm - 3pm (RIOT Events)

[Google Calendar]

This is a notification for:

Title: Biweekly virtual meeting
Developer discussions that will only happen if a proposed agenda exists.  
Some instructions and a link to the agenda can be found in the RIOT wiki  
(https://github.com/RIOT-OS/RIOT/wiki/Meetings). Remote participation will  
be provided.

When: Wed Mar 9, 2016 2pm - 3pm Berlin
Calendar: RIOT Events
Who:
* Ludwig Ortmann - creator

Event details:  
https://www.google.com/calendar/event?action=VIEW=Z2tqN2ZyY3NmdnEzOWFkbDdmMXJkb2hrbzhfMjAxNjAzMDlUMTMwMDAwWiBrM3FsOHNldHY3bDQ4b2Zub2wwdGZ1dTZ0c0Bn


Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this email at the account peterschme...@gmail.com because  
you are subscribed for notifications on calendar RIOT Events.


To stop receiving these emails, please log in to  
https://www.google.com/calendar/ and change your notification settings for  
this calendar.


Forwarding this invitation could allow any recipient to modify your RSVP  
response. Learn more at  
https://support.google.com/calendar/answer/37135#forwarding
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] wrong checksum

[Alexander Aring]

Hi,

On Mon, Mar 07, 2016 at 09:08:01PM +0100, Martine Lenders wrote:
> Hi Malo,
> did you check if everything is coming out right out of 6LoWPAN IPHC
> and/or fragmentation (check with a sniffer)? Sometimes older 6LoWPAN
> implementations have wrong datagram sizes and do weird stuff in the
> IPHC header (don't want to discredit your work though Alexander; up
> until now it seemed fine ^^").
>

this wasn't me. The not working parts was copy from contiki from
the old maintainers.

btw: We don't have currently a stable strategy, that means we don't fix
things into stable. It's just too difficult, because the most patches
are "rework xy".

So please use the lastest greatest kernel, the RPi has meanwhile a good
mainline support, so you could use [0] which I recommend.

- Alex

[0] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel