Re: [lwip-users] Implementing sys_arch on lwip 1.3.2

[Simon Goldschmidt]

Luca Ottaviano <address@hidden> wrote:
> Ah, maybe that's the misunderstanding; I'm initializing the interface
> using:
> netif_add(&netif, &ipaddr, &netmask, &gw, NULL, ethernetif_init, ip_input)
> 
> So my ethernet thread is calling ip_input() directly instead of
> tcpip_input().

Well, that's a bug in your port then. The (often repeated) principle of lwIP is 
that only one thread may be active in lwIP at a time. And if you are using 
NO_SYS==0 (so you are using the tcpip_thread), you *must* use tcpip_input to 
pass packets into the stack. Using ip_input does not work in that case (and 
BTW, you should have used ethernet_input to prevent coding the ARP processing 
yourself).

Unless I understood you wrong and you're not calling lwip_init() or 
tcpip_init() at startup or you're not using NO_SYS==0.

Simon
-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de