Miku Jha wrote:
[ ... ]
The situation is that if the client crashes, the server eventually sends a
RST (10.39.53) Following this RST, the client comes back in lets say around
2-3 minutes. Now when the client sends a SYN(10.42.23), there is no
timestamp option.
If the client opens a connection
--- Chuck Swiger <[EMAIL PROTECTED]> wrote:
> jha miku wrote:
> > 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.
>
> FreeBSD (and OS X, and other things using
jha miku wrote:
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.
FreeBSD (and OS X, and other things using a BSD network stack) will generate
initial TCP SYN packets contain
> 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 PROTEC
