I am using lwIP 1.3.0 and it works great, but I've always wondered where
there's an approx. three second delay after the ARP response before lwIP
sends the SYN. In other words:
1. I initiate a TCP connection
2. lwIP sends an ARP request almost immediately
3. The host responds (relatively)
Hello,
I am starting a new project with a Freescale PowerPC MPC8641D which
embeds a Three-Speed Ethernet Controller.
Does someone have already made a port for this kind of MAC ? This MAC is
compatible with PowerQuiccIII MAC.
Regards,
Nicolas
___
On Tue, 2009-10-13 at 09:15 +0100, FreeRTOS Info wrote:
I've never been sure why it is done like that. I normally change it
to
store the MAC address or the ARP request origin as it comes in, then
you
can send the request out immediately.
I'm not sure what you mean. Can you give a bit
I tried filing a bug but failed. I registered, I installed the cert, but
nothing worked.
Anyway, here's how I fixed the problem in netconn_recv().
There's probably a better way but this one's been running for many hours
now.
The fix was to set a temp variable to ERR_TIMEOUT and assign it
conn-err
Occasionally, the payload in my TCP return packet sent from lwip is more
bytes than I'm expecting.
It looks like it may be concatenating two copies of the payload.
When it happens, it enters this section of tcp_enqueue():
/* If there is room in the last pbuf on the unsent queue,
chain the
That description sounds suspiciously like a known bug in 1.3.1, where TCP
segments are incorrectly attached to the unsent queue.
https://savannah.nongnu.org/bugs/?27504
There is a patch attached to the bug report, and Simon checked it into LWIP
a couple of days ago. If you can get CVS-head or
