2009/6/29 Kieran Mansley <address@hidden>
It is not your problem for sure, as lwIP receives the UDP packet, thinks
the checksum is correct, and sends a response. The response gets lots
somewhere in etharp_output() before making it onto the network though.
I notice that in the udp_echo.trace.txt there is the following:
This is odd for two reasons: (i) it should already have an entry for the
<LF>find_entry: selecting empty entry 1
<LF>etharp_request: sending ARP request.etharp_raw: sending raw ARP
packet.etharp_query: queued packet 215bf0 on ARP entry 1
PC's MAC address as it's updated that entry lots already from the other
ARP requests seen on the network earlier; and (ii) the packet it sends
is not an ARP request for the PC's MAC, but a gratuitous ARP of its own
MAC. I think there is definitely something going wrong here.