Page History

Table of contents

This part of the article contains routing configuration scenarios for various tasks. In order to focus on the article static routing topic, let's make the following assumptions, which are valid for all scenarios:

• a the radio link is links are established between the wireless devices;
• at the ending endpoint devices (the PCs), the IP addresses of the wireless devices to which they are directly connected are set as a gateway. After specifying the gateway, ending devices add each endpoint device adds a default route to the its routing table;
• switching is off on the devices of  of the InfiLINK 2x2, InfiMAN 2x2, InfiLINK Evolution, InfiMAN Evolution families;
• at in the examples for the InfiLINK 2x2, InfiMAN 2x2 family devices IP , InfiLINK Evolution, InfiMAN Evolution families of devices, the IP addresses are assigned to the physical interfaces, however, virtual interfaces can be used instead, for example, vlan interfaces.

InfiLINK 2x2, InfiMAN 2x2, InfiLINK Evolution, InfiMAN Evolution families of devices

Routing configuration for the management traffic

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

Image Removed

...

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

...

Step 2

Step 3

Image Removed

Description	Add static routes for the connection between the PC and the Slave.
Master	The Master device is intermediate on the path of the packets between the PC and the Slave. Routes to towards the PC and to towards the Slave have been added to the Master's device routing table table based on the configuration in the previous steps (see step 2), so there is no need to add static entries at the Master device.
Slave		A static route must be added towards PC1's network: Image Added

Step 3a

Image Removed

Description	A default route can be configured on the Slave device instead of a static route to towards the PC's network.
Master	No changes required.	Slave		No changes required.
Slave	Add the IP address of the Master's rf interface as default gateway, so that all the packets will be sent to it by default, if no other specific route is present: Image Added

Step 4

Step 4a

Step 5

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 4
netstat -r

Slave's device configuration:
Step 1
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-point scheme

Let's look at the task of performing the routing configuration for the data traffic at the using a PtP scheme (Figure 2). Within For this task, the connectivity between the PC-1 and the PC-2 devices should be organized established using routing, as PC-1 and PC-2 belong to different subnets.

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

...

Step 2

Step 3

Step 3a

Step 4

Step 4a

Step 5

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 this task, should be organized the  The connectivity between PC-1, PC-2, PC-3 and PC-4 using routing, all PCs belong to different subnets.

...

                                                               Image Removed

...

-4 should be established using routing, since all the PCs belong to different subnets.

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

...

Step 2

Step 3

Step 3a

Step 4

Step 4a

Step 5

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-22'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

InfiLINK XG, InfiLINK XG 1000 families of devices

...

Routing configuration for the management traffic

...

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

Center
Image RemovedImage Added Figure 4 - Scheme of Routing configuration for the management traffic routing configuration using the InfiLINK XG , / InfiLINK XG 1000 families of devices families

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

...

Description	Add the IP addresses to the interfaces of the devices interfaces in accordance with according to the scheme. Unlike the devices of the InfiLINK 2x2 , / InfiMAN 2x2 families, the IP address is not assigned to the physical interfaces, but to the virtual management interface (see the Switch section).
Master	Image RemovedImage Added
Slave	Image RemovedImage Added

Step 2

Step 3

Step 3a

Step 4

Step 4a

Step 5

Master's device configuration:
Step 1
ifc mgmt 192.168.1.1/24
ifc mgmt 172.16.0.1/29
Step 2
netstat -r
Step 4
netstat -r

Slave's device configuration:
Step 1
ifc mgmt 192.168.2.2/24
ifc mgmt 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

Quanta 5, Quanta 6, Quanta 70 families of devices

...

Routing configuration for the management traffic

...

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

Center
Image RemovedImage Added Figure 5 - Scheme of Routing configuration for the management traffic routing configuration using the Quanta 5, Quanta 6, Quanta 70families of devices families

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

...

Description	Add the IP addresses to the interfaces of the devices interfaces in accordance with according to the scheme. Unlike the devices of the InfiLINK 2x2 , / InfiMAN 2x2 families, the IP address is not assigned to the physical interfaces, but to the virtual management interface (see "Switch settings" section⁣).
Master	Image RemovedImage Added
Slave	Image RemovedImage Added

Step 2

Step 3

Step 4

Step 5

Master's device configuration:
Step 1
ifc eth0 192.168.1.1/24
ifc eth0 172.16.0.1/29
Step 2
netstat -r
Step 4
netstat -r
Slave's device configuration:
Step 1
ifc eth0 172.16.0.2/29
Step 2
netstat -r
Step 3
route add default 172.16.0.1
Step 4
netstat -r

Additional materials

Online courses

1. Quanta 5 / Quanta 6: Installation and Configuration.
2. InfiLINK XG Family Product.
3. InfiLINK 2x2 / InfiMAN 2x2: Initial Link Configuration and Installation.

...

1. Typical scenario of routing setting using Infinet Wireless devices. Part I.
   

Other

1. Quanta 5 / Quanta 6 device configuration.
2. InfiLINK XG, InfiLINK XG 1000 devices configuration.

3. Network configuration via Web interface for InfiLINK 2x2, InfiMAN 2x2 families devices.

4. Network configuration via Web interface for InfiLINK Evolution, InfiMAN Evolution families devices.
5. ifconfig command (interfaces configuration)
6. route command (static routes configuration)