From: Ira Abramov <lists-lartc@ira.abramov.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] same address range, different interfaces
Date: Wed, 19 Nov 2003 15:44:15 +0000 [thread overview]
Message-ID: <marc-lartc-106925676212315@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106924600531191@msgid-missing>
Quoting Ira Abramov, from the post of Wed, 19 Nov:
> I have a router machine, kernel 2.4.20 with 4 physical interfaces (but
> many more virtual ones over differel VLANs). we need to NAT/route
> between hosts on different VLANs, but with the same address, for
> instance, 10.0.0.2 reachable via eth0.2 needs to talk to 10.0.0.2 which
> is on eth0.3.
I'll simplify it further.
What I need is a mechanism that translates the source BEFORE routing and
then the destination AFTER routing. is that possible with iproute2 or do I
need to resort to netfilter?
--
All rights reserved
Ira Abramov
http://ira.abramov.org/email/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-11-19 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 12:38 [LARTC] same address range, different interfaces Ira Abramov
2003-11-19 15:44 ` Ira Abramov [this message]
2003-11-20 9:44 ` Ira Abramov
2003-11-20 15:32 ` Ira Abramov
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-106925676212315@msgid-missing \
--to=lists-lartc@ira.abramov.org \
--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.