[lwip-users] LWIP capabilities

[Robert Morse]

Hi,
	I am trying to use the lwip stack and while most things are working I 
am having some
problems.

        I have a lot of connections that are needed.

	I have 1 thread that listens on a TCP port, then passes the connected 
socket
off to 1 of 3 threads (These are static threads not created on the 
fly).  They deal with
the transfer of data, the close the socket, then wait for a new one to 
be passed to it.
These connections can be short <open><command><response><close> or they 
can be chained
commands where you have 
<open><command><response>..........<command><response><close> where
the connection might be open for a long period of time, the chained 
command has a 300MS
timeout then the socket will be closed.

	I have 1 thread that listens on a UDP port, that accepts requests from 
clients, and a
second thread sends status information out, to clients that have 
subscribed.
This uses recvfrom, and sendto.

	At a later date, another 3 or 4 threads doing TCP/UDP will also need 
to be added.

	It seems like everything is ok, as long as I only have one TCP 
connection running, I
can sometimes get away with a second TCP connection, but other times 
everything locks up.
I am currently not sure where the lock up is, as I don't have an 
in-circuit debugger to
figure out where it is stopping.

	My driver, in the receive interrupt, just messages a HIGH priority 
task, to actually
handle passing the data into the lwip stack.

So, my question is do you think I am pushing the lwip stack to far?

Robert