|From:||Muhamad Ikhwan Ismail|
|Subject:||RE: [lwip-users] strange tcp connection issue|
|Date:||Mon, 14 Jul 2008 09:47:02 +0000|
I have seen it myself, but the problem itself is very hard to cause. I had to connect and reconnect every 1 ms,
and sometimes the port is closed and every attempt at connecting is answered with a RST. I checked and the
listening socket is not there anymore. In my code itself no deleting of the listening socket is executed so it makes me wonder.
Though as I said, the problem is very hard to trigger. I only managed to trigger it once on the debugger. And I dont think its
a problem with the stack and rather perhaps with my application coding. I ll keep on debugging and inform u what I see
Subject: RE: [lwip-users] strange tcp connection issue
Date: Sat, 12 Jul 2008 10:23:28 +0000
On my implementation i have an telnet-like server for runtime system information exchanged.
A friend of mine had tested it and told me of the same thing though i havent seen it myself. I was planing on
doing some test next week. Apparently if he keep on logging in to the server frequently (per mouse click)
at some point the server stops listening and wont accept connections. The stack itself is still ok as other
program is running ok and the stack can be pinged.
Like I said i am gonna take a look at it on monday and i might have something to post. My implementation is the
> Date: Fri, 11 Jul 2008 12:32:32 -0700
> From: address@hidden
> To: address@hidden
> Subject: [lwip-users] strange tcp connection issue
> On my platform I have an ftp server listening on port 21. During
> automated testing, where the ftp is accepting and closing connections
> frequently, the target will sometimes stop listening on port 21 for no
> apparent reason. All other apps listening on other ports still
> function correctly. I've debugged it down to where I find a
> discrepancy between the socket layer and the stack:
> I have a real time display which shows the state of all sockets
> current active in the system. At the time of the problem, this
> correctly shows a TCP socket listening on port 21. To get this data,
> I dereference the socket->conn->pcb.tcp->state variable in the user
> application context. I also added some code to tcp_input to print out
> the tcp_listen_pcb list if no matching PCB was found for the incoming
> segment (down by where it calls tcp_rst). What I found was
> interesting. I see something like the following:
> listening on port: 1030
> listening on port: 1027
> listening on port: 0 <-- this one WAS 21, but now isn't.
> Any ideas on what might cause such a discrepancy? This is a late 1.2 cvs head.
> Thomas Taranowski
> Certified netburner consultant
> lwip-users mailing list
Its a talkathon but its not just talk. Check out the im Talkathon.
The im Talkaton. Can 30-days of conversation change the world? Find out now.
|[Prev in Thread]||Current Thread||[Next in Thread]|