Infinet Wireless: Technical Documentation
Page tree

Versions Compared

Old Version 13

changes.mady.by.user Unknown User (msirbu)

Saved on

compared with

New Version 14

changes.mady.by.user Unknown User (msirbu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Description

Since the data from any CPE to the BS or to another CPE goes through the BS, the routing tables of the CPEs can be optimized. Instead of three static entries, one default route can be added.

The routing table of the BS cannot be optimized, as the BS has separate connections with each station with subscriber, havinng no common point.

BS-
CPE2

CPE3

CPE4

...

DescriptionThe task has been solved: the connectivity between PC-1, PC-2, PC-3 and PC-4 was successfully established. Note that along with the data traffic routing, the routing for the management traffic routing was also established.
Tip
titleHow to solve the same task using CLI commands
Expand
titleCommands list
Code Block
languagetext
themeEmacs
BS's device configuration:
Step 1
ifc eth0 192.168.1.1/24
ifc rf5.0 172.16.0.1/29
Step 2
netstat -r
Step 3
route add 192.168.2.0/24 172.16.0.2
route add 192.168.3.0/24 172.16.0.3
route add 192.168.4.0/24 172.16.0.4
Step 4
netstat -r

CPE-2's device configuration:
Step 1
ifc eth0 192.168.2.2/24
ifc rf5.0 172.16.0.2/29
Step 2
netstat -r
Step 3
route add 192.168.1.0/24 172.16.0.1
route add 192.168.3.0/24 172.16.0.3
route add 192.168.4.0/24 172.16.0.4
Step 3a
route add default 172.16.0.1
Step 4
netstat -r
Step 4a
netstat -r

CPE-3's device configuration:
Step 1
ifc eth0 192.168.3.3/24
ifc rf5.0 172.16.0.3/29
Step 2
netstat -r
Step 3
route add 192.168.1.0/24 172.16.0.1
route add 192.168.2.0/24 172.16.0.2
route add 192.168.4.0/24 172.16.0.4
Step 3a
route add default 172.16.0.1
Step 4
netstat -r
Step 4a
netstat -r
CPE-4 device configuration
Step 1
ifc eth0 192.168.4.4/24
ifc rf5.0 172.16.0.4/29
Step 2
netstat -r
Step 3
route add 192.168.1.0/24 172.16.0.1
route add 192.168.2.0/24 172.16.0.2
route add 192.168.3.0/24 172.16.0.3
Step 3a
route add default 172.16.0.1
Step 4
netstat -r
Step 4a
netstat -r

...

Let's look at the task of performing the routing configuration for the management traffic (Figure 4). Within this task, the  The Slave's device management interface should be accessible to the engineer working at the PC, while . Since the PC and the Slave devices belong to different subnets routing must be used.

Center

Figure 4 - Scheme of Routing configuration for the management traffic routing configuration for using the InfiLINK XG / InfiLINK XG 1000 families of devices

Let's perform a step by step configuration of for the Master and Slave devices using the Web interface:

...

Let's look at the task of performing the routing configuration for the management traffic (Figure 5).  Within this task, the The Slave's device management interface should be accessible to the engineer working at the PC, while . Since the PC and the Slave devices belong to different subnets routing will be used.

Center

Figure 5 - Scheme of Routing configuration for the management traffic routing configuration for using the Quanta 5 / Quanta 70 families of devices

...

DescriptionAnalyze the routing table: after adding IP addresses to the device's interfaces, the routing table was filled up with entries specifying the directly connected networks (mark marked as C).
Master

Slave

Step 3
Description

Add static routes for establishing the communication between the PC and Slave devices.

The Quanta 5 and the Quanta 70 families of devices allows allow to configure only the default route.

MasterThe Master device is intermediate on the path of the packets between the PC and the Slave. Routes towards the PC and towards the Slave have been added to the Master's device routing table (see step 2), so there is no need to add static entries.
Slave

...