All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] help on iproute2
Date: Sat, 02 Mar 2002 13:24:45 +0000	[thread overview]
Message-ID: <marc-lartc-101507553527272@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101506260304664@msgid-missing>

On Sat, Mar 02, 2002 at 01:48:43AM -0800, Bambang Yulianto wrote:
> here is the pic :
> 
> [internet]----------[Linux]----------[LAN]
>     |                  |               |
> 202.149.83.192-207  202.149.83.194   192.168.0.1-35

Very good!

> ip rule add from 192.168.0.0/30 nat 202.149.83.195
> ip rule add from 192.168.0.4/30 nat 202.149.83.196
> ip rule add from 192.168.0.8/30 nat 202.149.83.197

I don't think this syntax works anymore. I would do this with iptables,
http://www.iptables.org - that syntax is far more widely used. I'm not even
sure if it ever worked! Every packet coming from 192.168.0.1 or 0.2 or 0.3
will get assigned 202.149.83.195 - this is information loss, there is no way
to map back.

Otherwise, read the iproute documentation, it's called ip-cref.tex I think.

But I think you should use iptables and SNAT - you need a way to map packets
back using a table.

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-03-02 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-02  9:48 [LARTC] help on iproute2 Bambang Yulianto
2002-03-02 13:24 ` bert hubert [this message]
2002-03-02 13:45 ` Julian Anastasov
2002-03-05 17:36 ` Ard van Breemen

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-101507553527272@msgid-missing \
    --to=ahu@ds9a.nl \
    --cc=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 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.