Greetings,
Apologies for being a bonehead. the routing table in the container was problem 
#1, plus it turns out that I also forgot to turn on ip routing inside the vm. 
DOH!
Anyway, thanks so much for your help.
Have a good day.

> Date: Fri, 7 Sep 2012 11:35:06 +0700
> Subject: Re: [Lxc-users] Using VMware as a test-bed for hosting lxc 
> containers.
> From: l...@fajar.net
> To: spier...@hotmail.com
> CC: lxc-users@lists.sourceforge.net
> 
> On Fri, Sep 7, 2012 at 11:29 AM, Peter-Frank Spierenburg
> <spier...@hotmail.com> wrote:
> > Anyway, I am having trouble convincing the lxc guests to talk to the network
> > outside the box hosting the vm hosting the container.
> 
> If you use latest ubuntu it'll work out of the box.
> 
> > I've also got iptables configured to do the masquerading for the br0 device:
> 
> I usually just let lxc or libvirt create lxcbr0/virbr0, with the
> necessary rules. Much simpler that way.
> 
> 
> > Finally, one of the lxc containers:
> >
> > eth0      Link encap:Ethernet  HWaddr 00:16:3e:38:88:bb
> >           inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
> 
> 
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use
> > Iface
> > 0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 eth0
> 
> 
> And you're wondering why it DOESN't work? seriusly?
> Hint: check the ip address on eth0 and the gateway.
> 
> -- 
> Fajar
                                          
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Reply via email to