My physical server has one single NIC, currently holding the "public" IP address in the context of the LAN.
The device is identified as eth0 and has the following settings to allow routed networking:
In the guest containers, /etc/network/interfaces looks as follows (save for the different IP assigned to each, of course):
I can reach the host server (ping 10.10.10.1 is answering), but have no access to the internet.
What am I missing here?
I've tried a bridged model before and it does work, but I'd rather go for a routed configuration.
My aim is to keep the guest containers behind a reverse proxy even when accessed from any point in the LAN. A bridged connection, however, exposes the guest machines by assigning LAN IP's to them.
Thanks for your help!
The device is identified as eth0 and has the following settings to allow routed networking:
Code:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.0.7
netmask 255.255.255.0
gateway 192.168.0.1
auto vmbr0
iface vmbr0 inet static
address 10.10.10.1
netmask 255.255.255.0
bridge_ports none
bridge_stp off
bridge_fd 0
In the guest containers, /etc/network/interfaces looks as follows (save for the different IP assigned to each, of course):
Code:
# Auto generated lo interface
auto lo
iface lo inet loopback
# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
up ifconfig venet0 up
up ifconfig venet0 127.0.0.2
up route add default dev venet0
down route del default dev venet0
down ifconfig venet0 down
iface venet0 inet6 manual
up route -A inet6 add default dev venet0
down route -A inet6 del default dev venet0
auto venet0:0
iface venet0:0 inet static
address 10.10.10.2
netmask 255.255.255.255
I can reach the host server (ping 10.10.10.1 is answering), but have no access to the internet.
What am I missing here?
I've tried a bridged model before and it does work, but I'd rather go for a routed configuration.
My aim is to keep the guest containers behind a reverse proxy even when accessed from any point in the LAN. A bridged connection, however, exposes the guest machines by assigning LAN IP's to them.
Thanks for your help!