问题原文
原帖链接 · EthernetCable · CC BY-SA 3.0
I'm trying to setup multiple LXC containers on a host, each with public static IPs of their own.
My host is running the latest Ubuntu. It has a single network interface named eth0. The static IPs are pingable from the internet and are named eth0:210, eth0:211... The numbers after the colon are the least significant byte of the addresses. In addition to these interfaces I have br0 setup on the host's public IP. There are also the lo, veth2LPP9A, and lxcbr0 interfaces. The lxcbr0 has the address of a private IP.
The host /etc/network/interfaces looks like:
auto br0
iface br0 inet static
bridge_ports eth0
bridge_fd 0
[...]
So far I've used various online sources, including Bridging LXC containers to host eth0 so they can have a public IP to help me set this up.
The container's config file has:
lxc.network.type = veth
lxc.network.link = br0
I've removed the static lxc.network.ipv4 configuration from this file since it caused problems. When I ran lxc-ls --fancy with this configuration, I'd see the same public IP twice in the output. Additionally, it would mess with the subnet configuration of the container's /etc/network/interfaces.
Speaking of the container's interfaces file, it looks a bit like:
auto eth0
iface eth0 inet static
address [...]
netmask 255.255.255.255
#gateway [...]
dns-nameservers 8.8.8.8
post-up route add [...] dev eth0
post-up route add default gw [...]
post-down route del [...] dev eth0
post-down route del default gw [...]
I had to comment out the gateway and add the route add commands to this file. Otherwise, the container would take minutes to boot.
The /proc/sys/net/bridge/bridge-nf-* files on the host are all set to 0. The /proc/sys/net/ipv4/ip_forward value is 1.
The problem is, even though the container's "route -n" looks like it should, I can't ping out of the container. SSHing to what should be the container's IP, connects me to the host.
EDIT: Removing the container's static IP from the host did help, but now I'm getting a new error. Trying to ping the container from the host results in Redirect HostFrom , New nexthop. The packets are just going from the gateway to the host, repeatedly. Running a traceroute from the host shows that the first stop is at the gateway. Then all of the other routes are * * *. I get the same problem regardless if the container is online or not.
社区高分解答
原帖链接 · sebastianwagner · CC BY-SA 3.0
In fact you can set the address and gateway from within the host and configure the container not to touch the interface at all using the keyword manual.
Place this within the guests /etc/network/interfaces:
auto eth0
iface eth0 inet manual
Also leave it up to the container's config file to set up the interface:
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxc-bridge-nat
lxc.network.ipv4 = 192.168.100.16/24
lxc.network.ipv4.gateway = auto
The guest will behave like it's BIOS already set up the interface and just use it.
Especially explore lxc.network.ipv4.gateway.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
