I'm still having problems with my Solaris 2.5.1 system, but I certainly got
my questions answered about routing. Thanks to everyone who replied. It was
a LONG list.
I think that the heart of the problem is that there are problems with our
Xylan switch. My 2.5.1 system worked for about 5 minutes earlier today, but
has stopped working again. A netstat -rn shows that it has the correct
default router defined, and it has the same default router as the system
that's working.
As for my original question about how routes get defined (assuming I am
summarizing correctly), at boot time, " ... /etc/defaultrouter is ment to do
exactly that: adds default route to the routing table while going through the
boot sequence (it is the one marked with "G" for gateway in the netstat -rn
command output). This default route will enable the box to talk to any IP
nodes which are not on the local subnet. This file is consulted in the
"single user mode" part of boot sequence. Go to /etc/rcS.d and execute 'grep
defaultrouter *'. This will enlighten you how it is being used." The quote
was from Greg Sawicki.
And, according to Raymond Wong, "Both 2.5.1 and 2.6 go through pretty much
the same process for determining route. They check for /etc/defaultrouter,
or check for some existing default route setting (i.e. a manual route command
has already been run in the script) If they don't find those, they try
running router discovery (in.rdisc), and if that doesn't work they run routed
(in.routed) to listen for continuuing RIP."
I think the network people are tinkering with our switch even as I write
this. I'll keep my fingers crossed ...
Rodney
-----Original Message-----
From: Rodney Wines <Rodney.Wines@ahqps.alcatel.fr>
To: Sun Managers List <sun-managers@sunmanagers.ececs.uc.edu>
Date: Sunday, February 14, 1999 11:18 PM
Subject: Router Question
>I've got two systems, one running Solaris 2.5.1, and the other Solaris 2.6.
>The systems are sitting side by side on the same network segment. Both
>systems USED to work fine. However, we have had some network problems
>recently. The 2.6 system is working fine, and a "netstat -r" shows it using
>the proper router. The 2.5.1 system cannot talk to any system that isn't on
>its network segment. An ifconfig -a shows that both systems have the same
>broadcast and subnet masks.
>
>I tried a sys-unconfig on the misbehaving 2.5.1 system, but I wasn't
prompted
>for a router when the system booted. I created a /etc/defaultrouter file,
>and added the correct router, and the system works sort of. However, the
2.6
>system doesn't have this file, and I never needed it before.
>
>How is my router being defined, and does anybody have any suggestions for
>places I can look to discover why I suddenly need a /etc/defaultrouter file?
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:15 CDT