[Ns-bugs] [Bug 170] Tcpsocket::connect(127.0.0.1) return 0 if no server exists
bugzilla-daemon at nsnam-www.ece.gatech.edu
Thu May 8 11:55:30 PDT 2008
------- Comment #3 from craigdo at ee.washington.edu 2008-05-08 14:55 -------
> Are you saying that, in the real world, connect will synchronously wait
> for the syn ack ?
I'm responding to the bug report by saying that ns-3 just calls down into TCP
to send a SYN and returns in TcpSocket::Connect(). Really I'm mostly saying
that there is no "real world" example of an ns3::TcpSocket::Connect() to refer
But to answer your question, if this were BSD sockets, yes, I would expect a
connect() request on a TCP socket to block until some kind of positive or
negative response came back from the network or the server in question. If the
response was a SYN ACK from the server it would ACK the SYN ACK and then put
the socket into established and wake the connect() returning to the client.
This is how I remember it working back in the year 1725 anyway :-)
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the Ns-bugs