Note that the router may also communicate with devices in a “public” IP network, as defined in the
command “set ip lan <ip_addr> <netMask>”.
When you modify the private IP network, related routes in the IP Routing Table and all entries in the
Static DHCP table and the Network Address Translation table which conflict with the new address
space will be deleted. You will receive a warning message asking if you would like this to be done.
Example:
Router> set ip private 10.0.1.168 255.255.255.0
set ip rip [Interface Name] <disabled/passive/active> <rip1/rip2>
Description: This command sets the IP RIP state to the disabled mode, passive mode or active mode.
When in the passive mode, the router will receive RIP broadcast data from other routers (but not
transmit); when in active mode, it will receive RIP broadcast data from other routers, and also
broadcast the routing table and routing table updates as necessary. When “Interface Name” is omitted,
the command applies to the entire system. The default mode is Active.
One common way of configuring routers for a central site and a remote (relatively small) site network
is as follows: assume the local site is a small branch network, which is connected to a central site,
through which many other networks can be reached. Instead of allowing both routers to turn on RIP, a
better way is to turn on RIP for the branch, but set the central site to be in the passive mode only.
Thus, the central site will not send its routing table to the branch router, but the branch site will send
the routing table and updates to the central site. Additionally, on the branch router, the user should set
the default route to the WAN connection that leads to the central site.
Now, from the central site’s point of view, since it still sees all networks at the branch site, it has no
problem routing any packet to the remote site. On the other hand, from the remote site’s perspective,
whenever a packet is to be routed, the remote site router will apply the standard routing algorithm to
the packet and, if no route can be found, the packet will just be passed on to the central site for
resolution. The idea is that the central site has the complete routing table, and thus “should” know how
to route the packet. With that assumption, the branch router is relieved of the burden of having to
receive routing table updates from the central site (which, in case of a large network, could be a huge
routing table containing hundreds or thousands of routing entries).
RIP, version 1 (or RIP1) transmits its routing table without subnet or next hop information, while RIP,
version 2 (or RIP2) includes this information. These two versions are not compatible and RIP2 should
only be specified when communicating to other RIP2 routers.
set ip <Profile Name> set ip <Profile Name> < local-ipAddr> <netMask> <remote-ipAddr>
Description: This command enables IP routing over the connection specified by Profile Name.
Additionally, a WAN connection that supports IP routing, may, either be assigned zero or two IP
addresses. If none are assigned, the connection is termed unnumbered, a popular feature available in
newer routers (since the connection does not consume IP addresses). Numbered connections are
assigned two addresses, one at each end of the connection (complete with the network mask).
Example 1: