Re: [riot-devel] Raspberry Pi 3 and packet sniffing

2016-06-06 Thread Aaron Sowry 
Hi Sebastian,

Nice! Great instructions btw - I can verify that after compiling and
installing the more recent kernel for Raspbian I am successfully
sniffing packets again. Thanks a lot for your help.

Regards,
Aaron

2016-06-07 0:26 GMT+12:00 smlng :
> Hi Aaron,
> Hi Alex,
>
> first I can confirm that with latest default Raspbian and Kernel 4.4.* I saw 
> nothing with wireshark, though the interface was up and running, no error in 
> dmesg or anything.
>
> However, I just compiled a Kernel v4.7.y following my guide in [1], and it 
> works! I sniffed traffic between another RasPi (1 B+) and some RIOT nodes and 
> was also able to ping the other RasPi.
>
> @Aaron: Could you test/verify this using the newer Kernel, thanks!
>
> Best
>   Sebastian
>
> [1]: 
> https://github.com/RIOT-Makers/wpan-raspbian/wiki/Create-a-generic-Raspbian-image-with-6LoWPAN-support#4-new-linux-kernels-for-the-pi
>
>> Am 03.06.2016 um 12:01 schrieb Alexander Aring :
>>
>> Hi,
>>
>> On Fri, Jun 03, 2016 at 09:30:16PM +1200, Aaron Sowry wrote:
>>> Hi,
>>>
>>> Yeah I tried a few different speeds with no luck - according to the
>>> docs the default is now 3 MHz anyway. If I could at least get garbled
>>> packets *consistently* this would be a step in the right direction,
>>> but the fact that it's sporadic makes debugging things rather
>>> difficult...
>>>
>>
>> there was one guy @#linux-wpan channel which had similar issues on
>> RPi2 or RPi3? and he fixed it by using the mainline kernel _NOT_ rpi
>> kernel.
>>
>> I never used myself the rpi kernel for RPi2 so I can't say if this is
>> broken or not.
>>
>> Maybe you have the chance to build a recent mainline kernel from
>> kernel.org. I don't know the RPi3 support, fast googling result into
>> [0], which seems to be available at "git://git.kraxel.org/linux
>> bcm2837".
>>
>> - Alex
>>
>> [0] 
>> http://lists.infradead.org/pipermail/linux-rpi-kernel/2016-June/003916.html
>> ___
>> 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
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT Vs Iotivity, AllJoyn, Thread

2016-06-06 Thread Iván Briano 
Sorry, I was under the assumption that this had been settled in private
conversations already, but now I see that's not the case (and the person
involved is not even copied).

Soletta has an implementation of OIC, the protocol that IoTivity
implements, but there's nothing about AllJoyn or Thread.

I'm in no position to talk about anything now, so I have to decline the
invitation, but maybe some of the others listed that have been more
involved with Soletta and OIC can respond.

