docs: change code blocks from "shell" to "console"
Change-Id: I136fccfc06e07fb68d11df686c59687362fb8827
Signed-off-by: John DeNisco <jdenisco@cisco.com>
diff --git a/docs/usecases/Routing.rst b/docs/usecases/Routing.rst
index 0c5908f..cecc263 100644
--- a/docs/usecases/Routing.rst
+++ b/docs/usecases/Routing.rst
@@ -9,7 +9,7 @@
Enter container *cone*, and check the current network configuration:
-.. code-block:: console
+.. code-block:: shell
root@cone:/# ip -o a
1: lo inet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever
@@ -24,7 +24,7 @@
Check if the interfaces are down or up:
-.. code-block:: console
+.. code-block:: shell
root@cone:/# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
@@ -42,7 +42,7 @@
Make sure your loopback interface is up, and assign an IP and gateway to veth_link1.
-.. code-block:: console
+.. code-block:: shell
root@cone:/# ip link set dev lo up
root@cone:/# ip addr add 172.16.1.2/24 dev veth_link1
@@ -54,7 +54,7 @@
Run some commands to verify the changes:
-.. code-block:: console
+.. code-block:: shell
root@cone:/# ip -o a
1: lo inet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever
@@ -77,7 +77,7 @@
After thats done for *both* containers, exit from the container if you're in one:
-.. code-block:: console
+.. code-block:: shell
root@ctwo:/# exit
exit
@@ -85,7 +85,7 @@
In the machine running the containers, run **ip link** to see the host *veth* network interfaces, and their link with their respective *container veth's*.
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# ip link
1: lo: <LOOPBACK> mtu 65536 qdisc noqueue state DOWN mode DEFAULT group default qlen 1
@@ -112,7 +112,7 @@
With VPP in the host machine, show current VPP interfaces:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# vppctl show inter
Name Idx State MTU (L3/IP4/IP6/MPLS) Counter Count
@@ -122,14 +122,14 @@
Based on the names of the network interfaces discussed previously, which are specific to my systems, we can create VPP host-interfaces:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# vppctl create host-interface name vethQL7K0C
root@localhost:~# vppctl create host-interface name veth8NA72P
Verify they have been set up properly:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# vppctl show inter
Name Idx State MTU (L3/IP4/IP6/MPLS) Counter Count
@@ -142,14 +142,14 @@
Set their state to up:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# vppctl set interface state host-vethQL7K0C up
root@localhost:~# vppctl set interface state host-veth8NA72P up
Verify they are now up:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# vppctl show inter
Name Idx State MTU (L3/IP4/IP6/MPLS) Counter Count
@@ -160,7 +160,7 @@
Add IP addresses for the other end of each veth link:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# vppctl set interface ip address host-vethQL7K0C 172.16.1.1/24
root@localhost:~# vppctl set interface ip address host-veth8NA72P 172.16.2.1/24
@@ -168,7 +168,7 @@
Verify the addresses are set properly by looking at the L3 table:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# vppctl show inter addr
host-vethQL7K0C (up):
@@ -179,7 +179,7 @@
Or looking at the FIB by doing:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# vppctl show ip fib
ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto ] locks:[src:plugin-hi:2, src:default-route:1, ]
@@ -238,7 +238,7 @@
At long last you probably want to see some pings:
-.. code-block:: console
+.. code-block:: shell
root@localhost:~# lxc-attach -n cone -- ping -c3 172.16.2.2
PING 172.16.2.2 (172.16.2.2) 56(84) bytes of data.