User's Manual Part 3

〓MSR Series Quick Start Guide, AOS-v2.0〓

If NAT is disabled on the portal router, more configurations are needed for the wired-

network router (hereby referred to as the LAN router) to which the portal router is

connected. The configuration requires extensive knowledge of network routing and is

not recommended for novice users. Therefore, disabling NAT is only recommended for

advanced network administrators who need a finer control of their network topology.

To allow in-bound and out-bound traffic to properly flow between the portal node and the

LAN router, the routing table on the LAN router must contain all routes known by the

portal node. This information can be obtained via the “show ip route” command on the

portal node.

After initial configuration and reboot of the portal node, allow a few minutes for the node

to learn the routes to all the nodes within the network. Then log into the CLI’s EXEC

privilege mode of the router and enter “show ip route”

Sample result of “show ip route”

MSR2000_1# show ip route

Codes: K - kernel route, C - connected, S - static, H - host,

A - AWR, > - selected route, * - FIB route

S>* 0.0.0.0/0 [1/0] via 192.168.0.1, fast-ethernet 0

H 192.168.10.1/32 [0/0] is directly connected, lo:2

C>* 192.168.10.1/32 is directly connected, lo:2

C>* 172.16.1.0/24 is directly connected, Dot11Radio0

H>* 172.16.1.1/32 [0/0] is directly connected, Dot11Radio0

C>* 200.1.2.0/24 is directly connected, Radio1AWds0

H>* 200.1.2.1/32 [0/0] is directly connected, Radio1AWds0

C>* 200.1.3.0/24 is directly connected, Radio1AWds1

H>* 200.1.3.1/32 [0/0] is directly connected, Radio1AWds1

C>* 192.168.1.0/24 is directly connected, fast-ethernet 0

H>* 192.168.1.1/32 [0/0] is directly connected, fast-ethernet 0

Other than the default route, all the other routes should be added to the routing table of

the LAN router via its own CLI or some other configuration interface.

Manual Link Configuration

The setup described in the previous sections relies on MSR series’ radio management

intelligence to automatically discover other nodes and form the mesh network. While

this feature reduces the amount of work to set up a mesh network, it prevents users from

controlling the configuration of the backhaul wireless links. In addition, automatic mesh-

forming cannot guarantee full mesh connectivity or stable convergence. To solve this

problem, it is recommended for one to set up the backhaul links manually using the

instructions in this appendix.