|From:||Muhamad Ikhwan Ismail|
|Subject:||RE: [lwip-users] Strange ghost segments|
|Date:||Mon, 14 Jul 2008 09:43:28 +0000|
When u say ghost data, did Wireshark tag those packets as Ethernet -II or Ethernet Type II packets or something like that ?
I used to have the problem at start 1.3.0 and it was because in 1.2.0 the TCP data are mostly single chain element packets, and UDP
are normally a chain of 2 (the header and the payload) and my driver did exactly that.
In 1.3.0 as I discovered the TCP data can be chains of multiple pbufs now, so most probably your driver sent
a single chained packets, and the rest are seen as garbage (the ones in the next chains).
Try fixing the driver as mine was definitely a problem with the driver.
> Subject: Re: [lwip-users] Strange ghost segments
> From: address@hidden
> To: address@hidden
> Date: Mon, 14 Jul 2008 09:17:57 +0100
> On Mon, 2008-07-14 at 09:53 +0200, address@hidden wrote:
> > Hello,
> > I'm currently using lwip 1.2.0, which does work (well, I do have a
> > problem,
> > but I'll open another thread for that). Now I tried upgrading to
> > 1.3.0
> > (for auto-IP support). Basically, it works, but when sending TCP data,
> > sometimes a bunch of garbage data is inserted. When I look at it with
> > Wireshark, I see an additional TCP segment that contains 125 bytes of
> > garbage data. Afterwards, the stream continues normally. When running
> > the
> > same test app several times, this sometimes happens and sometimes
> > doesn't.
> > I'm using the socket interface. This only happens with 1.3.0. I don't
> > really know how to go on to find out where this comes from. Maybe
> > someone
> > could give me a hint?
> Can you give more details about which port of lwIP you're using and what
> lwip-users mailing list
Need to know now? Get instant answers with Windows Live Messenger. IM on your terms.
|[Prev in Thread]||Current Thread||[Next in Thread]|