Page tree

Versions Compared

Key

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

...

  • wireless links are established between the BS1, CPE2 and CPE3 devices. BS1 is configured as Master and CPE2, CPE3 - as Slaves;
  • each wireless device is connected to a wired network segment and each segment uses its own IP addressing;
  • router R1 is also connected to LAN-3, as well as to the LAN-6, LAN-7, LAN-8 networks;
  • it is necessary to establish connectivity between all the networks by configuring the ODR protocol on the BS1, CPE2 and CPE3 wireless devices.
Center

Image RemovedImage Added

Figure 1 - ODR configuration scheme

...

The ODR configuration will be performed via CLI and after each step, the routing information will be displayed for analysis.

Note
titleNOTE

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.

Pre-configuration

DescriptionPerform the pre-configuration of the devices: establish the wireless connections.

BS1

Code Block
languagetext
themeEmacs
Set IP addresses
ifc eth0 10.10.10.1/24
ifc rf5.0 172.16.0.1/29

Disable switching
switch stop

Establish the radio link
rf rf5.0 band 20
rf rf5.0 freq 5000

mint rf5.0 -name "BS_1"
mint rf5.0 -type master
CPE2
Code Block
languagetext
themeEmacs
Set IP addresses
ifc eth0 10.10.20.2/24
ifc rf5.0 172.16.0.2/29

Disable switching
switch stop

Establish the radio link
mint rf5.0 -name "CPE_2"
mint rf5.0 -type slave
mint rf5.0 prof 1 -band 20 -freq 5000 -type slave

CPE3

Code Block
languagetext
themeEmacs
Set IP addresses
ifc eth0 10.10.30.3/24
ifc rf5.0 172.16.0.3/29

Disable switching
switch stop

Establish the radio link
mint rf5.0 -name "CPE_3"
mint rf5.0 -type slave
mint rf5.0 prof 1 -band 20 -freq 5000 -type slave

Description

Analyze the routing table on each device. There are two entries added in the routing table, one for each directly connected networks associated with the eth0 and rf5.0 radio interfaces.

BS1

Code Block
languagetext
themeEmacs
BS_1#1> netstat -r
Routing tables
Destination        Gateway            Flags     Refs     Use  Interface
10.10.10.0/24      link#2             UC          0        0  eth0
127.0.0.1          127.0.0.1          UH          1      473  lo0
172.16.0.0/29      link#3             UC          0        0  rf5.0
224.0.0.0/8        127.0.0.1          UGS         0    15780  lo0

CPE2

Code Block
languagetext
themeEmacs
CPE_2#2> netstat -r
Routing tables
Destination        Gateway            Flags     Refs     Use  Interface
10.10.20.0/24      link#2             UC          0        0  eth0
127.0.0.1          127.0.0.1          UH          1      432  lo0
172.16.0.0/29      link#3             UC          0        0  rf5.0
224.0.0.0/8        127.0.0.1          UGS         0    18457  lo0⁣

CPE3

Code Block
languagetext
themeEmacs
CPE_3#1> netstat -r
Routing tables
Destination        Gateway            Flags     Refs     Use  Interface
10.10.30.0/24      link#2             UC          0        0  eth0
127.0.0.1          127.0.0.1          UH          1      560  lo0
172.16.0.0/29      link#3             UC          0        0  rf5.0
224.0.0.0/8        127.0.0.1          UGS         0    10686  lo0

...

Description

Analyze the information about the ODR's protocol operation:

  • BS1: there are two subscriber devices, CPE2 and CPE3 added in the spoke devices list. The device does not export any routes, because it has the hub role.
  • CPE2: BS1 has been added to the list of devices having the hub role, while there is no list of spoke devices. The device exports a route to the 10.10.20.0/24 network, but does not export the 172.16.0.0/29 network, because the ODR protocol is running on the rf5.0 radio interface, which is associated with the 172.16.0.0/29 network.
  • CPE3: the same as for CPE2.
BS1
Code Block
languagetext
themeEmacs
BS_1#1> mint rf5.0 -odr show
  rf5.0: ODR state - HUB
  List of active Spokes:
    00043513724E "AS_3"
      10.10.30.3/24
    000435109CC0 "AS_2"
      10.10.20.2/24
  Total Spokes: 2
CPE2
Code Block
languagetext
themeEmacs
CPE_2#2> mint rf5.0 -odr show
  rf5.0: ODR state - SPOKE
  Preffered HUB: 00043510E5B9 "BS_1"
  List of HUBs:
  00043510E5B9 "BS_1", cost 51, hops 1

  Exported routes:
  10.10.20.2/24
CPE3
Code Block
languagetext
themeEmacs
CPE_3#1> mint rf5.0 -odr show
  rf5.0: ODR state - SPOKE
  Preffered HUB: 00043510E5B9 "BS_1"
  List of HUBs:
  00043510E5B9 "BS_1", cost 51, hops 1

  Exported routes:
  10.10.30.3/24

...

In order to transmit the routing information about LAN-6, LAN-7 and LAN-8 to all the wireless devices, it is necessary to export the static records to ODR.  This This operation can be performed using CPE3's configuration, since the routing table of this device contains the static entries and the rf5.0 radio interface supports ODR.

DescriptionExport the static routes to ODR.
BS1Changes are not required.
CPE2Changes are not required.
CPE3
Code Block
languagetext
themeEmacs
mint rf5.0 -odr spoke kernel

...

  1. Network configuration via web interface for InfiLINK 2x2, InfiMAN 2x2.

  2. Network configuration via Web interface for InfiLINK Evolution, InfiMAN Evolution families devices.
  3. Ifconfig command (interfaces configuration)
  4. route command (static routes configuration)
  5. mint command (MINT version)
  6. mint command (TDMA version)