Difference between revisions of "Differences between venet and veth"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(Category changed)
(Fixes)
Line 1: Line 1:
= Differences between venet and veth =
+
OpenVZ provides you to use either [[venet]] or [[veth]] devices (or both) for in-[[VE]] networking. Here we describe the differences between those devices.
* veth allows broadcasts in VE, so you can use even dhcp server inside VE or samba server with domain broadcasts or other such stuff.
+
 
 +
* veth allows broadcasts in VE, so you can use even a DHCP server inside a VE, or a samba server with domain broadcasts or other such stuff.
 
* veth has some security implications, so is not recommended in untrusted environments like HSP. This is due to broadcasts, traffic sniffing, possible IP collisions etc. i.e. VE user can actually ruin your ethernet network with such direct access to ethernet layer.
 
* veth has some security implications, so is not recommended in untrusted environments like HSP. This is due to broadcasts, traffic sniffing, possible IP collisions etc. i.e. VE user can actually ruin your ethernet network with such direct access to ethernet layer.
* With venet device, only node administrator can assign an IP to a VE. With veth device, network settings can be fully done on VE side. VE should setup correct GW, IP/mask etc and node admin then can only choose where your traffic goes.
+
* With venet device, only node administrator can assign an IP to a VE. With veth device, network settings can be fully done on VE side. VE should setup correct gateway, IP/netmask etc. and then a [[HN|node]] admin can only choose where your traffic goes.
 
* veth devices can be bridged together and/or with other devices. For example, in host system admin can bridge veth from 2 VEs with some VLAN eth0.X. In this case, these 2 VEs will be connected to this VLAN.
 
* veth devices can be bridged together and/or with other devices. For example, in host system admin can bridge veth from 2 VEs with some VLAN eth0.X. In this case, these 2 VEs will be connected to this VLAN.
 
* venet device is a bit faster and more efficient.
 
* venet device is a bit faster and more efficient.
* With veth devices IPv6 auto generates an address from MAC.
+
* With veth devices, IPv6 auto generates an address from MAC.
  
 
The brief summary:
 
The brief summary:
Line 22: Line 23:
 
|-
 
|-
 
! Network security
 
! Network security
| low <ref>Due to broadcasts, sniffing and possible IP collisions etc.</ref> || hi
+
| style="background: #ffdddd" | Low <ref>Due to broadcasts, sniffing and possible IP collisions etc.</ref> |
 +
| style="background: #ddffdd" | High
 
|-                         
 
|-                         
 
! Can be used in bridges
 
! Can be used in bridges
Line 28: Line 30:
 
|-
 
|-
 
! Performance
 
! Performance
| fast || fastest
+
| style="background: #ffdddd" | Fast
 +
| style="background: #ddffdd" | Fastest
 
|-
 
|-
 
|}
 
|}

Revision as of 20:48, 28 June 2006

OpenVZ provides you to use either venet or veth devices (or both) for in-VE networking. Here we describe the differences between those devices.

  • veth allows broadcasts in VE, so you can use even a DHCP server inside a VE, or a samba server with domain broadcasts or other such stuff.
  • veth has some security implications, so is not recommended in untrusted environments like HSP. This is due to broadcasts, traffic sniffing, possible IP collisions etc. i.e. VE user can actually ruin your ethernet network with such direct access to ethernet layer.
  • With venet device, only node administrator can assign an IP to a VE. With veth device, network settings can be fully done on VE side. VE should setup correct gateway, IP/netmask etc. and then a node admin can only choose where your traffic goes.
  • veth devices can be bridged together and/or with other devices. For example, in host system admin can bridge veth from 2 VEs with some VLAN eth0.X. In this case, these 2 VEs will be connected to this VLAN.
  • venet device is a bit faster and more efficient.
  • With veth devices, IPv6 auto generates an address from MAC.

The brief summary:

Differences between veth and venet
Feature veth venet
MAC address Yes No
Broadcasts inside VE Yes No
Traffic sniffing Yes No
Network security Low [1] | High
Can be used in bridges Yes No
Performance Fast Fastest
  1. Due to broadcasts, sniffing and possible IP collisions etc.