Page tree

Versions Compared

Key

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

...

Mode nameDescription
Basic

The basic RIP mode is used to analyze the output of the diagnostic commands and to switch to the configuration mode.

The switching to the basic mode is performed from the WANFleX command shell using the "arip" command.

Code Block
languagetext
themeEmacs
BS_1#1> arip
RIP>
RIP configuration

The configuration mode allows to manage the RIP service running on the device and proceed to the configuration modes: router, interfaces or route-maps.

The switching to the RIP configuration mode is performed from the basic mode using the "config" command.

Code Block
languagetext
themeEmacs
RIP> config
RIP(config)#
RIP router configuration

In the router configuration mode, basic RIPF settings can be made. The mode allows to configure the announced networks, router ID, etc.

Switching The switching to the RIP router configuration mode is performed from the configuration mode using the "router" command.

Code Block
languagetext
themeEmacs
RIP(config)# router
RIP(config-router)# 
RIP interface configuration

The RIP interface configuration mode allows to configure the protocol settings related to a specific interface.

The switching to the RIP interface configuration mode is performed from the configuration mode using the "interface IFNAME" command.

Code Block
languagetext
themeEmacs
RIP(config)# interface rf5.0
RIP(config-if)#
Route-maps configuration

The route-maps configuration mode allows to configure the rules that should be applied to the advertised or received RIP routes.

The switching to the RIP route-map configuration mode is performed from the configuration mode using the rule creation command "route-map WORD (deny|permit) <1-65535>".

Code Block
languagetext
themeEmacs
RIP(config)# route-map MAP permit 10
RIP(config-route-map)#

...

The devices will be configured step-by-step. In addition to the RIP configuration, static routing routes will be used (see Static routing) for providing connectivity with LAN-6, LAN-7 and LAN-8.

...

Description

Perform a preliminary configuration of the devices, consisting of the following steps:

  • Configure the device IDIDs.
  • Remove the svi1 interface.
  • Assign IP addresses to the network interfaces, according to the scheme.
  • Add static entries to the routing table.
  • Disable switching.
  • Establish the wireless links.
BS1
Code Block
languagetext
themeEmacs
Set the device ID
system prompt BS_1

Remove the svi1 interface
ifc svi1 destroy

Assign IP addresses
ifc eth0 10.10.10.1/24
ifc rf5.0 172.16.0.1/29
ifc lo0 192.168.0.1/32

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 the device ID
system prompt CPE_2

Remove the svi1 interface
ifc svi1 destroy

Assign IP addresses
ifc eth0 10.10.20.2/24
ifc rf5.0 172.16.0.2/29
ifc lo0 192.168.0.2/32

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 the device ID
system prompt CPE_3

Remove the svi1 interface
ifc svi1 destroy

Assign IP addresses
ifc eth0 10.10.30.3/24
ifc rf5.0 172.16.0.3/29
ifc lo0 192.168.0.3/32

Add static routes
route add 192.168.5.0/28 10.10.30.1
route add 192.168.6.0/28 10.10.30.1

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

The routing tables of the wireless devices , contain entries about each subnet shown in the scheme. This means that the devices have successfully exchanged routing information and added it to the FIB.

Note that the routing tables contain also routes to the addresses assigned to the loopback interfaces of the other wireless devices. These interfaces have been added to RIP in various ways:

  • BS1: redistribution of a directly connected network;
  • CPE2: the device advertises all the networks to which it is connected because of the configuration of the 0.0.0.0/0 network;
  • CPE3: the network assigned to the loopback interface is explicitly announced.

Also pay attention to the default route on the CPE2 and CPE3 devices. According to the configuration, BS1 announces the default route to all the devices that support RIP, indicating itself as a gateway. At the same time, the default route is absent from the BS1's routing table.

The CPE3 router redistributes the static routes, therefore, the routing tables of BS1 and CPE2 contain paths towards the networks 192.168.6.0/24, 192.168.7.0/24 and 192.168.8.0/24.

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
10.10.20.0/24      172.16.0.2         UG3         0        0  rf5.0
10.10.30.0/24      172.16.0.3         UG3         0        0  rf5.0
127.0.0.1          127.0.0.1          UH          3      106  lo0
172.16.0.0/29      link#3             UC          0        0  rf5.0
192.168.0.1        192.168.0.1        UH          0        0  lo0
192.168.0.2        172.16.0.2         UGH3        0        0  rf5.0
192.168.0.3        172.16.0.3         UGH3        0        0  rf5.0
192.168.6.0/28     172.16.0.3         UG3         0        0  rf5.0
192.168.7.0/28     172.16.0.3         UG3         0        0  rf5.0
192.168.8.0/28     172.16.0.3         UG3         0        0  rf5.0
224.0.0.0/8        127.0.0.1          UGS         0      346  lo0
CPE2
Code Block
languagetext
themeEmacs
AS_2#1> netstat -r
Routing tables
Destination        Gateway            Flags     Refs     Use  Interface
default            172.16.0.1         UG3         0        0  rf5.0
10.10.10.0/24      172.16.0.1         UG3         0        0  rf5.0
10.10.20.0/24      link#2             UC          0        0  eth0
10.10.30.0/24      172.16.0.3         UG3         0        0  rf5.0
127.0.0.1          127.0.0.1          UH          3      100  lo0
172.16.0.0/29      link#3             UC          0        0  rf5.0
192.168.0.1        172.16.0.1         UGH3        0        0  rf5.0
192.168.0.2        192.168.0.2        UH          0        0  lo0
192.168.0.3        172.16.0.3         UGH3        0        0  rf5.0
192.168.6.0/28     172.16.0.3         UG3         0        0  rf5.0
192.168.7.0/28     172.16.0.3         UG3         0        0  rf5.0
192.168.8.0/28     172.16.0.3         UG3         0        0  rf5.0
224.0.0.0/8        127.0.0.1          UGS         0      703  lo0
CPE3
Code Block
languagetext
themeEmacs
AS_3#1> netstat -r
Routing tables
Destination        Gateway            Flags     Refs     Use  Interface
default            172.16.0.1         UG3         0        0  rf5.0
10.10.10.0/24      172.16.0.1         UG3         0        0  rf5.0
10.10.20.0/24      172.16.0.2         UG3         0        0  rf5.0
10.10.30.0/24      link#2             UC          0        0  eth0
127.0.0.1          127.0.0.1          UH          3       84  lo0
172.16.0.0/29      link#3             UC          0        0  rf5.0
192.168.0.1        172.16.0.1         UGH3        0        0  rf5.0
192.168.0.2        172.16.0.2         UGH3        0        0  rf5.0
192.168.0.3        192.168.0.3        UH          0        0  lo0
192.168.6.0/28     10.10.30.1         UGS         0        0  eth0
192.168.7.0/28     10.10.30.1         UGS         0        0  eth0
192.168.8.0/28     10.10.30.1         UGS         0        0  eth0
224.0.0.0/8        127.0.0.1          UGS         0      349  lo0

...