On 04.01.2012 00:26, Derek Simkowiak wrote: > I think this is the problem: > > lxc.network.hwaddr = 00:24:1d:2f:d6:5f > > You have that set to the hardware (MAC) address of your physical bridge > device. That is wrong.
Thanks, that was it, it works now. However, this was my home computer and everything is within 192.168, in reality I have host and container on completely different subnets: 1.1.1.0/30 - host (1.1.1.0 - network, 1.1.1.1 - gw/switchport, 1.1.1.2 - host, 1.1.1.3 - bcast) 2.2.2.0/30 - container (2.2.2.0 - network, 2.2.2.1 - gw/switchoort, 2.2.2.2 - host, 2.2.2.3 - bcast) Of course, in container one cannot add route to 1.1.1.0/30 since it doesn't know anything about it (you get that stupid message: "siocaddrt: no such process") and LXS is configured with: lxc.network.ipv4 = 2.2.2.2/30 I was thinking to add dummy eth0:1 that would have /30 that's on hosts bridge (1.1.1.0/30) and then adding default gateway to 1.1.1.2 (hosts bridge IP) or 1.1.1.1 (host's gw/switchport), but this doesn't work. Not only that I get "Destination Host Unreachable" when I try to ping something outside the container, but hosts network dies completely then and I can't access the server other than physically console it until LXC is stopped. Any ideas? Regards, Vedran ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
