Difference between revisions of "Solving connectivity to container problem for openVZ"
From Notes_Wiki
(Created page with "<yambe:breadcrumb>Troubleshooting_openVZ_issues|Troubleshooting openVZ issues</yambe:breadcrumb> =Solving connectivity to container problem for openVZ= If some of the contain...") |
m |
||
| Line 1: | Line 1: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Virtualization tools]] > [[OpenvZ]] > [[Troubleshooting openVZ issues]] > [[Solving connectivity to container problem for openVZ]] | |||
If some of the containers have interfaces added using '--netif_add' and such containers are started without adding the corresponding 'veth<n>.<m>' interface to a software bridge then complete networking of containers that use venet0 based network stops. To solve this problem use 'vzlist -a' to list all the containers which do not have IP address column and then use 'brctl addif <bridge> <interface>' command to add interface to appropriate bridge. | If some of the containers have interfaces added using '--netif_add' and such containers are started without adding the corresponding 'veth<n>.<m>' interface to a software bridge then complete networking of containers that use venet0 based network stops. To solve this problem use 'vzlist -a' to list all the containers which do not have IP address column and then use 'brctl addif <bridge> <interface>' command to add interface to appropriate bridge. | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Virtualization tools]] > [[OpenvZ]] > [[Troubleshooting openVZ issues]] > [[Solving connectivity to container problem for openVZ]] | |||
Latest revision as of 13:10, 24 August 2022
Home > CentOS > CentOS 6.x > Virtualization tools > OpenvZ > Troubleshooting openVZ issues > Solving connectivity to container problem for openVZ
If some of the containers have interfaces added using '--netif_add' and such containers are started without adding the corresponding 'veth<n>.<m>' interface to a software bridge then complete networking of containers that use venet0 based network stops. To solve this problem use 'vzlist -a' to list all the containers which do not have IP address column and then use 'brctl addif <bridge> <interface>' command to add interface to appropriate bridge.
Home > CentOS > CentOS 6.x > Virtualization tools > OpenvZ > Troubleshooting openVZ issues > Solving connectivity to container problem for openVZ
