From: Lamont Granquist <lamont@scriptkiddie.org>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Stephen Clark <sclark46@earthlink.net>, <linux-kernel@vger.kernel.org>
Subject: Re: NAT counting
Date: Sun, 9 Feb 2003 11:01:51 -0800 (PST) [thread overview]
Message-ID: <20030209105503.M4561-100000@coredump.scriptkiddie.org> (raw)
In-Reply-To: <20030206231044.GA8704@hh.idb.hist.no>
On Fri, 7 Feb 2003, Helge Hafting wrote:
> On Thu, Feb 06, 2003 at 09:46:44AM -0500, Stephen Clark wrote:
> > Hi all,
> >
> > Is Linux being fixed to prevent this?
> >
> >
> > "how to remotely count the number of machines hiding behind a NAT box"
> > <http://www.research.att.com/%7Esmb/papers/fnat.pdf> /
> >
> Not a problem. The purpose of NAT isn't to "hide" stuff, but
> to share an ipv4 address. If you need more than that, let a
> firewall mangle your packets in interesting ways.
> You can probably do that with linux if you really want to...
NAT should work correctly though. It'd be nice if it didn't violate RFC
1323 by having non-monotonically increasing TCP timestamps for machines
that it is NAT'ing. The RFC 1323 violations are proably just as useful as
the IPid field for this "NAT counting" *and* they can break things in
certain situations (e.g. receiving a SYN to a TIME_WAIT socket with a
smaller TCP timestamp). I wouldn't mind at all if someone tried to fix
iptables so that it would do all the proper header munging to hide the
fact that there were multiple machines behind it (obviously this would be
slower, so it'd need to be an option that wasn't on by default...)
prev parent reply other threads:[~2003-02-09 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 14:46 Stephen Clark
2003-02-06 18:14 ` Lamont Granquist
2003-02-06 22:25 ` Alan Cox
2003-02-06 23:10 ` Helge Hafting
2003-02-09 19:01 ` Lamont Granquist [this message]
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=20030209105503.M4561-100000@coredump.scriptkiddie.org \
--to=lamont@scriptkiddie.org \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®