Hey Mark, Simon,
well it does work when introducing the source address in the routing algorithm
and thats what I did for now.
But obviously, Simon is right: routing doesn't have anything to do with the
source address and it shouldn't have to.
The underlying problem in LwIP at the moment is
Read the wiki, and if it is not clear enough, I will change it
http://lwip.wikia.com/wiki/Raw/TCP
So far, the last user that asked (almost) exactly the same as you did
not complain, so it should be OK.
___
lwip-users mailing list
lwip-users@nongnu.org
You have a working http server in the contrib tree.
You also have my http server, which expands a bit over the official one:
http://scaprile.ldir.com.ar/cms/category/os/lwhttpd/
If that is not enough and you really need to do your own, you have
working examples on how to develop TCP applications
Sergio,
I have been to the site many times and find it very helpful. My problem is that
I can send data from my project to our server with no problem the first time
but after closing the first connection and opening another with a different
port the server will not respond to the request. At
Sergio,
I have been to the site many times and find it very helpful. My problem is that
I can send data from my project to our server with no problem the first time
but after closing the first connection and opening another with a different
port the server will not respond to the request. At
My guess would be that you have manual listen backlog enabled but don't tell
the stack to decrement the listen backlog after accepting a connection...
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
Simon,
Thanks. I do have a listen open as well. I used
tcp_listen_with_backlog(pcb,1) with my #define TCP_LISTEN_BACKLOG 1. I guess
I don't understand the backlog function. Should the backlog be larger than 1?
Thanks again,
Paul
From:
