Re: [lwip-users] LWIP stops responding on Ping and HTTP calls from a browser

[Kieran Mansley]

On Wed, 2011-04-27 at 13:36 +0200, Ruben wrote:
> It is strange but UDP frames are not blocking and keep on beeing
> processed by the stack but TCP not.
> in the function ip_input at "switch (IPH_PROTO(iphdr)) " the UDP case
> it called but the TCP case us never called untill I wait a while and
> refresh my broser. and if i am lucky the tcp frame is decoded and the
> browser display a webpage.

In that case I would use the LWIP_STATS code to find out if there is
some TCP-specific resource that is being exhausted.

Kieran