Page tree

Versions Compared

Key

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

...

Tip
titleHow to solve the same task using CLI commands
Expand
titleCommands list
Code Block
languagetext
themeEmacs
Master'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
Step 3a
route add default 172.16.0.2
Step 4
netstat -r
Step 4a
netstat -r

Slave'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
Step 3a
route add default 172.16.0.1

Step 4
netstat -r
Step 4a
netstat -r

...

Routing configuration for the data traffic

...

using a Point-to-Multipoint scheme

Let's look at the task of performing the routing configuration for the data traffic at the using a PtMP scheme (Figure 3). Within  With this task, should be organized the connectivity between PC-1, PC-2, PC-3 and PC-4 should be established using routing, since all the PCs belong to different subnets.

Center

                                                              

Figure 3 - Scheme of the data traffic routing configuration for the InfiLINK 2x2 , / InfiMAN 2x2 families of devices

Let's look at the step-by-step configuration of the wireless devices using the Web interface:

...

DescriptionAdd the IP addresses to the devices interfaces in accordance with interfaces of the devices according to the scheme.
BS

CPE2

CPE3

CPE4

...

DescriptionAnalyze the routing table: after adding the IP addresses to the device devices' interfaces, the routing tables were filled up with entries about specifying the directly connected networks (markmarked as C).
BS

CPE2

CPE3

CPE4

Step 3
Description

Add static routes for connection the connectivity between the PCs.

Three static routes should be added on each wireless devicesdevice, for the other 3 PCs that are not directly connected.

BS

CPE2

CPE3

CPE4

Step 3a
Description

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

The routing table on of the BS is not possible to optimizecannot be optimized, as the BS has separate connections with each station with no common point.

BS-
CPE2

CPE3

CPE4

Step 4
DescriptionAnalyze the routing table: three static entries (flag S) have been added to the routing table of each device.
BS

CPE2

CPE3

CPE4

...

DescriptionIf a default route was added in step 3a, a corresponding entry (flag S) will be added to the routing table.
BSChanges are not required on the BS.
CPE2

CPE3

CPE4

Step 5
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 management traffic routing was also organizedestablished.
Tip
titleThe How to solve the same task solving using the 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

...