Include Page | ||||
---|---|---|---|---|
|
Hide_comments |
---|
Table of contents
Table of Contents | ||||
---|---|---|---|---|
|
This part of the article contains routing configuration scenarios for various tasks. In order to focus on the static routing topic, let's make the following assumptions, which are valid for all scenarios:
- the radio links are established between the wireless devices;
- at the endpoint devices (the PCs), the IP addresses of the wireless devices to which they are directly connected are set as gateway. After specifying the gateway, each endpoint devices device adds a default route to its routing table;
- switching is off on the devices of the InfiLINK 2x2 and , InfiMAN 2x2, InfiLINK Evolution, InfiMAN Evolution families;
- in the examples for the InfiLINK 2x2 and , InfiMAN 2x2, 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 concerning the routing configuration for the management traffic (Figure 1). For this task, the Slave's device management interface must 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.
Notecenter | |||
---|---|---|---|
|
| ||
An configuration example is given for the InfiLINK 2x2, InfiMAN 2x2 families devices, pay attention to the name of the radio interface on your devices during the scheme implementation. |
Center |
---|
Figure 1 - Routing configuration for the management traffic using the InfiLINK 2x2, InfiMAN 2x2, InfiLINK Evolution, InfiMAN Evolution families of devices |
Let's perform a step by step configuration for the Master and the Slave devices using the Web interface:
...
Description | Add the IP addresses to device's interfaces the interfaces of the devices according to the scheme. |
---|---|
Master | |
Slave |
...
Description | Analyze the routing table: after adding the IP addresses to the device's interfaces, the routing table was filled up with entries for every new connected network (mark marked as C). |
---|---|
Master | |
Slave |
Step 3
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 towards the PC and towards the Slave have been added to the Master's device routing 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: |
...
Description | Analyze the routing table: a static entry (marked with as S) has been added to the Slave's routing table. |
---|---|
Master | see step 2 |
Slave |
...
Description | If a default route has been added as in step 3a, a corresponding entry (marked with as S) will be added to the routing table. |
---|---|
Master | see step 2 |
Slave |
...
Let's look at the task of performing the routing configuration for the data traffic using a PtP scheme (Figure 2). For this task, the connectivity between the PC-1 and the PC-2 devices should be established using routing, as PC-1 and PC-2 belong to different subnets.
Center |
---|
Figure 2 - Scheme of Routing configuration for the data traffic routing configuration for using the InfiLINK 2x2 / , InfiMAN 2x2 families , InfiLINK Evolution, InfiMAN Evolution families of devices |
Let's look at the step-by-step configuration of the Master and Slave devices using the Web interface:
...
Description | Analyze the routing table: after adding IP addresses to the devices' interfaces, the routing tables were filled up with entries specifying the directly connected networks (markmarked as C). |
---|---|
Master | |
Slave |
Step 3
Description | Add static routes for the connection between PC-1 and PC-2. There is no route towards the PC-2's subnet on the Master device, and no route towards the PC-1's subnet on the Slave. Let's add these routes. |
---|---|
Master | |
Slave |
...
Description | Analyze the routing table: a static entry (marked with as S) has been added to the routing tables of the Master 's and to the Slave 's devices routing tables. |
---|---|
Master | |
Slave |
Step 4a
Description | If a default route has been added in step 3a, a corresponding entry (marked with as S) will be added to the routing tables. |
---|---|
Master | |
Slave |
...
Tip | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
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 connectivity 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 Routing configuration for the data traffic routing configuration for InfiLINK using the InfiMAN 2x2, InfiMAN 2x2 families Evolution families of devices |
Let's look at the step-by-step configuration of the wireless devices using the Web interface:
...
Description | Add the IP addresses to the devices interfaces in accordance with interfaces of the devices according to the scheme. |
---|---|
BS | |
CPE2 | |
CPE3 | |
CPE4 |
...
Description | Analyze 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 stationsubscriber, havinng no common point. |
---|---|
BS | - |
CPE2 | |
CPE3 | |
CPE4 |
Step 4
Description | Analyze the routing table: three static entries (flag S) have been added to the routing table of each device. |
---|---|
BS | |
CPE2 | |
CPE3 | |
CPE4 |
...
Description | If a default route was added in step 3a, a corresponding entry (flag S) will be added to the routing table. |
---|---|
BS | Changes are not required on the BS. |
CPE2 | |
CPE3 | |
CPE4 |
Step 5
Description | The 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 organizedestablished. |
---|
Tip | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
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 |
---|
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 | |
Slave |
...
Description | Analyze the routing table: after adding IP addresses to the device's interfaces, the routing table was filled up with entries about specifying the directly connected networks (mark flag C). |
---|---|
Master | |
Slave |
Step 3
Description | Add static routes for establishing the communication between the PC and the Slave device connectivitydevices. | |
---|---|---|
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 during the previous steps using the directly connected networks (see step 2), so there is no need to add static entries. | Slavestatic entries. |
Slave | Configure a static route on the Slave device towards the PC's network: |
Step 3a
Description | A default route can be configured on the slave device instead of a route to towards the PC's network. |
---|---|
Master | Changes are not required. |
Slave |
...
Description | Analyze the routing table: a static entry (mark flag S) has been added to the Slave's routing table. |
---|---|
Master | See step 2 |
Slave |
...
Description | If a default route has been added in step 3a, a corresponding entry (mark flag S) will be added to the routing table. |
---|---|
Master | See step 2 |
Slave |
...
Description | The task has been solved: an engineer working at on the PC has access to the Slave's device management interface. |
---|
Tip | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
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 |
---|
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 devices interfaces in accordance with interfaces of the devices 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 | |
Slave |
...
Description | Analyze the routing table: after adding IP addresses to the device's interfaces, the routing table was filled up with entries about 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 device connectivitydevices. The Quanta 5 5, Quanta 6 and the Quanta 70 families of devices allows allow to set configure only the default route only. |
---|---|
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 (see step 2), so there is no need to add static entries. |
Slave |
...
Description | Analyze the routing table: a static entry (mark flag S) has been added to the Slave's routing table. |
---|---|
Master | See step 2 |
Slave |
...
Description | The task has been solved: an engineer working at on the PC has access to the Slave's device management interface. |
---|
Tip | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
Tip | ||
---|---|---|
| ||
The article continuecontinues with: Dynamic routing. |
Additional materials
Online courses
- Quanta 5 / Quanta 6: Installation and Configuration.
- InfiLINK XG Family Product.
- InfiLINK 2x2 / InfiMAN 2x2: Initial Link Configuration and Installation.
...
Other
- Quanta 5 / Quanta 6 device configuration.
- InfiLINK XG, InfiLINK XG 1000 devices configuration.
Network configuration via Web interface for InfiLINK 2x2, InfiMAN 2x2 families devices.
- Network configuration via Web interface for InfiLINK Evolution, InfiMAN Evolution families devices.
- ifconfig command (interfaces configuration)
- route command (static routes configuration)