[Ns-bugs] [Bug 424] TCP FIN notification callback needed
code@nsnam.ece.gatech.edu
code at nsnam.ece.gatech.edu
Sun Mar 29 22:41:02 PDT 2009
http://www.nsnam.org/bugzilla/show_bug.cgi?id=424
--- Comment #7 from Tom Henderson <tomh at tomh.org> 2009-03-30 01:41:02 EDT ---
(In reply to comment #1)
> http://code.nsnam.org/raj/ns-3-tcp/rev/83ccf9c5afa8
>
> Does this do the trick?
>
(In reply to comment #6)
> From the article Tom posted:
> What we can do however is issue a shutdown(), which will lead to a FIN packet
> being sent to program B. Program B in turn will close down its socket, and we
> can detect this from program A: a subsequent read() will return 0.
>
>
> This scenario (of detecting EOF when reading from the socket) is supported by
> the current TCP implementation; the packet you get in the RecvCallback will
> have Size=0 only when the read reaches EOF, which is when the read hits the
> data that had the FIN on it originally.
Raj, it seems you are saying that the originally reported bug (callback needed)
is invalid since the read of length zero suffices? What is the immediate plan
for this bug?
--
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.
More information about the Ns-bugs
mailing list