From: ebiederm@xmission•com (Eric W. Biederman)
To: "Rémi Denis-Courmont" <remi@remlab•net>
Cc: Chris Friesen <cbf123@mail•usask.ca>, netdev@vger•kernel.org
Subject: Re: recommended way to support duplicate IP addresses on different VLANs?
Date: Fri, 15 Jul 2011 17:24:54 -0700 [thread overview]
Message-ID: <m1tyankr6x.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <201107111804.26500.remi@remlab.net> ("Rémi Denis-Courmont"'s message of "Mon, 11 Jul 2011 18:04:25 +0300")
"Rémi Denis-Courmont" <remi@remlab•net> writes:
> 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.
For reference.
The namespace file descriptor code is in 3.0. setns is present in the
latest glibc. And the iproute support is just finishing up.
What doesn't exist at the moment is a handy socketat library
function to make it a userspace program that uses multiple network
namespaces trivial. But that is only a few lines of code.
It sounds like you don't need the full generality of network
namespaces but if you do the functionality is present.
Eric
next prev parent reply other threads:[~2011-07-16 0:25 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
2011-07-11 15:48 ` Chris Friesen
2011-07-11 15:56 ` Ben Greear
2011-07-16 0:24 ` Eric W. Biederman [this message]
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=m1tyankr6x.fsf@fess.ebiederm.org \
--to=ebiederm@xmission$(echo .)com \
--cc=cbf123@mail$(echo .)usask.ca \
--cc=netdev@vger$(echo .)kernel.org \
--cc=remi@remlab$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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