[Ns-bugs] [Bug 426] TCP: close does not send RST

[code@nsnam.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=426


Tom Henderson <tomh at tomh.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tomh at tomh.org




--- Comment #4 from Tom Henderson <tomh at tomh.org>  2009-03-18 01:12:58 EDT ---
(In reply to comment #3)
> Is this the behavior for both Shutdown AND Close?
> 

It seems to me that this is related to bug 424 (need for a FIN-received
callback).

To summarize, if close() is called on a socket that has unread data, TCP should
send a RST.  If close() is called on a socket that has no unread data, TCP can
send a FIN, but if it subsequently receives any more data (that is not a bare
FIN) it should also send a RST.

A clean way to close an ns-3 socket that was used to send data is to call
ShutdownSend(), and then wait for the NotifyClose() callback to be invoked, at
which point the application can call Close().

This is worth a read:
http://blog.netherlabs.nl/articles/2009/01/18/the-ultimate-so_linger-page-or-why-is-my-tcp-not-reliable


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.