Hi all, though I do not have the same setup ready for testing, I _cannot_ confirm any problems with UDP on latest RIOT master branch.
I just tested UDP on a SAMR21-XPRO running gnrc_networking example and successfully send and received UDP data from and to a RasPi with Openlabs transceiver running netcat on latest Raspbian-Linux. Could you clarify which RIOT branch/commit you use? Best, Sebastian > Am 21.06.2016 um 21:42 schrieb Alexandre Abadie <alexandre.aba...@inria.fr>: > > Hi Mattia, > > Thanks for reporting this issue. > >> I've discovered a possible bug in RIOT. I'm working with 2 samr21-xpro: on >> the first is running gnrc_border_router (I'll call it A) and on the other >> (I'll call it B) is running gnrc_networking. I've well configured my >> scenario infact I can ping both my nodes from linux shell. But, when I send >> a UDP packet to B (with nc) it is forwarded correctly on tap interface (I >> seen it on wireshark) but it arrives corrupted (wrong checksum) to B and it >> is dropped by UDP thread. I've enabled packet dump and the packet arrives >> with different packet lengths in ipv6 and udp headers (fixed to 8, it is >> the UDP header length) and the udp payload is removed. > > I have the exact same problem although I didn't track it as deep as you did. > >> How can I fix this problem? > > A regression was introduced 2 or 3 weeks ago in master and you could first > "git bisect" to try to identify the incriminated commit. > > Thanks, > > Alex > _______________________________________________ > 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
