Path: utzoo!attcan!uunet!lll-winken!rogue.llnl.gov!oberman
From: oberman@rogue.llnl.gov
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Reply to Re: Ethernet Address Uniqueness...
Message-ID: <1990Oct16.093137.1@rogue.llnl.gov>
Date: 16 Oct 90 16:31:37 GMT
References: <9010092346.AA29384@ftp.com>
Sender: usenet@lll-winken.LLNL.GOV
Lines: 18

In article <9010092346.AA29384@ftp.com>, jbvb@FTP.COM (James B. Van Bokkelen) writes:
> This is a standard gotcha of using protocols that change the address.
> There is no solution other than to make sure that DECNet is always
> started before anything else that cares about the Ethernet address.
 
This is getting a bit far afield from tcp-ip, but the above is not quite true.
By setting the SYSGEN value for SCSSYSTEMID to the value ((DECnet area*1024) +
node), the order in which products are started in no longer significant as the
MAC address of the Ethernet cards is rewritten before any layered software is
run. 48.168 would yield an SCSSYSTEMID of 49320, (48*1024)+168.

					R. Kevin Oberman
					Lawrence Livermore National Laboratory
					Internet: oberman@icdc.llnl.gov
   					(415) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything.