That's interesting.

My boxes do not have /etc/defaultrouter. They do have two Ethernet ports
(the one for Nodebus and one for the Plant network) and in.routed is NOT
running.

Like I said, I've never tried /etc/defaultrouter because I was told long ago
that in.routed would startup.


I just took a look at one of my boxes. The /etc/rc2.d/S69inet startup script
has the lines that start in.routed commented out. We (Foxboro) must do this
as one of our configuration changes.

The lines that issue a /usr/sbin/route command are retained.

So, on an I/A Series AW/AP/WP, using /etc/defaultrouter does no harm.

Just be careful that you never start in.routed.


Regards,

Alex Johnson
The Foxboro Company
10707 Haddington
Houston, TX 77043
713.722.2859 (v)
713.722.2700 (sb)
713.932.0222 (f)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 


        -----Original Message-----
        From:   John Metsker [SMTP:[EMAIL PROTECTED]]
        Sent:   Thursday, June 01, 2000 5:58 PM
        To:     'Foxboro DCS Mail List'
        Subject:        RE: Ethernet Networking Question

        Alex, 

        It is one of those rare times, but I believe you need to be
corrected.  Solaris will start in.routed and act like a router only when
multiple interfaces (le?, hme?, whatever) are defined and /etc/defaultrouter
does NOT exist.

        If /etc/defaultrouter exists, a Solaris box will always send I.P.
packets to the "default route" device whenever it is trying to communicate
to devices on segments not directly connected to it.

        I never do it myself or recommend to others using anything but the
standard Sun supplied mechanisms to configure any part of I.P. networking
for additional interfaces on a machine.

        John Metsker 
        General Mills, Inc   

        -----Original Message----- 
        From: Johnson,Alex [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ] 
        Sent: Thursday, June 01, 2000 4:38 PM 
        To: Foxboro DCS Mail List 
        Subject: RE: Ethernet Networking Question 


        The problem with defaultrouter that it supposedly starts the Solaris
routing 
        software too. This is a bad thing since it would "publish" the
Nodebus IP 
        addresses. 

        I can't say that I've tested that myself, but if someone (Darryl?)
is using 
        it do a ps -ef | grep in.routed and see if it is running. If it is,
you 
        could be publishing a bunch of IP addresses that are not unique. 


        Regards, 

        Alex Johnson 
        The Foxboro Company 
        10707 Haddington 
        Houston, TX 77043 
        713.722.2859 (v) 
        713.722.2700 (sb) 
        713.932.0222 (f) 
        [EMAIL PROTECTED] < mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > 


                -----Original Message----- 
                From:   Darryl Bond [SMTP:[EMAIL PROTECTED]] 
                Sent:   Thursday, June 01, 2000 5:19 PM 
                To:     Foxboro DCS Mail List 
                Subject:        Re: Ethernet Networking Question 

                "Loupe, Rory" wrote: 
                > 
                > You need to add the router as the default gateway.  First
enter 
        "route add 
                > default 112.113.1.1", next edit /etc/fox/rc.foxapps and
add "route 
        add 
                > default 112.113.1.1" to the file. 
                > 
                > Rory Loupe 

                The Sun way is to add the entry for the router in /etc/hosts

                112.113.1.1 router 

                Then create a file called /etc/defaultrouter with the word
'router' 
        in 
                it. 

                echo router >/etc/defaultrouter 

                When Solaris boots it will configure the default router for
you. 

                Darryl Bond 
                NRG Gladstone 

                
        

-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Reply via email to