64
edits
Changes
→(2) An OVZ Hardware Node has two ethernet interfaces (TODO)
Every variant has its pros and cons, nevertheless for HN static IP configuration variant 2 seems to be acceptable (and the most simple).
== (2) An OVZ Hardware Node has two ethernet interfaces (TODO) ==(assume Assume you have 2 interfaces eth0 and eth1and want to separate local traffic (10.0.0.0/24)from the external traffic.Let's assign eth0 for the external traffic and eth0 for the local one.
If there is no aim to make VE accessible from HN and vice versa, it's enough to replace 'br0' with 'eth1' in the following steps of above configuration:
* Hardware Node configuration -> [[Using_private_IPs_for_Hardware_Nodes#Assign_the_IP_to_the_bridge|Assign the IP to the bridge]]
* Hardware Node configuration -> [[Using_private_IPs_for_Hardware_Nodes#Resurrect_the_default_routing|Resurrect the default routing]]
For the VE <-> HN connections availability it's nesessary to set an IP (local) to the 'br0'.
== (3) Putting VEs to different subnetworks ==
It's enough to set up the correct $VETH_IP_ADDRESS and $VE_DEFAULT_GATEWAY values in the
[[Using_private_IPs_for_Hardware_Nodes#Edit_the_VE.27s_configuration|above configuration]].
== See also ==
* [[Virtual network device]]
* [[Differences between venet and veth]]
[[Category: HOWTO]]
[[Category: Networking]]
