RE: [lwip-users] netconn api problem

[Bill Auerbach]

You could add a UDP broadcast after the big write and use that in WireShark
to find the smaller packet that follows.  Wouldn't you hate to go down this
path for a long time to find out byte ends up being in the WireShark
capture?  Sure, I agree, it's 99.9% sure not going to be there.  But the
Wireshark capture might show other problems in and around that area.  And
are there errors in the capture or is it clean?

Can you shrink iteratively the size of the first large send until the 2nd
send works?  This might point to some size or boundary condition when the
problem appears.

Bill

>-----Original Message-----
>> I'm connecting to lwIP from a Windows PC via a socket in python. I
>have a hard time believing the PC is dropping the byte. I know I could
>verify this with Wireshark, but since the problem is random and not too
>frequent, it would take me forever to wade through the lengthy packet
>history.
>>
>> Anybody have any insight and/or guidance on where I might go in the
>code or what settings I might tweak to fix and/or understand this issue?
>>
>> Other lwipopts.h settings that might be relevant:
>>
>> MEM_LIBC_MALLOC = 1
>> TCP_OVERSIZE = 1
>> LWIP_TCPIP_CORE_LOCKING = 1
>> LWIP_TCPIP_CORE_LOCKING_INPUT = 1
>
>
>Thanks,
>Tyrel
>_______________________________________________
>lwip-users mailing list
>address@hidden
>http://lists.nongnu.org/mailman/listinfo/lwip-users