tomponline / lxc-routednet Goto Github PK

Hi, I can successfully install lxc-routenet without issue on a Debian Buster server using lxc 3.0.3 and go 1.14.2. I can start the new container without error and can then ping the container's interface from the host... however when I attach to the container I have no access to either the hosts interface or the larger world.

From the hosts routing table I can see a route to the container:
192.168.31.3 0.0.0.0 255.255.255.255 UH 0 0 0 vethTXM68R

From inside the container, I see this:
# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 169.254.0.1 0.0.0.0 UG 0 0 0 eth0 169.254.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0

...however, as mentioned, I cannot ping or resolv anything outside the container.

Can you give any additional guidance for configuring networking from inside the container? Is there anything else I need to do to get this working? At this point I'm assuming I need to configure something else but I'm not sure what. For example, do I need to configure a static route on my router? Sorry if this is a basic question but I'm not sure how to continue.

Thanks!

I have 10 containers, all with public IPs. some containers can ping from A to B, but pinging fails when tried from B to A.
I am using veth and a regular Linux bridge
auto br0
iface br0 inet manual
bridge-ports eth1
bridge-stp off
bridge-fd 0
bridge_maxwait 0

lxc.net.0.type = veth
lxc.net.0.flags = up
lxc.net.0.link = br0
lxc.net.0.name = eth0
lxc.net.0.l2proxy=1

What is the best configuration so my containers can talk to each other?