From: "Rémi Denis-Courmont" <remi@remlab.net>
To: Chris Friesen <cbf123@mail.usask.ca>
Cc: netdev@vger.kernel.org
Subject: Re: recommended way to support duplicate IP addresses on different VLANs?
Date: Mon, 11 Jul 2011 18:04:25 +0300 [thread overview]
Message-ID: <201107111804.26500.remi@remlab.net> (raw)
In-Reply-To: <4E1B0F86.2040508@mail.usask.ca>
Le lundi 11 juillet 2011 17:58:14 Chris Friesen, vous avez écrit :
> Hi all,
>
> We've got a server that sits on multiple VLANs. Each VLAN is segregated
> and doesn't know about the others. The IP address ranges in each of the
> VLANs may overlap, and the server may be assigned the same IP address in
> multiple VLANs.
>
> We've got a messy solution now involving unique internal addresses and
> NATing between those and the duplicate external addresses, but I'm
> wondering if there is a cleaner way to handle this.
>
> It seems like network namespaces would work, but it would require
> multiple instances of our software which is a dealbreaker.
>
> Is there any other way to deal with this scenario?
Namespace file descriptors if/when they get accepted.
Or then binding sockets to devices (SO_BINDTODEVICE) might work.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
next prev parent reply other threads:[~2011-07-11 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 14:58 recommended way to support duplicate IP addresses on different VLANs? Chris Friesen
2011-07-11 15:04 ` Rémi Denis-Courmont [this message]
2011-07-11 15:48 ` Chris Friesen
2011-07-11 15:56 ` Ben Greear
2011-07-16 0:24 ` Eric W. Biederman
2011-07-17 15:21 ` David Lamparter
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=201107111804.26500.remi@remlab.net \
--to=remi@remlab.net \
--cc=cbf123@mail.usask.ca \
--cc=netdev@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.