| Virtual ethernet device wiki [message #41325] |
Thu, 30 December 2010 21:40 |
sdad
Messages: 2
Registered: December 2010
Location: Grand Ledge, MI
|
Junior Member |
|
|
I am using kernel 2.6.26-686 and vzctl v 3.0.22
the wiki says:
Quote:Making a veth-device persistent
According to {CANT SUPPLY LINK} , a bug that stopped the veth device persistent was "Obsoleted now when --veth_add/--veth_del are introduced"
See {CANT SUPPLY THE LINK) Making_a_veth-device_persistent for a workaround that used to be described in this section.
That's it! At this point, when you restart the CT you should see a new line in the output, indicating that the interface is being configured and a new route being added. And you should be able to ping the host, and to enter the CT and use the network.
I read that --netif_add is same as --veth_add, so all my setup should work, right?
I could ping in and out of container, but lost it on hardware reboot. I didn't do something right! I don't view what the last paragraph says I should get.
This minor hurdle and then its on to bridge 4 containers to the same physical interface
Thank you for your time
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