On Mon, 06 Jun 2016 22:40:34 +0200, Baptiste Clenet wrote:
> Could some of you answer please?
> Thanks
> 
> Baptiste
> 
> 2016-05-31 17:30 GMT+02:00 Thiago Macieira :
> 
> > Hello Baptiste, Emmanuel
> >
> > I'll let the people more familiar (in cc) with it reply.
> >
> > On terça-feira, 31 de maio de 2016 16:05:22 BRT Emmanuel Baccelli wrote:
> > > Hi Thiago,
> > > basically, we are interested in learning more about it.
> > > And in particular, we were wondering whether it could be a good idea to
> > > present this at the RIOT Summit [1].
> > > What do you think about this idea?
> > > Best,
> > > Emmanuel
> > >
> > >
> > > [1] summit.riot-os.org
> > >
> > > On Tue, May 31, 2016 at 3:52 PM, Baptiste Clenet 
> > >
> > > wrote:
> > > > Not really but I saw him answering some post on Iotivity and Soletta
> > > > project for people asking to port Iotivity to constraint object.
> > > >
> > > > Thiago, could you explain Soletta Project and the relation with OIC and
> > > > RIOT please?
> > > >
> > > > 2016-05-30 21:07 GMT+02:00 Emmanuel Baccelli <
> > emmanuel.bacce...@inria.fr>:
> > > >> Hi Baptiste,
> > > >>
> > > >> Thanks for the clarification.
> > > >>
> > > >> Have you already been in contact personally with Thiago?
> > > >>
> > > >> It may be interesting if they attend and/or present something on this
> > > >> topic at the upcoming RIOT Summit [1].
> > > >>
> > > >> Cheers,
> > > >>
> > > >> Emmanuel
> > > >>
> > > >> [1] summit.riot-os.org
> > > >>
> > > >> On May 30, 2016 4:19 PM, "Baptiste Clenet" 
> > wrote:
> > > >>> Hi, I correct what I said, Soletta Project is not an implementation
> > of
> > > >>> Iotivity but an implementation of OIC specification (Iotivity too) so
> > > >>> Iotivity and Soletta project can communicate together since they use
> > > >>> same
> > > >>> specification.
> > > >>>
> > > >>> Intel Open Source is in charge of this project and you can ask
> > > >>> thiago.macie...@intel.com for more information.
> > > >>>
> > > >>> Cheers,
> > > >>>
> > > >>> 2016-05-30 10:41 GMT+02:00 Oleg Hahm :
> > >  Hi!
> > > 
> > >  On Mon, May 30, 2016 at 09:16:17AM +0200, Baptiste Clenet wrote:
> > >  > - Iotivity would be great in RIOT, Soletta project [1] imported it
> > >  > for
> > >  > RIOT, I haven't tried it but it seems to work. I think Riot should
> > > 
> > >  have an
> > > 
> > >  > implementation of Iotivity directly in its repo (package) so it
> > will
> > > 
> > >  be
> > > 
> > >  > better maintain.
> > > 
> > >  Very interesting and good to know. I was not aware of this project
> > (and
> > >  I
> > >  think most of the RIOT maintainers weren't either). And yes, for
> > >  maintainability a package in RIOT might make sense. We just need a
> > >  maintainer
> > >  willing to do so. ;-)
> > > 
> > >  Baptiste, do you know the people behind Soletta?
> > > 
> > >  Cheers,
> > >  Oleg
> > > 
> > >  --
> > >  printk("Entering UltraSMPenguin Mode...\n");
> > > 
> > >  linux-2.2.16/arch/sparc64/kernel/smp.c
> > > 
> > >  ___
> > >  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
> >
> >
> > --
> > Thiago Macieira - thiago.macieira (AT) intel.com
> >   Software Architect - Intel Open Source Technology Center
> >
> > ___
> > 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

Re: [riot-devel] Regarding RNDIS support

2016-06-06 Thread Johann Fischer 

Hello Stefan,

Am 06.06.2016 um 14:39 schrieb Stefan Schmidt:

I am working on usb device support for RIOT. There is a PR[1] for it,
but it is outdated and will be rebased/updated with [2].

[2] supports kinetis and sam[r,d]-21. The CDC-ACM and CDC-ECM support
is very anstable and WIP. Currently I am working on the stability of
CDC-ACM.

I plan:
- remove CDC-ECM first
- add a netdev2-802154-over-usb interface and opposite driver for
linux kernel


Could you elaborate on this part? I'm not sure I understand what your
plan is here.

If your plan is to expose 15.4 level API over USB and write a matching
Linux Kernel driver that fits into linux-wpan at least Alexander and
myself would be interested in your plans. :)


That's exactly what I planned. For the beginning we can take the netdev2 
for it. If we (someday) have a proper MAC in RIOT, then it may be a 
better way to use it with linux hardmac interface and to build a 15.4 
dongle based on RIOT.


We currently have even the hardware for it [1] and a SAM-R21 Xplaned 
board can also be used as the dongle.


Unfortunately, I have some ugly bugs in CDC-ACM code and the code needs 
clean up, when it is fixed i will update [2].


[1] http://www.phytec.de/produkt/internet-of-things/phystick-kw2x/
[2] https://github.com/RIOT-OS/RIOT/pull/3890

Cheers,

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

Re: [riot-devel] Regarding RNDIS support

2016-06-06 Thread Stefan Schmidt 

Hello.

On 06/06/16 13:25, Johann Fischer wrote:

Hi,

Am 06.06.2016 um 11:55 schrieb shishir tiwari:

Hello,

As RIOT support Ethernet devices and USB device , Is someone working
on rndis(Remote Network Driver Interface Specification) Protocol.??


I am working on usb device support for RIOT. There is a PR[1] for it, 
but it is outdated and will be rebased/updated with [2].


[2] supports kinetis and sam[r,d]-21. The CDC-ACM and CDC-ECM support 
is very anstable and WIP. Currently I am working on the stability of 
CDC-ACM.


