Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Konrads Smelkov konrads@interbaltika.com
To: lartc@vger.kernel.org
Subject: [LARTC] multiple subnets and nat in one LAN
Date: Tue, 13 Feb 2001 02:18:55 +0000	[thread overview]
Message-ID: <marc-lartc-98373940417010@msgid-missing> (raw)

<PRE>Here is the situation:
I have 2 subnets with real addresses and one with local (fake, 10.x.x.x).
So for local ones i do nat'ing to one real address. When i had only one &quot;real&quot; subnet i could settle with : 
iptables -t nat -A POSTROUTING -s ! realnet1/mask -j SNAT --to ipaddr-nat

so, right now, when i have two i have to do something like:

iptables -t nat -I POSTROUTING -s 10.0.0.0/24 -o eth1 -j SNAT --to ipaddr-nat
eth1 is link trough wich nat'ed ip's go out.
Q: Is this ok? My concern is about messages like this:

64 bytes from realipaddr2: icmp_seq=1 ttl%5 time$6 usec
&gt;<i>From gw (10.0.0.1): Redirect Host(New nexthop: realipaddr2)
</I>

</PRE>

                 reply	other threads:[~2001-02-13  2:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-lartc-98373940417010@msgid-missing \
    --to=lartc@vger.kernel.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