Reference ManualThe Routing Information Protocol can be quite useful on private LANs which consist of multiple subnets interconnected by gateways. For example, consider a gateway which connects subnet 172.16.2.0 and subnet 172.16.3.0. The machines on each subnet will not know how to reach the machines on the other subnet, unless a network-specific route is added to each machine on each subnet. This is tedious and error-prone, so running RIP on the gateway will be of benefit. Of course, a RIP listener will be required on each machine, but most Operating Systems such as Windows (except Windows 95), Unix, and Linux have built-in RIP support, although it must usually be explicitly enabled. NAT32 fully supports RIP, and it is enabled by issuing the command:
start rip
The NAT32 RIP implementation can be configured to not propagate or accept RIP updates on a specific interface, so it is quite safe to use in an Internet Connection Sharing environment. To disable RIP on an interface, enter the following command:
setr ifn off
where "ifn" indicates the desired Interface. The value "p" can be used to specify the Primary (i.e. the Internet connected) interface, and the value "s" can be used to specify the current Secondary (i.e. the private LAN) interface. The second argument can also be "on", if you wish to enable RIP on an interface. The default setting is to allow RIP (if it has been started) on ALL interfaces.
All versions of Windows NT4 (SP4 and later) and 2000 support a RIP Listener (sometimes called "Silent RIP"), which is enabled as follows:
To force NAT32 to broadcast a RIP update within the next 5 seconds, simply enter the command rip from the NAT32 Console.
Internet Connection Sharing Modules Multiple Subnets