I plan:
- remove CDC-ECM first
- add a netdev2-802154-over-usb interface and opposite driver for 
linux kernel 


Could you elaborate on this part? I'm not sure I understand what your 
plan is here.


If your plan is to expose 15.4 level API over USB and write a matching 
Linux Kernel driver that fits into linux-wpan at least Alexander and 
myself would be interested in your plans. :)


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

Re: [riot-devel] Raspberry Pi 3 and packet sniffing

2016-06-06 Thread smlng 
Hi Aaron,
Hi Alex,

first I can confirm that with latest default Raspbian and Kernel 4.4.* I saw 
nothing with wireshark, though the interface was up and running, no error in 
dmesg or anything.

However, I just compiled a Kernel v4.7.y following my guide in [1], and it 
works! I sniffed traffic between another RasPi (1 B+) and some RIOT nodes and 
was also able to ping the other RasPi.

@Aaron: Could you test/verify this using the newer Kernel, thanks!

Best
  Sebastian

[1]: 
https://github.com/RIOT-Makers/wpan-raspbian/wiki/Create-a-generic-Raspbian-image-with-6LoWPAN-support#4-new-linux-kernels-for-the-pi

> Am 03.06.2016 um 12:01 schrieb Alexander Aring :
> 
> Hi,
> 
> On Fri, Jun 03, 2016 at 09:30:16PM +1200, Aaron Sowry wrote:
>> Hi,
>> 
>> Yeah I tried a few different speeds with no luck - according to the
>> docs the default is now 3 MHz anyway. If I could at least get garbled
>> packets *consistently* this would be a step in the right direction,
>> but the fact that it's sporadic makes debugging things rather
>> difficult...
>> 
> 
> there was one guy @#linux-wpan channel which had similar issues on
> RPi2 or RPi3? and he fixed it by using the mainline kernel _NOT_ rpi
> kernel.
> 
> I never used myself the rpi kernel for RPi2 so I can't say if this is
> broken or not.
> 
> Maybe you have the chance to build a recent mainline kernel from
> kernel.org. I don't know the RPi3 support, fast googling result into
> [0], which seems to be available at "git://git.kraxel.org/linux
> bcm2837".
> 
> - Alex
> 
> [0] 
> http://lists.infradead.org/pipermail/linux-rpi-kernel/2016-June/003916.html
> ___
> 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] Regarding RNDIS support

2016-06-06 Thread Johann Fischer 

Hi,

Am 06.06.2016 um 11:55 schrieb shishir tiwari:

Hello,

As RIOT support Ethernet devices and USB device , Is someone working
on rndis(Remote Network Driver Interface Specification)  Protocol.??


I am working on usb device support for RIOT. There is a PR[1] for it, 
but it is outdated and will be rebased/updated with [2].


[2] supports kinetis and sam[r,d]-21. The CDC-ACM and CDC-ECM support is 
very anstable and WIP. Currently I am working on the stability of CDC-ACM.


I plan:
- remove CDC-ECM first
- add a netdev2-802154-over-usb interface and opposite driver for linux 
kernel :-)


About RNDIS:
- why should RIOT supports a Microsoft proprietary protocol?
- why not CDC-ECM or CDC-EEM ?

Cheers,

[1] https://github.com/RIOT-OS/RIOT/pull/3890
[2] https://github.com/jfischer-phytec-iot/RIOT/tree/test%40cdc-ecm

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

[riot-devel] UDP datagram sending

2016-06-06 Thread Mateusz Kubaszek 

Hi :)

I am writing an UDP module for sending and receiving datagrams with 
ACKs. It is based on udp and pktdump example. I have a certain problem 
with datagram sending from my custom thread. Using shell module the 
datagrams are prepared as pktsnip and then sent by calling 
"gnrc_netapi_dispatch_send(GNRC_NETTYPE_UDP, GNRC_NETREG_DEMUX_CTX_ALL, 
ip);". The thread number is 2 which indicates the main thread. Up to 
this point everything seems to work fine. When I'm doing the same thing 
using my custom thread it doesn't work. Why is it so?


Best regards,
Mateusz Kubaszek
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Regarding RNDIS support

2016-06-06 Thread shishir tiwari 
Hello,

As RIOT support Ethernet devices and USB device , Is someone working
on rndis(Remote Network Driver Interface Specification)  Protocol.??

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