On Thu, 2011-02-03 at 09:09 -0800, Dean Mao wrote:
> You can just add a new bridge with "brctl addbr br7" if you wanted to
> add a bridge 7... then configure it with "ifconfig br7 172.16.0.1
> netmask 255.255.255.0 up" and you'll have a new network on the same
> computer.
Didn't know that... I th
The bridges are essentially dummy interfaces -- you can add as many as you
want, and have them on random networks if you want, and have complicated
routing schemes between them. I don't think you need to create a dummy
interface anywhere. You can just add a new bridge with "brctl addbr br7" if
yo
On Thu, 2011-02-03 at 09:13 -0200, Andre Nathan wrote:
> eth0 -> external network
> eth1 -> 10.0.0.0/16 network
> containers -> 192.168.0.0/16 network
Hmm I managed to do this creating a dummy interface and setting up a
bridge on it, so now I have
eth0 -> external network
eth1 -> 10.0.0.0/16 netw
On Wed, 2011-02-02 at 12:07 -0800, Dean Mao wrote:
> Yeah, it's quite easy to do this. Here's my lxc network config from
> one of my machines:
>
>
> lxc.network.type = veth
> lxc.network.flags = up
> lxc.network.link = br1
> lxc.network.ipv4 = 192.168.0.4/24
>
>
> My outside network is eth0/br
Yeah, it's quite easy to do this. Here's my lxc network config from one of
my machines:
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br1
lxc.network.ipv4 = 192.168.0.4/24
My outside network is eth0/br0, and my inside network is just br1. I add
these rules to forward br0 to
Hello
My host is configured with two networks as below:
eth0: external network a.b.c.d/24
eth1: internal network 10.1.0.0/16
I would like to configure my containers to belong to a third network
(say, 10.2.0.0/16), and then set up two NAT rules (one for eth0 and one
for eth1) to allow them to acc
