Configuration examples

The following example shows the contents of an NCPROUTE gateways data set containing multiple entries:

   options default.router no trace.level 4 supply on
   net testnet gateway 9.0.0.100 metric 1 passive
   net 2.0.0.2 gateway 9.0.0.101 metric 2 external
   host 2.0.0.3 gateway 9.0.0.102 metric 3 passive
   host 2.0.0.4 gateway 9.0.0.103 metric 2 external
   active active gateway 2.0.1.1 metric 1 active

In the second entry, the route indicates that NCPROUTE can reach network testnet through the gateway 9.0.0.100, and that it is one hop away. This passive route is not broadcast to other RIP routers.

In the third entry, the route indicates that NCPROUTE can reach network 2.0.0.2 through the gateway 9.0.0.101, and that it is two hops away. Because this route is external, NCPROUTE should not add routes for this network to the routing tables and routes received from other RIP routers for this network should not be accepted.

In the fourth entry, the route indicates that NCPROUTE can reach host 2.0.0.3 through gateway 9.0.0.102, and that it is one hop away. This passive route is not broadcast to other RIP routers.

In the fifth entry, the route indicates that NCPROUTE can reach host 2.0.0.4 through gateway 9.0.0.103, and that it is two hops away. Because this route is external, NCPROUTE should not add routes for this network to the routing tables, and routes received from other RIP routers for this network should not be accepted.

The sixth entry shows an active gateway. Note that it is specified as the last entry in the data set.

Note: If a default route is to be defined to a destination gateway or router, configure a default route in this gateways data set (if the default route is not defined in a NCP client's generation definition).