home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!usc!news.service.uci.edu!cerritos.edu!arizona.edu!telcom.arizona.edu!leonard
- Newsgroups: comp.dcom.lans.ethernet
- Subject: Re: new hardwareaddress
- Message-ID: <1993Jan6.093649.4210@arizona.edu>
- From: leonard@telcom.arizona.edu (Aaron Leonard)
- Date: 6 Jan 93 09:36:47 MST
- Reply-To: Leonard@Arizona.EDU
- References: <hoens.726222216@gmd.de> <mark.726251794@coombs> <hoens.726332427@gmd.de>
- Distribution: world,local
- Organization: University of Arizona Telecommunications
- Nntp-Posting-Host: penny.telcom.arizona.edu
- Lines: 24
-
- In article <hoens.726332427@gmd.de>, hoens@gmd.de (Guenter Hoens) writes:
-
- | we have about 600 machines on our ethernet. sometimes there are
- | new machines, sometimes boards are changed.
- | we can not walk along the cable to look after every transceiver.
- |
- | if the new machine uses IP, then we can find out all about the new
- | machine, but if it is a different protocol, then we can find out (by looking
- | at the packets) what sort of machine/ethernet board and what protcol is
- | used.
- | we might be able to write a programm, which will ask the new machines
- | after their name. but we will have to know about something like a
- | name binding protocol for the used protocol. unfortunately most of the
- | protocols are not very well documentated.
- |
- | any ideas?
-
- Sounds like what you want to do is to reinvent the Network General
- Sniffer (TM). I.e. you need some software that can decode the many
- higher layer protocols that you have flying around your network.
- If you don't want to write the code yourself, buy a Sniffer (or one of
- its competitors.)
-
- Aaron
-