From: Emmanuel Guiton <emmanuel@netlab.hut.fi>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: NAPT with several IP addresses?
Date: Fri, 21 Nov 2003 14:33:01 +0200 [thread overview]
Message-ID: <3FBE05FD.2050704@netlab.hut.fi> (raw)
In-Reply-To: 20031121104404.GI29432@sunbeam.de.gnumonks.org
Sorry, my mistake, you can forget about my comment.
I'm not yet familiar with the whole code and I misunderstood the meaning
of IP_NAT_RANGE_PROTO_SPECIFIED.
Thanks,
Emmanuel
Harald Welte wrote:
>On Fri, Nov 21, 2003 at 11:36:34AM +0200, Emmanuel Guiton wrote:
>
>
>>Hei!
>>
>>I was looking at the Linux Netfilter Hacking HOWTO and at the source
>>code in ip_nat_proto_tcp.c and I realized that doing NAPT with several
>>ports is not supported, am I right?
>>
>>
>
>of course it is supported.
>
>
>
>>I mean, in the HOWTO it's written "If IP_NAT_RANGE_PROTO_SPECIFIED isn't
>>set, it means that the user is doing NAT, not NAPT". Well, we could also
>>use a range of IP addresses and still perform NAPT, couldn't we? Still
>>this possibility is not implemented, isn't it?
>>
>>
>
>I don't really understand what your point. IP_NAT_RANGE_PROTO_SPECIFIED
>just tells us if the give nat range has only a layer 3 (ip) range, or
>also layer 4 (tcp/udp/...) range. It doesn't tell you at all if you nat
>to a single address or to multiple addresses.
>
>A nat mapping is internally always represented as a nat range. Even if
>the range has only the size of one (i.e. a single ip address or port).
>
>
>
>> Emmanuel
>>
>>
>
>
>
prev parent reply other threads:[~2003-11-21 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 9:36 NAPT with several IP addresses? Emmanuel Guiton
2003-11-21 10:44 ` Harald Welte
2003-11-21 12:33 ` Emmanuel Guiton [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=3FBE05FD.2050704@netlab.hut.fi \
--to=emmanuel@netlab.hut.fi \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@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.