From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Natted packets
Date: Fri, 12 Jan 2007 23:38:09 -0600 [thread overview]
Message-ID: <45A87041.4070500@riverviewtech.net> (raw)
In-Reply-To: <45A38372.7090609@eternet.cc>
On 01/09/07 05:58, Lucas Diaz wrote:
> My question is if some other router somewhere else on the net (inside my
> lan) has NATed the traffic?
> And the original NATed IP?
> This router NATing traffic and my router are in the same network...
Ok, you are wanting to see if there is an additional NATing router
somewhere in your LAN?
(I'll presume yes for the rest of this post)
There are some ways that you can attempt to find IP addresses with
specific types of behavior (all beyond me) that can be indicative of
NATed IPs. I believe that (some of) these tests are based on the TCP
sequence number. More specifically, an IP stack *usually* behaves in a
predictable way. Thus you can look at the TCP sequence numbers of
packets coming from an IP address to see patterns of ranges / sliding
windows of TCP sequence numbers. If there are multiple (fuzzy)
definable groups, there is a good chance that each group is a given
computer. However, this can possibly be hidden by the NATing device.
Much beyond that and I don't know any more. However, I do know that
there is a lot of discussion about this on the reverse side on the net.
Namely I have stumbled across a lot of discussion where people were
trying to use NATing technology on providers that did not want them to,
i.e. they charged per device, and what they did to hide them selves from
the provider.
Grant. . . .
next prev parent reply other threads:[~2007-01-13 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 21:43 Natted packets Lucas Diaz
2007-01-08 22:00 ` Jan Engelhardt
2007-01-09 10:13 ` Pablo Neira Ayuso
2007-01-09 3:06 ` Grant Taylor
2007-01-09 11:58 ` Lucas Diaz
2007-01-13 5:38 ` Grant Taylor [this message]
2007-01-15 5:38 ` Grant Taylor
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=45A87041.4070500@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@lists.netfilter.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.