Attached. I could be wrong, but it looks like a WireShark bug (0.99.6a). The 1-byte "bad" packet has a payload of 0x11 which you see in the packet data. The 2-byte correct packet has 0x2222. Also, I wasn't nice and sent a payload with 0 size and lwIP tried to send the packet. Are 0 size payloads for UDP and TCP allowed?
I think it's a resolved bug. It seems right for Wireshark Version 1.0.6 (SVN Rev 27387).
-- Clément David
begin:vcard fn;quoted-printable:Cl=C3=A9ment David n;quoted-printable:David;Cl=C3=A9ment email;internet:[email protected] tel;cell:+33626265190 x-mozilla-html:FALSE version:2.1 end:vcard
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
