From: Ira Abramov <lists-lartc@ira.abramov.org>
To: lartc@vger.kernel.org
Subject: [LARTC] same address range, different interfaces
Date: Wed, 19 Nov 2003 12:38:54 +0000 [thread overview]
Message-ID: <marc-lartc-106924600531191@msgid-missing> (raw)
Hello people,
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.
clearly if they were of different subnets this poses no problem, but I
want to create an iproute2-based setup where they each know each other
by a different address, as set on the router, for instance one could
access the other at 10.1.1.2 and the other will access the first one at
10.1.2.2.
in other words:
Host A[]--------[Router]------[]Host B
A and B's address is the same,
each knows the other at addresses A' and B' as NATed by the router. This
solution should be possible with iproute2 logicly, but I have exhausted
Google and this list's archives trying to find a documentation for this.
just addring rule and route to each as the FAQs simply list (for static
NAT) does not give expected results. I'll forward here any outputs you
may be interested in, let me know how I can help you help me.
our final goal is to be able to do a proof f concept of this with N
physical interfaces and M VLANs on each, and see what the limits and
overheads do.
thanks in advance,
Ira
--
On orange alert
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 reply other threads:[~2003-11-19 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 12:38 Ira Abramov [this message]
2003-11-19 15:44 ` [LARTC] same address range, different interfaces Ira Abramov
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-106924600531191@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.