...
This part of the article contains routing configuration scenarios for various tasks. In order to focus on the article 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 each endpoint devices add adds a default route to the its routing table;
- switching is off on the devices of of the InfiLINK 2x2 , and InfiMAN 2x2 families;
- at in the examples for the InfiLINK 2x2 , and InfiMAN 2x2 family 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 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, while the PC and the Slave devices belong to different subnets.
| Center |
|---|
Figure 1 - Scheme of the management traffic routing configuration for the InfiLINK 2x2 , / InfiMAN 2x2 families of devices |
Let's perform a step by step configuration of for the Master and the Slave devices using the Web interface:
...
| Description | Add the IP addresses to device interfaces in accordance with 's interfaces according to the scheme. |
|---|---|
| Master |
|
| Slave |
|
Step 2
| Description | Analyze the routing table: after adding the IP addresses to the device's interfaces, the routing table was filled up with entries about for every new connected networks network (mark 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 to towards the PC and to 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:
|
Step 3a
| Description | A default route can be configured on the Slave device instead of a route to the PC network. |
|---|---|
| Master | No changes required. |
| Slave | the Slave device instead of a static route towards the PC's network. |
| Master | 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:
|
Step 4
| Description | Analyze the routing table: a static entry (mark marked with 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 (mark marked with S) will be added to the routing table. |
|---|---|
| Master | see step 2 |
| Slave |
|
Step 5
| Description | Problem has been solvedTask accomplished: an engineer working on a the PC has access to the management interface of the Slave device. |
|---|
| Tip | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...