Differences

This shows you the differences between two versions of the page.

--- qos_project [2017/11/29 08:52] – [5. [CO1] Connecting the Platform] samer
+++ qos_project [2017/11/29 08:54] – [5. [CO1] Connecting the Platform] samer
@@ Line 78: / Line 78: @@
 In order to analyse the addressing and routing on the platform, we need to look carefully on the interface configuration and routing tables of the different devices.
-Let us start with the routing devices. The routing table of the GL-iNet is shown using the command ``ip route`` and gives the following:
+Let us start with the routing devices. The routing table of the GL-iNet is shown using the command ''ip route'' and gives the following:
 <code bash>
 .0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.1 # Loopback address
-.168.8.0/24 dev wlan0  proto kernel  scope link  src 192.168.8.1 # connection to the wifi interface
+.168.8.0/24 dev wlan0  proto kernel  scope link  src 192.168.8.1 # Connection to the wifi interface
-.168.100.0/24 dev eth1  proto kernel  scope link  src 192.168.100.1 # connection to our LAN 192.168.100.0/24 (HP is part of this network)
+.168.100.0/24 dev eth1  proto kernel  scope link  src 192.168.100.1 # Connection to the LAN 192.168.100.0/24
-.168.200.0/24 via 10.0.0.2 dev eth0  proto static # static route to the 192.168.200.0/24 network via the interface
+.168.200.0/24 via 10.0.0.2 dev eth0  proto static # Static route to the 192.168.200.0/24 network via the interface
 .0.0.2 of the TP-LINK router
 </code>
+Similarly, the routing table of the TP-LINK router shows the following:
 <code bash>
-Routing table of GL-iNet:
 .0.0.0/24 dev eth1  src 10.0.0.2 # connection to directly connected network 10.0.0.0/24
 .168.100.0/24 via 10.0.0.1 dev eth1 # static route to the network 192.168.100.0/24 via the interface
 .0.0.1 of the GL-iNet router
 .168.200.0/24 dev br-lan  src 192.168.200.1 # connection to our LAN 192.168.200.0/24
 </code>