Editing Virtual Ethernet device
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 130: | Line 130: | ||
The following steps are needed when the [[CT]] is '''not''' bridged to a [[CT0]] network interface. That is because the [[CT]] is connected to a virtual network that is "behind" [[CT0]]. [[CT0]] must forward packets between its physical network interface and the virtual network interface where [[CT]] is located. The first step below to configure the interface is not necessary if the container has been started, since the device will have been initialized. | The following steps are needed when the [[CT]] is '''not''' bridged to a [[CT0]] network interface. That is because the [[CT]] is connected to a virtual network that is "behind" [[CT0]]. [[CT0]] must forward packets between its physical network interface and the virtual network interface where [[CT]] is located. The first step below to configure the interface is not necessary if the container has been started, since the device will have been initialized. | ||
<pre> | <pre> | ||
− | [host-node]# ifconfig veth101.0 | + | [host-node]# ifconfig veth101.0 up |
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/veth101.0/forwarding | [host-node]# echo 1 > /proc/sys/net/ipv4/conf/veth101.0/forwarding | ||
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/veth101.0/proxy_arp | [host-node]# echo 1 > /proc/sys/net/ipv4/conf/veth101.0/proxy_arp |