http://lwip.wikia.com/wiki/Writing_a_device_driver
You have to peek in your driver when it calls netif->input
(function pointer passed on netif add)
Wether you call ethernet_input or ip_input depends on your driver: the
flags it sets, it removes link layer info or not. Common behavior for
Yes the devices are inside our company network and there is a lot of
other traffic, but i did check with wireshark and there is really no
response to the pings.
I will try it with the example directly, thats a good idea, thanks.
If i try to debug in ip_input i see that the packages that timeout
I bet your driver is missing frames by letting them sleeping inside the
chip as many do, but you have a lot of unknown variables.
Is there any other traffic in your network ?
Is the TCP app running while you ping your hardware ?
Did you try the same with a known good application like the
