wikiroute

networking recipes

User Tools

Site Tools


qos_project

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
qos_project [2017/11/23 14:27] – [5. [CO1] Connecting the Platform] samerqos_project [2017/11/29 08:52] – [5. [CO1] Connecting the Platform] samer
Line 65: Line 65:
  
 ===== -. [CO1] Connecting the Platform ===== ===== -. [CO1] Connecting the Platform =====
-<WRAP center round tip 100%>+
 Describe and analyze the basic steps for ensuring the platform connectivity: addressing and routing Describe and analyze the basic steps for ensuring the platform connectivity: addressing and routing
 +<WRAP center round info 100%>
   * Accomplished   * Accomplished
       * Enable end-to-end communication       * Enable end-to-end communication
       * Analyse the addressing and routing (routing tables, DHCP, etc.)       * Analyse the addressing and routing (routing tables, DHCP, etc.)
   * Exceeded   * Exceeded
-      * Identify the necessary commands and configurations for enabling end-to-end communications +      * Identify the necessary commands and configurations for enabling end-to-end communication 
 +  
 </WRAP> </WRAP>
 +
 +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: 
 +
 +
 +<code bash>
 +10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.1 # Loopback address
 +192.168.8.0/24 dev wlan0  proto kernel  scope link  src 192.168.8.1 # connection to the wifi interface
 +192.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)
 +192.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>
 +
 +<code bash>
 +
 +Routing table of GL-iNet:
 +
 +10.0.0.0/24 dev eth1  src 10.0.0.2 # connection to directly connected network 10.0.0.0/24
 +192.168.100.0/24 via 10.0.0.1 dev eth1 # static route to the network 192.168.100.0/24 via the interface 
 +10.0.0.1 of the GL-iNet router
 +192.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'
 +
 +
 +</code>
 +===== Extracts =====
 +
  
qos_project.txt · Last modified: 2021/08/28 09:58 by samer