Re: How do containers tie to multiple IP's on a NIC?

[Whit Blauvelt <whit-M6G8SDWvnhfby3iVrkZq2A@public.gmane.org>]

On Mon, Jul 05, 2010 at 05:50:38PM +0800, Pavel Labushev wrote:

> What exactly are you trying to achieve? A transparent packet forwarding
> between containers and external networks?

I'm trying to get the overview of what can be achieved, and how. Unless I've
missed it, there's not much documentation on even moderately complex use of
containers. Since the capabilities are rapidly advancing, maybe I'm just
asking the question a few months too early? From the outside, as someone new
to containers, it looks like a maze where there are a number of entrances,
each of which may lead approximately to the goal, but some of which may be
dead ends. 

The examples I have found are along the lines of: Here's how to start a
container, bridge it to a NIC which has a single IP assigned, ssh to it ...
and the examples stop there. What I'd like to achieve is a setup where, say,
a box with 6 IPs on an external network - on eth0 before bridging (or its
alternatives) - can have 5 of those IPs each dedicated to different single
container.

I'm not committed to a particular way of achieving that yet, just looking at
the maze entrances wondering which to choose. Standard packet forwarding,
routing and firewalling in Linux isn't what I'm asking about, I use that
stuff frequently in complex ways, and I already run some things in simple
chroots. I'm trying to learn how, on a test basis, to set up something like
a production environment with lxc, where it involves multiple IPs, WAN or
LAN, on each single NIC, behind some of which should be containers which
effectively own individual IPs, publicly available.

It's probably looking harder to me than it is, because I haven't found a
clear description of it yet. 

Thanks,
Whit