trouble with telnet

Jim Jagielski jim at jagubox.gsfc.nasa.gov
Wed May 29 21:21:34 AEST 1991


In article <PST.91May28163950 at ack.Berkeley.EDU> pst at okeeffe.Berkeley.EDU (Paul Traina) writes:
}It is useless to run in.routed if your routers do not generate RIP
}information.
}
}At Stanford (one of the sites Tony was mentioning), our routers will
}communicate with each other (not using RIP though), but each subnet
}only has one router, so people are instructed to just create a default
}route to their router.

Of course, this is correct and maybe I made my "use in.routed -q" statement
rather quickly. I did infer, however, that in the method I described, that
at least one machine on your net (a gateway) "handle" the routing, which
basically implies that it broadcast RIP (Routing Information Protocol) to
all the other machines which are running in.routed quietly and just listening
for info...    -whew-

When I used to use static routing, I added the required "route add" statement
in /etc/rc right after I mounted the file systems... this was needed since my
/usr partition was (and still is) a separate file system.
--
===========================================================================
#include <std/disclaimer.h>
                                 =:^)
           Jim Jagielski                    NASA/GSFC, Code 711.4
     jim at jagubox.gsfc.nasa.gov               Greenbelt, MD 20771

"If we increase the size of the penguin until it is the same height as a man
 and then compare the relative brain size, we know find that the penguin's
 brain is still smaller. But, and this is the point, it is larger than it WAS!"



More information about the Comp.unix.aux mailing list