All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Tomek Macioszek <tomekm@cea.pl>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: multiple mapping
Date: Wed, 01 Sep 2004 07:07:14 -0400	[thread overview]
Message-ID: <1094036834.2045.2.camel@localhost> (raw)
In-Reply-To: <006701c48ff9$9627b5b0$2a245cc2@cea05>

On Wed, 2004-09-01 at 03:59, Tomek Macioszek wrote:
> Hi
> I have my FIREWALL BOX with address 4.3.2.1 (eth0) and local address 192.168.10.0/24.
> Now I have SNAT:
> iptables -t nat -A POSTROUTING -s 192.168.10.0/24 -o eth1 -j SNAT --to 4.3.2.1
> I would like to make SNAT with i.e two external address.
> iptables -t nat -A POSTROUTING -s 192.168.10.0/28 -o eth1 -j SNAT --to 4.3.2.1
> iptables -t nat -A POSTROUTING -s 192.168.10.128/28 -o eth1 -j SNAT --to 4.3.2.2. It is good solution? Should I make alias for eth0 with address 4.3.2.2?
> Thanks for help and sorry for my English.
> Best regards
> T.  
Yes, that should work fine.  You will need to bind the address to eth0
so that it responds to ARP requests:
ip address add 4.3.2.2/?? dev eth0
Are you sure about the 28 bit mask for the subnets? It looks like you
want /25 unless you are hiding some of your addresses.  Good luck - John
-- 
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net 



  reply	other threads:[~2004-09-01 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01  7:59 multiple mapping Tomek Macioszek
2004-09-01 11:07 ` John A. Sullivan III [this message]
     [not found]   ` <007f01c49015$9544e610$2a245cc2@cea05>
2004-09-01 11:33     ` John A. Sullivan III
2004-09-01 16:44 ` Jose Maria Lopez

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=1094036834.2045.2.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=tomekm@cea.pl \
    /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.