OK, it seems to be a chain. Since I only checked the tot_len field and used this for copying the data I of course got some crap because I tried to pull all data out of the first pbuf payload. Thanks for the hint!
On Fri, Jan 3, 2014 at 10:57 PM, Bill Auerbach <[email protected]> wrote: > Hi, > > Could be a packet chain (pbuf chain) of 8 packets. The "some crap" part is > not good and probably means the driver needs some scrutiny for times when > it's being pushed. > > Bill > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf > Of Satz Klauer > Sent: Friday, January 03, 2014 3:44 PM > To: Mailing list for lwIP users > Subject: [lwip-users] Strange packet sizes in receive-callback > > Hi, > > I'm new to lwIP, so hopefully my question is not too stupid. > > I'm sending huge amounts of data to my BeagleBone Black where a lwIP > implementation is running. Due to that within my receive callback I get > repeatedly packets with a size of 1460 bytes (which should be some TCP > segment/framesize?). > > This works mainly well...but sometimes a packet with a bigger size is > received (e.g. 11680 bytes). This is bigger than the maximum possible size > and the memory contains some crap. > > Any idea what the reason could be for this behaviour? > > Thanks! > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users > > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
