Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: nuchat!steve@uunet.uu.net (Steve Nuchia)
Newsgroups: comp.sys.sun
Subject: Re: Ethernet address of second board on Sun
Keywords: Hardware
Message-ID: <7359@nuchat.UUCP>
Date: 8 May 89 13:16:13 GMT
References: <8904071527.AA02511@shire.cs.psu.edu>
Sender: usenet@rice.edu
Organization: Houston Public Access
Lines: 26
Approved: Sun-Spots@rice.edu
Original-Date: 28 Apr 89 16:54:44 GMT
X-Sun-Spots-Digest: Volume 7, Issue 274, message 2 of 12

ehrlich@shire.cs.psu.edu (Daniel R. Ehrlich) writes:
>Try this one.  We have a single coax on which we run two different class B
>networks, 128.118 and 130.203.  As far as I know this is perfectly OK.
>Here is were the trouble starts.  Assume I have a Sun with three ethernet
>interfaces that I would like to use as a gateway between the two class B
>nets (remember these are both on the same physical wire) and a third class

There is an undocumented ifconfig option that overrides the ethernet
address of the interface.  Sun uses this in their Sunlink DNI (DECnet
compatiblity software) product.  My guess is you can use it to make the
boards have whatever address you want.  Choosing a good address is left as
an excersize. :-)

The only documentation I've seen is in the installation scripts for DNI,
and all that stuff is at a client site that I can't get to anytime soon,
but the hint should help.

Suggest you get your Sun contact to dig up the details for you.  Another
thing to check is to see if you can find where they are setting the
addresses.  I'd guess that the boards have unique addresses burned into
them and they are having the default address loaded into them in one of
the boot scripts.

Steve Nuchia	      South Coast Computing Services
uunet!nuchat!steve    POB 890952  Houston, Texas  77289
(713) 964 2462	      Consultation & Systems, Support for PD Software.