Jonathan M. Bresler writes:
>
> no response, no service. furthermore, you can cache the arp data
>in a file on your local dns server. (write a tiny perl script to sit
>around responding to requests, iteratively. it can also notify you when
>the guy with a pc in the next office decides to start using the wrong ip
>number. a common problem here, as we bring all the dussss and windoze
>users to the real world)
ftp.net.ohio-state.edu:/pub/networking/arpmon/*
It passively watches arp requests (and replies if you're willing to take
the performance hit on the machine doing the monitoring) with tcpdump and
produces formatted reports.
--
mark
maf+ @
osu .
edu
References:
|
|
