SYSTEM@CRNLNS.BITNET (08/11/87)
Ken, In message <12325520704.139.SY.KEN@CU20B.COLUMBIA.EDU> you commented: >I'm afraid I fail to see where you get AA-00-03-01-10-E7 from 19.53. >... >or, node 57.784. Well, I'm afraid I didn't get it: DECnet did. I guess it doesn't use your algorithm. Herewith the Ethernet address used by the same node with the same hardware interface after I changed its address to be 43.298 = 44330 decimal (1024*43+298). (We are in the process of vacating area 19 so someone else can use it.) The following report was generated by the command "MCR NCP SHOW KNOWN LINE CHARACTERISTICS" Known Line Volatile Characteristics as of 11-AUG-1987 08:38:42 Line = UNA-0 Receive buffers = 6 Controller = normal Protocol = Ethernet Service timer = 4000 Hardware address = AA-00-03-01-1D-E7 UNA device buffer size = 1498 I hope this helps. Selden E. Ball, Jr. (Wilson Lab's network and system manager) Cornell University NYNEX: +1-607-255-0688 Laboratory of Nuclear Studies BITNET: SYSTEM@CRNLNS Wilson Synchrotron Lab ARPA: SYSTEM%CRNLNS.BITNET@WISCVM.WISC.EDU Judd Falls & Dryden Road PHYSnet/HEPnet/SPAN: Ithaca, NY, USA 14853 LNS61::SYSTEM = 44283::SYSTEM (node 43.251)
jch@OMNIGATE.CLARKSON.EDU (Jeffrey C Honig) (08/12/87)
>>I'm afraid I fail to see where you get AA-00-03-01-10-E7 from 19.53. >>... >>or, node 57.784. > >Well, I'm afraid I didn't get it: DECnet did. I guess it doesn't >use your algorithm. Actually, it does. >Hardware address = AA-00-03-01-1D-E7 What your 'ncp show line una-0 char' report is showing you is the hardware ethernet address before DECnet changes it. Try looking at an Ethernet monitor. If you are running TCP/IP on that host they try looking in the ARP cache of another host or router on that network for the Ethernet address that is actually being used. Jeff