Article View: comp.protocols.appletalk
Article #5391Re: Re-assigning node numbers?
From: Richard Silverman
Date: Sat, 21 Jan 1989 02:46
Date: Sat, 21 Jan 1989 02:46
19 lines
1539 bytes
1539 bytes
Scanner,
When the Mac boots, it attempts to open the ATP drivers. If it's
connected to an AppleTalk network, it will pick a node number and use a LAP
control packet to determine whether it is unique (other nodes will respond
if it is not). It then stores that node ID in parameter RAM, and uses it
as the first node ID to try the next time the drivers open. This way, node
IDs tend to remain stable. The only way it should change while it's still
on is if the ATP drivers are closed and then reopened, and in the mean time
someone else (presumable a device brand new to this network) has been connected
and claimed that ID -- unlikely situation. Of course, if you have a device
that's misbehaving by not reusing it's old node ID, or perhaps not obeying
the LAP control protocol, then you could have problems.
Richard Silverman
arpa: rsilverman@eagle.wesleyan.edu Wesleyan University
bitnet: rsilverman@wesleyan Middletown, CT
CIS: [72727,453] 06457
Technical Details
Message-ID:
<Added.gXpyIzy00Ui3MXcU9b@andrew.cmu.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!EAGLE.WESLEYAN.EDU!RSILVERMANShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!EAGLE.WESLEYAN.EDU!RSILVERMAN From: RSILVERMAN@EAGLE.WESLEYAN.EDU (Richard Silverman) Newsgroups: comp.protocols.appletalk Subject: Re: Re-assigning node numbers? Message-ID: <Added.gXpyIzy00Ui3MXcU9b@andrew.cmu.edu> Date: 21 Jan 89 02:46:32 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 19 X-Unparsable-Date: 20-JAN-1989 20:52:22.32