Common Networking HOWTOs - Revision history

128.179.66.4 at 11:18, 9 August 2011

2011-08-09T11:18:30Z

Narcisgarcia: /* DHCP supplied addresses */ Bridging Network Connections with Debian

2010-11-03T13:15:58Z

‎DHCP supplied addresses: Bridging Network Connections with Debian

83.108.233.203: /* DHCP supplied addresses */

2010-01-30T17:05:36Z

‎DHCP supplied addresses

64.65.78.18: /* Veth */

2010-01-25T02:33:04Z

‎Veth

Guaka: VE?

2009-04-08T13:59:37Z

VE?

Blueroomhosting: Added static public addresses section

2008-06-13T00:17:32Z

Added static public addresses section

Blueroomhosting: /* Private VEs (not directly visible from the LAN) */

2008-06-12T16:06:39Z

‎Private VEs (not directly visible from the LAN)

Blueroomhosting: Added to HOWTO and Networking categories

2008-06-12T15:50:46Z

Added to HOWTO and Networking categories

Blueroomhosting: New page: While other pages do a great job of going into the details of veth and venet networking, this page is all about getting the results you want quickly. == Private VEs (not directly visible ...

2008-06-12T15:43:02Z

New page: While other pages do a great job of going into the details of veth and venet networking, this page is all about getting the results you want quickly. == Private VEs (not directly visible ...

New page

While other pages do a great job of going into the details of veth and venet networking, this page is all about getting the results you want quickly.

== Private VEs (not directly visible from the LAN) ==

== Public VEs (with their own IP addresses) ==

=== Static addresses ===

=== DHCP supplied addresses ===

For this section the following assumptions have been made:

* The host is connected to the LAN by eth0, and also uses DHCP.
* The DHCP server is another machine on the LAN.

To make the VEs truly part of the LAN it is best to create a bridge that binds them, and the LAN, together.
Configuring the host to use a bridge when it boots is distribution specific and beyond the scope of this article.
It can be done from the command line as follows:

<pre>
bring eth0 down (distro dependent)
[host-node]# /etc/init.d/net.eth0 down
-- or --
[host-node]# ifdown eth0
etc.

create the bridge
[host-node]# brctl addbr br0

add eth0
[host-node]# brctl addif br0 eth0

each bridge interface must be up, but with no ip address
[host-node]# ifconfig eth0 0

now run DHCP for the bridge (client dependent)
[host-node]# dhcpcd br0
-- or --
[host-node]# dhclient3 br0
etc.
</pre>

At this stage the host should be present on the LAN (test with pings), much as it was before, only now it is using a bridge that can have other interfaces attached to it.

Starting with a new VE (101), which should have no networking configured and be running, it is now necessary to add a veth device. First the mac address of eth0 must be determined.

<pre>
[host-node]# ifconfig eth0
...
HWaddress 00:12:34:56:78:9B
...
</pre>

Now a new mac address must be invented, preferably higher than eth0's address.

<pre>
[host-node]# easymac.sh -R
00:12:34:56:78:9A
</pre>

The new veth device can be assigned using the above information.

<pre>
[host-node]# vzctl set 101 --veth_add veth101.0,00:12:34:56:78:9A,eth0,00:12:34:56:78:9B --save
</pre>

Now add the new device to the bridge and bring it up on the host.

<pre>
[host-node]# ifconfig veth101.0 0
[host-node]# brctl addif br0 veth101.0
</pre>

Finally, the network should be fully in place, so run the DHCP client inside the VE
<pre>
[host-node]# vzctl enter 101
101# dhcpcd venet0:0
</pre>

@@ Line 3: / Line 3: @@
 == 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.
+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 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).

@@ Line 113: / Line 113: @@
 # dhcpcd eth0
 </pre>
 [[Category: HOWTO]]
 [[Category:Networking]]

@@ Line 111: / Line 111: @@
 <pre>
 [host-node]# vzctl enter 101
-# dhcpcd venet0:0
+# dhcpcd eth0
 </pre>
 [[Category: HOWTO]]
 [[Category:Networking]]

@@ Line 28: / Line 28: @@
 === Veth ===
-This is a stub
+See the [[VEs and HNs in same subnets]] article.
 == Public VEs (with their own IP addresses) ==

@@ Line 3: / Line 3: @@
 == 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.
+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).

@@ Line 34: / Line 34: @@
 === Static addresses ===
-This is a stub.
+This is very similar to using private addresses, except there is no need for masquerading and the VE will be visible to others on the LAN.
 === DHCP supplied addresses ===