SV: [lwip-users] Followup - Difficulty ending a connection over lwipraw-api

[Jan Wester]

Hello Larry
First, in listener mode you work with one pcb for listener (master) and
another pcb for each connection (slave).
You shall do close on slave pcb, the master pcb you have to set up only
once.
Second, the close start the close sequence and put the pcb in timewait
state, and it is deallocated after the timeout.
/Jan


WHI KONSULT
Jan Wester
Scheelegatan 11
SE-112 28 Stockholm
+46 8 449 05 30


-----Ursprungligt meddelande-----
Från: address@hidden
[mailto:address@hidden För Larry Rachman
[Innovation Design and Solutions,Inc.]
Skickat: den 8 augusti 2005 23:14
Till: address@hidden
Ämne: [lwip-users] Followup - Difficulty ending a connection over
lwipraw-api

Well, after some more experimentation, it appears (to me) that calling
tcp_close() does *NOT* in fact deallocate the pcb, in contrast to what the
documentation says. I can call tcp_close(), my connection drops, and on the
next inbound connection attempt I receive an accept callback and a new
connection is established.

This is great news for getting my application to work. But it raises two
questions:

1 - Can someone confirm that the behavior I'm seeing is correct, and...

2 - When I *want* to deallocate a pcb, how do I do it? I don't see a
"tcp_remove()" function, similar to the "udp_remove()" one that *is* in the
documentation. I have no immediate need to do this, but I'll eventually need
to when I add port agility.

Thanks,
-lr



_____________________________________
Larry Rachman
Innovation Design and Solutions, Inc.
1044 Washington Drive
Centerport, NY 11721
631-427-1112 (NY)
508-967-2511 (MA)
631-427-0656 (fax)
www.4innovation.biz
_____________________________________



_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users