[comp.sys.proteon] Proteon not accepting static routes

RUBIN@GRAF.POLY.EDU (David Rubin) (08/30/90)

I came across a problem with our P4200 that I did not realize before.
When I define a static route to a network, it seems that the Proteon is
not listening to it.  I needed to turn on RIP in order to get things
to work correctly, which I'd rather not do since we have a small network
and static routes would be more efficient.

Scenario: Router interface is 128.238.6.10.  Unix host at 128.238.6.5 is
acting as a gateway to a local network: 191.238.65.0  (this strange
address is required due to subnetting limitations on the Unix host).
I have set a static route in the proteon for 191.238.65.0, first hop
128.238.6.5, cost 1.

When I go to Process 5, IP, and ask for the route to 191.238.65.5,
response is "No net route, using default", and packets are sent to our
default Nysernet gateway.  When I Enable Receiving RIP for this
interface, the Unix host's routed successfuly provides the Proteon with
the RIP information, and things work as desired.

Am I missing something? Is there something else I must do to get the static
route to work so I can turn off RIP?  We are using software Rev. 8.1a.

David Rubin                        |     INTERNET: RUBIN@graf.poly.edu
Polytechnic University             |       BITNET: RUBIN@POLYGRAF
Brooklyn, NY                       |

bambi@kirk.nmg.bu.oz (David J. Hughes) (09/01/90)

From article <9008301627.AA18437@devvax.TN.CORNELL.EDU>, by RUBIN@GRAF.POLY.EDU (David Rubin):
> I came across a problem with our P4200 that I did not realize before.
> When I define a static route to a network, it seems that the Proteon is
> not listening to it.  I needed to turn on RIP in order to get things
> to work correctly, which I'd rather not do since we have a small network
> and static routes would be more efficient.

We do not run RIP, EGP or ARP Subnet routing on our p4200's.  All
internal routes are statically defined.  We have no problem with using
the static routes internally.  Our situation does differ from yours as
we are not yet connected to the Internet (AARNet in Australia) so we
don't have a default/external gateway defined.  Dumping the route table
on one of the p4200's gives :-

IP>dump

Type   Dest net         Cost Age  Next hop          Exchange Tables
                                                      Out     In

Sbnt   131.244.0.0      1    3    None                  .      .
 Dir   131.244.13.0     1    0    131.244.13.254        .      .
 Dir   131.244.1.0      1    0    131.244.1.254         .      .
 Dir   192.48.109.0     1    0    192.48.109.254        .      .
 Dir   131.244.254.0    1    0    131.244.254.1         .      .
Stat*  131.244.7.0      2    0    131.244.254.2         .      .
Stat*  131.244.8.0      2    0    131.244.254.2         .      .
Stat*  131.245.0.0      2    0    131.244.254.4         .      .
Stat*  131.244.14.0     2    0    131.244.254.3         .      .
Stat*  131.244.15.0     2    0    131.244.254.3         .      .
Stat*  131.244.23.0     2    0    131.244.254.5         .      .
Stat*  131.244.22.0     2    0    131.244.254.5         .      .
Stat*  131.244.40.0     2    0    131.244.254.6         .      .
Stat*  131.244.41.0     2    0    131.244.254.6         .      .


Notice that any network that is not directly connected to the box is
statically defined.

As I have said, we have no problems with routing internally.  We are
running version 8.1 of the C Gateway code.


David
+----------------------------------------------------------------------------+
| David J. Hughes   (AKA bambi)	 |   bambi@kowande.bu.oz.au                  |
| Systems Programmer		 |   bambi@kowande.bu.oz.au@uunet.uu.net     |
| Network Management Group       |   ..!uunet!munnari!kowande.bu.oz.au!bambi |
| Bond University, Gold Coast    |   Phone : +61 75 951111                   |
| Queensland,  Australia  4229   |   Fax :   +61 75 951456                   |
+----------------------------------------------------------------------------+