The IP addresses being recommended for the VM interface and the
"remote_ip" on the tunnel port are wrong. The host1 values were being
used before. Update to use the host2 values.

Signed-off-by: Cian Ferriter <cian.ferri...@intel.com>

---

v2:
- Refer directly to the commands that the host2 IP addresses should be
  used in.
---
 Documentation/howto/userspace-tunneling.rst | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/Documentation/howto/userspace-tunneling.rst 
b/Documentation/howto/userspace-tunneling.rst
index 4e23b2e0c..31d82fd5e 100644
--- a/Documentation/howto/userspace-tunneling.rst
+++ b/Documentation/howto/userspace-tunneling.rst
@@ -175,8 +175,16 @@ If the tunnel route is missing, adding it now::
 
     $ ovs-appctl ovs/route/add 172.168.1.1/24 br-phy
 
-Repeat these steps if necessary for `host2`, but using ``192.168.1.1`` and
-``172.168.1.2`` for the VM and tunnel interface IP addresses, respectively.
+Repeat these steps if necessary for `host2`, but using the below commands for
+the VM interface IP address::
+
+       $ ip addr add 192.168.1.2/24 dev eth0
+       $ ip link set eth0 up
+
+And the below command for the the `host2` VXLAN tunnel::
+
+       $ ovs-vsctl add-port br-int vxlan0 \
+         -- set interface vxlan0 type=vxlan options:remote_ip=172.168.1.1
 
 Testing
 -------
-- 
2.32.0

_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to