netdev - Re: recommended way to support duplicate IP addresses on different VLANs?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201107111804.26500.remi@remlab.net>
Date:	Mon, 11 Jul 2011 18:04:25 +0300
From:	"Rémi Denis-Courmont" <remi@...lab.net>
To:	Chris Friesen <cbf123@...l.usask.ca>
Cc:	netdev@...r.kernel.org
Subject: Re: recommended way to support duplicate IP addresses on different VLANs?

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html