Editing Using private IPs for Hardware Nodes
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 4: | Line 4: | ||
[[Image:PrivateIPs_fig1.gif|An initial network topology]] | [[Image:PrivateIPs_fig1.gif|An initial network topology]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Prerequisites == | == Prerequisites == | ||
Line 21: | Line 15: | ||
[[Basic_operations_in_OpenVZ_environment|container(s) created]]. If not, follow the links to perform the steps needed. | [[Basic_operations_in_OpenVZ_environment|container(s) created]]. If not, follow the links to perform the steps needed. | ||
{{Note|don't assign an IP after container creation.}} | {{Note|don't assign an IP after container creation.}} | ||
+ | |||
+ | == Using a spare IP in the same range == | ||
+ | If you have a spare IP to use, you could assign this as a subinterface and use this as nameserver: | ||
+ | |||
+ | <pre>[HN] ifconfig eth0:1 *.*.*.* | ||
+ | [HN] vzctl set 101 --nameserver *.*.*.*</pre> | ||
== An OVZ Hardware Node has the only one Ethernet interface == | == An OVZ Hardware Node has the only one Ethernet interface == |