From: Henrik Nordstrom <hno@marasystems.com>
To: don-nf@isis.cs3-inc.com (Don Cohen), netfilter-devel@lists.samba.org
Subject: Re: Syncookie firewall
Date: Thu, 6 Jun 2002 19:32:04 +0200 [thread overview]
Message-ID: <200206061932.04510.hno@marasystems.com> (raw)
In-Reply-To: <15615.36281.187120.257236@isis.cs3-inc.com>
Don Cohen wrote:
> Why do you think that's better than simply forwarding packets with
> sequence/ack# translation? Surely it's less efficient. And it raises
> questions about how much data to buffer between the two and how that
> can be controlled.
Because there is no good way to know the servers TCP options before you have
opened the TCP connection to the server, and you do not want to open the TCP
connection to the server before the client has acknowledged the connection...
Adjusting the sequence numbers is the simple part of the picture. Does not
worry me.. this is what the NAT engine is doing.
What worries me is
* Window scaling
* Timestamp
* ECN
and a number of other end-to-end TCP options that depend on correct
negotiation during SYN.
Sure, window scaling and ECN can be set by configuration if you know your
server, but there is no good way to deal with the timestamp option short of
forcibly filter it out entirely from the TCP stream.
Regards
Henrik
next prev parent reply other threads:[~2002-06-06 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020606020322.05BF64258@lists.samba.org>
2002-06-06 16:28 ` Syncookie firewall Don Cohen
2002-06-06 17:32 ` Henrik Nordstrom [this message]
2002-06-07 9:21 ` Michel Banguerski
2002-06-07 9:47 ` Michel Banguerski
2002-06-07 9:56 ` Henrik Nordstrom
[not found] <20020606192927.6B7684DCE@lists.samba.org>
2002-06-06 21:18 ` Don Cohen
2002-06-06 21:34 ` Henrik Nordstrom
2002-06-06 22:03 ` Mark Atwood
2002-06-06 22:36 ` Don Cohen
[not found] <20020603132204.7934546FF@lists.samba.org>
2002-06-05 19:30 ` Don Cohen
2002-06-05 19:38 ` Henrik Nordstrom
2002-06-02 18:47 Michel Banguerski
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=200206061932.04510.hno@marasystems.com \
--to=hno@marasystems.com \
--cc=don-nf@isis.cs3-inc.com \
--cc=netfilter-devel@lists.samba.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.