Solstice X.25 9.2 Administration Guide

Checking the Local Routing Tables

Use the netstat -r command to display the local routing tables:


hostname# netstat -r 

The routing table looks like this:


Routing tables
 Destination     Gateway     Flags     Refcnt     Use      Interface
 host_a          sun-bb      UGH       0          0        ie1
 host_b          sun-bb      UGH       0          0        ie1
 gateway_b       gateway_a   UGH       1          12897    ixe0
 route7          route7      UGH       0          0        ie0
 eastgate        route71     UGH       0          158      ie0
 backbone        alpha-bb    U         1          16087    ie1
 dresdenpc       route1      UG        0          0        ie1
 loopback        localhost   U         2          113436   lo0
 beta-bb         alpha       U         4063       146044   ie0
 dallas2         route7      UG        0          0        ie0
 trainingpc      route62     UG        0          0        ie1 

Make sure there is a routing table entry for each possible destination network. In particular, Solstice X.25 devices, listed under Interface, should be matched with the appropriate host names listed under Gateway. The Gateway entry should, in turn, be matched with the correct entry under Destination.

If there is not a routing table entry for each possible destination network, and you are using static routing, add the appropriate static routes. If you are using dynamic routing with in.routed, do the following:

  1. Check that in.routed is running by typing:


    # ps -ef | grep route
      root  process_id 1 80 Feb 22  1:55 /usr/sbin/in.routed -q

    If the routing tables still are not correct, become superuser, and continue with the next steps.

  2. Kill in.routed and flush the routing tables:


    #kill -9 process_id 
    #/usr/sbin route -f
    

    where process_ID is the process ID displayed by the ps -ef command.

  3. Restart in.routed as follows:


    #/usr/sbin/in.routed