Changes
no edit summary
== Private VEs (not directly visible from the LAN) ==
When starting with a new [[VE ]] that should not be directly visible on the LAN it is important to choose an appropriate IP address. By running "ifconfig -a" on the host it is possible to see all the networks the host is connected to. The VE should reside on a a new private network, choosing one of the 192.168.X.Y/24 subnets is a good choice.
For example, on a host which is already on a 192.168.1.0/24 subnet then the 192.168.2.0/24 subnet would be a reasonable choice (unless the host is already on that subnet too).
=== Veth ===
== Public VEs (with their own IP addresses) ==
=== Static addresses ===
This is a stubvery similar to using private addresses, except there is no need for masquerading and the VE will be visible to others on the LAN. In this example the host has eth0 with address 192.168.1.53, and the VE will be set up with 192.168.1.101. The VE (101) is assumed to be freshly created and started, with no networking currently set up. <pre>[host-node]# vzctl set 101 --ipadd 192.168.1.101 --save[host-node]# echo 1 > /proc/sys/net/ipv4/ip_forward</pre>
=== DHCP supplied addresses ===
<pre>
[host-node]# vzctl enter 101
101# dhcpcd venet0:0eth0
</pre>
* See also: [http://wiki.debian.org/BridgeNetworkConnections Bridging Network Connections with Debian]
[[Category: HOWTO]]
[[Category:Networking]]
