home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.lans.ethernet
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!spool.mu.edu!yale.edu!jvnc.net!newserver.jvnc.net!gmd.de!hoens
- From: hoens@gmd.de (Guenter Hoens)
- Subject: new hardwareaddress
- Message-ID: <hoens.726222216@gmd.de>
- Sender: news@gmd.de (USENET News)
- Nntp-Posting-Host: gmdzi
- Organization: GMD, Sankt Augustin, Germany
- Date: Tue, 5 Jan 1993 08:23:36 GMT
- Lines: 29
-
- it is our job, to look after our local ethernet.
- we think, that it is important, to know, which machines are connected
- to ethernet.
- (when we find broken packets on the net, which include the hardware-
- address, then we can look after that special machine, change the
- ethernet-board, if necessary and so on.)
-
- we have a set of known addresses, and we have software to find new
- addresses on our ethernet.
-
- if the new hardware address is in a internet-packet, we have good chances
- to find the machine, because the IP-address is well known on our net.
-
- but if the new machine uses a different protocol, we do not know, how to
- find out some facts about the new machine.
-
- of course we can see, what protocol is used, and we can see (first bytes
- of the hardware address), what sort of machine it is.
-
- but it is difficult to find out, where this machine is and how it is named
- by its user.
-
- do you have similiar problems? how do you handle this?
-
- --
- -----------------------------------------------------------------
- * Guenter Hoens, GMD - I8,
- * German National Research Center for Computer Science
- * hoens@gmd.de (02241) 14-2408
-