Packet 79 looks like its payload is corrupted. If I'm right on this, have you thoroughly debugged your Ethernet driver? Every time I've fought errors in WireShark and wanted to think it was lwIP, it was caused by errors of one form or another in my Ethernet driver.
Bill >-----Original Message----- >From: lwip-users-bounces+bauerbach=arrayonline....@nongnu.org >[mailto:lwip-users-bounces+bauerbach=arrayonline....@nongnu.org] On >Behalf Of Bernhard 'Gustl' Bauer >Sent: Wednesday, January 27, 2010 8:27 AM >To: Mailing list for lwIP users >Subject: [lwip-users] pbuf chain and packet queue > >Hi, > >my pbufs are large enough to contain a complete packet, so pbuf chains >should not occur. While hunting an error I discovered a pbuf with these >settings: >pbuf->next !=NULL >pbuf->len = 568 >pbuf->tot_len = 4948 > >My TCP_MSS is 1460. So 4948 = 3 * TCP_MSS + 568 > >Is this a pbuf chain, or a packet queue? > >The description in pbuf.c indicates the first. But in the pcap file that >is attached I have identified them as no. 196, 75, 77, and 79. So it >must be a packet queue, mustn't ist? But then the description in pbuf.c >is wrong. > >Could someone please enlighten me. > >Gustl > > > > _______________________________________________ lwip-users mailing list lwip-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/lwip-users
