> Are there other situations when timestamp gets disabled? In case of active open and net.inet.tcp.rfc1323 is set to non-zero, one possibility is TCP_NOOPT is turned on by setsockopt(). But I do not know which applications use TCP_NOOPT.
Regards, Noritoshi Demizu > From: jha miku <[EMAIL PROTECTED]> > To: freebsd-net@freebsd.org > Subject: Question regd timestamp option > Date: Thu, 11 Aug 2005 19:08:13 -0700 (PDT) > > In case of active open, the SYN segments always have > timestamp enabled, since the RFC flg is set. But, > Currently, I am seeing some SYN segments without > timestamp option. > > The only condition that I am aware of when timestamp is > disabled, is on sending the 3rd SYN in retransmit code > when the timestamp gets disabled. > looking at the tcpdump, it is unclear why the SYNs are > sent during active open without timestamp option. > > Are there other situations when timestamp gets > disabled? > Please let me know. > Thanks. > > ____________________________________________________ > Start your day with Yahoo! - make it your home page > http://www.yahoo.com/r/hs > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "[EMAIL PROTECTED]" _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
