Re: [riot-devel] UDP travic between RIOT device and Raspberry PI 6LoWPAN seems not to work
Hi, On Sun, Mar 13, 2016 at 08:36:21AM +0100, Martine Lenders wrote: > Hi, > > Bernhard Nägelewrites: > > thank you for that hint. Is it sufficient to enable that modul in the > > Makefile.dep file in the main-folder, or should I add this to the Makefile > > in my example//Makefiles? Are there any changes needed elsewhere? > > it is pretty insignificant where you enable it. You can even set > USEMODULE=gnrc_sixlowpan_iphc_nhc as a local environment variable to > make with the same effect (which IMHO is the cleanest approach since > it does not change any files, so in case you forget about that it > isn't hurting you afterwards ;-)): > btw: I want to change the default handling here inside the Linux kernel. Compression for nhc at transmit side is turned off and can be turned on by a debugfs UAPI which doesn't exist right now. Same handling like the "compression flag" for rfc6775 stateful compression, just adapted for nhc. Receive handling is default on for nhc de-compression. This is a small open task inside the linux-kernel, everybody is welcome to send-patches, see [0]. I currently have other priorities e.g. short address handling. - Alex [0] http://wpan.cakelab.org/#_developing ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] UDP travic between RIOT device and Raspberry PI 6LoWPAN seems not to work
Dear malo, thanks a lot for your used modules. No, I haven't got a sniffer up to now. I think this is the next step for me - set up a sniffer to find faults in the radio transmission. At the moment I'm lucky because UDP transfer works at the moment. It was just a quick check and real testing is the next step but getting it running was a big success this weekend. By the way: I have also a Beaglebone-Green running with a 4.1.14 mainline kernel and a Microchip MRF24J40MA radio device and it works as well. Wonderful! Thank you very much! Best regards, Bernhard ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] UDP travic between RIOT device and Raspberry PI 6LoWPAN seems not to work
Hello Martine, thank you for the hint about the missing header compression. I have added the module and now UDP data traffic works between a UDP-server application on Raspberry PI and a UDP client application on the RIOT side. Thank you very much! Best regards, Bernhard P.S.: Sorry about the misspelling of traffic in the mail header - really terrible ;-) ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] UDP travic between RIOT device and Raspberry PI 6LoWPAN seems not to work
Hi, Bernhard Nägelewrites: > thank you for that hint. Is it sufficient to enable that modul in the > Makefile.dep file in the main-folder, or should I add this to the Makefile > in my example//Makefiles? Are there any changes needed elsewhere? it is pretty insignificant where you enable it. You can even set USEMODULE=gnrc_sixlowpan_iphc_nhc as a local environment variable to make with the same effect (which IMHO is the cleanest approach since it does not change any files, so in case you forget about that it isn't hurting you afterwards ;-)): > USEMODULE=gnrc_sixlowpan_iphc_nhc make clean flash term Important is that you clean before you build, because gnrc_sixlowpan_iphc_nhc is a pseudo-module that takes different #ifdef paths without changing a file. To my knowledge no further changes are needed to communicate with other 6LoWPAN implementations. Cheers, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] UDP travic between RIOT device and Raspberry PI 6LoWPAN seems not to work
Hello Martine, thank you for that hint. Is it sufficient to enable that modul in the Makefile.dep file in the main-folder, or should I add this to the Makefile in my example//Makefiles? Are there any changes needed elsewhere? Thanks a lot, Bernhard ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] UDP travic between RIOT device and Raspberry PI 6LoWPAN seems not to work
Hi, 2016-03-12 21:58 GMT+01:00 Martine Lenders: > […] by adding the module `gnrc_sixlowpan_nhc_iphc` to your USEMODULE list. Typo: the module's name is `gnrc_sixlowpan_iphc_nhc`. Cheers, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] UDP travic between RIOT device and Raspberry PI 6LoWPAN seems not to work
Hi, Linux uses next header compression (NHC) for UDP communication. Sadly, our implementation of NHC has still some issues when forwarding packets [1, 2, 3], which are about to be fixed in the next few days or so. This is why we currently have it deactivated by default. For now, if you don't use a RIOT node as multihop router (your scenario does not sound like it) you can activate NHC manually by adding the module `gnrc_sixlowpan_nhc_iphc` to your USEMODULE list. Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/pull/4544 [2] https://github.com/RIOT-OS/RIOT/pull/5029 [3] https://github.com/RIOT-OS/RIOT/pull/5044 2016-03-12 21:51 GMT+01:00 Bernhard Nägele: > Hello everyone, > this week I made some success with exploring RIOT OS. > But now I stuck with trying to get a data transfer between a 6LoWPAN equiped > Raspberry Pi and "RIOT-MCUs". > > All my tests are based on the gnrc_networking example. > > First I made a UDP transfer between 2 identical RIOT equiped MCU boards. On > the first device I started > a UDP server and from the other I generated some data trafic to the other. > Result: full success - I have seen > the traffic on the shell (pktdump) and it was O.K. > > Then I set up a Raspberry for usage with 6LoWPAN as described on the RIOT > web page. > ping6 works wonderful in each direction but when I tried to get data trafic > through UDP I got > nothing - neither in one direction nor in the other. > I tried also to listen to the UDP port with netcat6 - also no success. > > Can anyone give me a hint what's different between a UDP transfer between 2 > RIOT devices and a trafic > between a Linux-based UDP server and a RIOT-based device? The > "basic"-Interface seems O.K. because > of the working ping6. > > Thanks a lot! > Best regards, > Bernhard > ___ > 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