From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: [release] ipsysctl tutorial 1.0.1
Date: Thu, 24 Oct 2002 23:33:57 +0000 [thread overview]
Message-ID: <marc-lartc-103550246808300@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103539326825533@msgid-missing>
Oskar Andreasson wrote:
>However, I notice one _big_ if in the page you are referring to, which by
>the way is quite old (dated circa 1996).
>
I have a distinct feeling that many IP based protocols don't change a
lot within these types of timespans. Look at how long IPv6 is taking to
deploy.
>"4. TCP options such as RFC1323, SACK and T/TCP options cannot be used."
>
>Nowhere does the documents explain how these problems can be solved (I
>haven't read the whole document yet, so I may burst out prematurely... but
>I wanted to respond to your questions:)).
>
I would assume that those options use bits in the packet header that SYN
cookies also use and therefore make unpredictable. I'm not sure either
though. FWIW, I've run all my machines 2.2.x and up with SYN cookies
turned on with no (known) ill effects; PCs and servers alike.
--
Michael T. Babcock
C.T.O., FibreSpeed Ltd.
http://www.fibrespeed.net/~mbabcock
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-24 23:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 17:13 [LARTC] Re: [release] ipsysctl tutorial 1.0.1 bert hubert
2002-10-23 18:39 ` Oskar Andreasson
2002-10-23 18:59 ` Michael T. Babcock
2002-10-24 17:56 ` Oskar Andreasson
2002-10-24 23:33 ` Michael T. Babcock [this message]
2002-10-28 19:55 ` Don Cohen
2002-10-28 20:16 ` Michael T. Babcock
2002-10-28 20:26 ` bert hubert
2002-10-28 20:31 ` Michael T. Babcock
2002-10-28 21:27 ` Oskar Andreasson
2002-10-29 14:32 ` Michael T. Babcock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103550246808300@msgid-missing \
--to=mbabcock@fibrespeed.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.