From: Laurent Luyckx <lololuy@tiscali.be>
To: Francois LE BOURDELLES <flebourdelles@free.fr>
Cc: netfilter@lists.netfilter.org
Subject: Re: How to nat a full subnet ?
Date: 11 May 2003 13:03:00 +0200 [thread overview]
Message-ID: <1052650980.699.4.camel@laurent.luyckx.net> (raw)
In-Reply-To: <1052642696.17942.14.camel@charlebourg-2-81-57-105-138.fbx.proxad.net>
Have look a the NETMAP patch from p-o-m.
It creates a static 1:1 mapping of the network address.
(http://www.netfilter.org/documentation/pomlist/pom-combined.html#NETMAP)
Cheers.
On Sun, 2003-05-11 at 10:44, Francois LE BOURDELLES wrote:
> Hello happy netfilter users,
>
> First i use kernel 2.4.20 patch-o-matic'ed and iptables 2.4.8
> I have to SNAT an DNAT a full subnet (199.1.4.0/0 (internal address
> plan) to 1998.1.4.0/0 (external view))
> so I tried to use the command :
>
> iptables -t nat -A POSTROUTING -s 199.1.4.0/24 --to 199.1.4.0/24 -o
> tunnel0 -j SNAT
> (tunnel0 is a GRE typed tunnel)
>
> as the NAT Howto page shows (NAT-HOWTO-6.html).
>
> The aim is to have per exemple : 199.1.4.13 source changed to 198.1.4.13
>
> but this command is rejected :
>
> As I understand the sources (iptables and kernel) this is because the
> --to only accept single IP address
> or a range of IP-address, the last one for a pool automatic selection
> [And I do not know for what this could be used !).
>
> DO THE HOW-TO PAGES HAVE TO BE UPDATED (removing of the full subnet SNAT
> and DNAT) ... or the iptables/ipfilter updated ?
>
> Regards.
--
Laurent Luyckx <lololuy@tiscali.be>
next prev parent reply other threads:[~2003-05-11 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 8:44 How to nat a full subnet ? Francois LE BOURDELLES
2003-05-11 11:03 ` Laurent Luyckx [this message]
2003-05-11 15:57 ` Francois LE BOURDELLES
2003-05-12 13:44 ` Jet
2003-05-12 21:33 ` Francois LE BOURDELLES
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=1052650980.699.4.camel@laurent.luyckx.net \
--to=lololuy@tiscali.be \
--cc=flebourdelles@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox