[riot-devel] Problem with UDP and SAMR21-XPRO

MATTIA ANTONINI mattia.antonini1 at studenti.unipr.it
Thu Jun 23 23:56:01 CEST 2016


Hi all!
I found the problem in the commit 0de34c9 [1]. Can anyone check this
commit? I've also tried  the commit before ( f7bd237) and everything works.

Cheers,

Mattia



[1]
https://github.com/RIOT-OS/RIOT/commit/0de34c91c618829a845feef753b3ea32683365ed

2016-06-22 15:14 GMT+02:00 Alexandre Abadie <alexandre.abadie at inria.fr>:

> Hi,
>
> > 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?
>
> Latest master. From what you say, the problem comes from the RIOT BR.
>
> Cheers,
>
> Alex
>
>
> >
> > Best,
> >   Sebastian
> >
> > > Am 21.06.2016 um 21:42 schrieb Alexandre Abadie
> > > <alexandre.abadie at 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 at riot-os.org
> > > https://lists.riot-os.org/mailman/listinfo/devel
> >
> > _______________________________________________
> > devel mailing list
> > devel at riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
> >
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20160623/1990063a/attachment.html>


More information about the devel mailing list