Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!sdd.hp.com!uakari.primate.wisc.edu!ames!mindcraft.com!karish
From: karish@mindcraft.com (Chuck Karish)
Newsgroups: comp.unix.aix
Subject: Re: strange tcpip problem:  SOLVED!!
Summary: Network adapter ID
Message-ID: <676836895.5438@mindcraft.com>
Date: 13 Jun 91 18:14:54 GMT
References: <1991Jun12.230426.22643@milton.u.washington.edu> <843@rufus.UUCP>
Organization: Mindcraft, Inc.
Lines: 21

In article <843@rufus.UUCP> drake@drake.almaden.ibm.com writes:
|In article <1991Jun12.230426.22643@milton.u.washington.edu>
|eliot@engr.washington.edu (Eliot Lim) writes:
||I don't know if this is a bug or a feature, but if you move your ethernet
||card, the OS will assign it a new hardware address and leave the old one
||and treat it as a device that has gone offline.  
|
|Feature.  How else could it work?  Consider a scenario ...
|
|Now, when the machine comes up, I really want it to remember that the
|slot 4 Ethernet card is on network B, not go playing guessing games.
|Any method that didn't make the adapter definitions slot dependent
|would cause icky problems in such scenarios...
|
|How do other systems handle this?

Record the cards' Ethernet ID numbers, and query them at boot time?
-- 

	Chuck Karish		karish@mindcraft.com
	Mindcraft, Inc.		(415) 323-9000