Differences

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

--- qos_project [2017/11/23 14:56] – [5. [CO1] Connecting the Platform] carine
+++ qos_project [2017/11/29 08:55] – [Extracts] carine
@@ Line 75: / Line 75: @@
 </WRAP>
-Routing table of GL-iNet:
-.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.1 : Loopback address
+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.
-.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)
+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:
-.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 10.0.0.2 of the TP-LINK router
+<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.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
+.0.0.2 of the TP-LINK router
+</code>
+Similarly, the routing table of the TP-LINK router shows the following:
+<code bash>
+.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>
+<code bash>
+#Configurations on TP-LINK router
+#Configuration of LAN interface :
+config interface 'lan'
+        option type 'bridge'
+        option ifname 'eth0'
+        option proto 'static'
+        option ipaddr '192.168.200.1'
+        option netmask '255.255.255.0'
+        option ip6assign '60'
+#Configuration of WAN interface :
+config interface 'wan'
+        option ifname 'eth1'
+#       option proto 'dhcp'
+        option proto 'static'
+        option ipaddr '10.0.0.2'
+        option netmask '255.255.255.0'
+#Configuration of the static route :
+config route
+        option interface 'wan'
+        option target '192.168.100.0'
+        option netmask '255.255.255.0'
+        option gateway '10.0.0.1'
+#Configuration of GL-iNET:
+All the network configuration on both routers (routing & addressing) are taken from /etc/config/network:
+On router GL-iNET, /etc/config/network shows the following:
+config interface 'lan'
+        option force_link '1'
+        option proto 'static'
+        option ipaddr '192.168.8.1'
+        option netmask '255.255.255.0'
+        option ip6assign '60'
+        option _orig_ifname 'eth1'
+        option _orig_bridge 'false'
+This interface (wifi) is configured with a static IP address 192.168.8.1/24
+config interface 'wan'
+        option ifname 'eth0'
+        option hostname 'GL-iNet-b2d'
+        option proto 'static'
+        option ipaddr '10.0.0.1'
+        option netmask '255.255.255.0'
+This interface (connected to the other router) is configured with a static IP address 10.0.0.1/24
+config route
+        option interface 'wan'
+        option target '192.168.200.0'
+        option netmask '255.255.255.0'
+        option gateway '10.0.0.2'
+This route enables GL-iNET to reach the network 192.168.200.0/24 via 10.0.0.2 of the other router.
+</code>
+===== Extracts =====