Difference between revisions of "Networking vserver guests"

Latest revision as of 23:09, 21 October 2011

Setting up network access to and from your vserver guests.

[edit] Introduction

Lets imagine, you have only one external IP -- $EXTIP.

You want to have several vservers running without worrying about port overlapping.

Example:

Two vservers run a default webserver, running on port 80. If each "guest" vserver shares an IP with the host, then the two webservers will conflict.

One solution is:

• All vservers are contained in a "virtual lan", say 192.168.1.x
• Each vserver has its own IP
• Control port forwarding on "parent" host. That is, run a router.

[edit] Configuration

[edit] Host

[edit] Optional: Load 'dummy' device(s)

[edit] Why?

This driver allows you to associate vServer guests with a virtual network device rather than the host's real network interface, which functions to hide packet counters from vServer guests. There is no other use for this step, so feel free to skip it if you are not worried about sharing packet counters. (Packet counts may be useful to an attacker with control of a vServer guest who wishes to perform side-channel attacks during cryptanalysis, or network traffic analysis against your host or other vServer guests. If you did not understand the last sentence and your installation is not particularly security sensitive, then the chances that you will encounter a skilled attacker and this will actually matter are slim to none and you should feel free to skip this section.)

[edit] Process

First you need to load the dummy interface driver (requires CONFIG_DUMMY=m in your kernel configuration)

# modprobe dummy

To have it automatically loaded on startup, add "loopback" to /etc/modules

Set up dummy0 interface on the parent host

# /etc/network/interfaces on a Debian box, 
# configure on other distros with your preferred way
auto dummy0
iface dummy0 inet static
    address 192.168.1.250
    netmask 255.255.255.0

[edit] Optional Extra Step

It is possible to facilitate further segregation (such that even dummy packet counters are never shared between guests). To do so, use:

# modprobe dummy numdummies=<number-of-devices-required>

... and associate each vServer with a unique dummy device.

[edit] Guests

Set up each guest vserver. If you skipped the host configuration above, you will need to replace dummy0 with the name of your host's primary network interface, for example eth0.

cd /etc/vservers/$VSERVER/interfaces/0
echo dummy0 > dev
echo 192.168.1.1 > ip
echo 1 > name
echo 24 > prefix

Consider using a value of name equal to the last digit of the IP for easy separation.

[edit] Host as router

Configure the host to act as a router.

For internal packets going outside, pretend each packet came from our external IP (put it in one line without backslash):

# iptables -t nat -A POSTROUTING -s 192.168.1.0/24 \ 
  ! -d  192.168.1.0/24 -j SNAT --to-source $EXTIP

For each service that runs on a vserver, map it to an external port. (For each ?) Vserver local address $VHOST and port $INTPORT, you select one external port $EXTPORT and run the following (put it in one line without backslash):

# iptables -t nat -A PREROUTING ! -s 192.168.1.0/24 \
  -m tcp -p tcp --dport $EXTPORT 
  -j DNAT --to-destination $VHOST:$INTPORT

That's all!

[edit] Verifying

Try ping pool.ntp.org from your vserver -- it should ping fine.

Try to connect to your $EXTIP:$EXTPORT (from another external host) -- you will successfully connect to service running on a guest vserver.

[edit] See also

• FAQ on private networking
• Permit guest sshd to bind to its IP address's port 22
• Networking_vserver_guests_RHEL