From: "John A. Sullivan III" <jsullivan@opensourcedevelopmentcorp.com>
To: "Irvin, Michael Thad" <michael.irvin@Citicorp.com>
Cc: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: Re: NATTING for a whole network.
Date: Fri, 10 Dec 2004 14:02:01 -0500 [thread overview]
Message-ID: <1102705228.3295.15.camel@localhost> (raw)
In-Reply-To: <4D7EBAB4CCB6DB4AB7EE598E9ED186950474D69B@asusfl45cex08.us-fl.cards.citicorp.com>
On Thu, 2004-12-09 at 12:22, Irvin, Michael Thad wrote:
> I'm kinda new at this iptables thing. I've been running into a problem with
> trying to NAT for a class C subnetted class A network...i.e. 10.168.1.0/24.
> The syntax I've been using is as follows -- $ipt -t nat -A POSTROUTING -o
> $outside -j SNAT -to-source $lan, with the variable $lan = "10.168.1.0/24".
> Everytime I've ran the script I get the following error <iptables v.x.x.x
> Bad IP Address. Can anyone please help me with the proper syntax to make
> this work? I've tried various options such the one above, also including
> the whole subnetmask and playing around with different delimitation
> options, nothing seems to work.
<snip>
I generally use the NETMAP patch from patch-o-matic for this. SNAT/DNAT
does not necessarily create a straight mapping of addresses as far as I
know whereas NETMAP does. In fact we use it all the time in the ISCS
network security project (http://iscs.sourceforge.net) to resolve
conflicting IP address space problems. Hope this helps - John
--
John A. Sullivan III
Open Source Development Corporation
Financially sustainable open source development
http://www.opensourcedevel.com
prev parent reply other threads:[~2004-12-10 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 17:22 NATTING for a whole network Irvin, Michael Thad
2004-12-10 18:56 ` primero@hdr-roma.it
2004-12-10 18:58 ` Andreas Grabner
2004-12-10 18:58 ` primero@hdr-roma.it
2004-12-10 18:59 ` Jason Opperisano
2004-12-10 19:02 ` John A. Sullivan III [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=1102705228.3295.15.camel@localhost \
--to=jsullivan@opensourcedevelopmentcorp.com \
--cc=michael.irvin@Citicorp.com \
--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