At 12:21 AM 2/21/2004, Saint Aardvark the Carpeted wrote:
Jim Pazarena disturbed my sleep to write:
> May sound rookie, but presently I go to each box and determine it's
> IP directly and then I "know" the IP (at least for this session).

What I end up doing is browing the hosts file on my gateway machine.

run "arp -an"

This didn't give very satisfactory results for my fbsd box e.g.

%arp -an
? ( at 00:08:74:c0:5e:69 on ep0 [ethernet]
? ( at 00:a0:cc:40:55:cf on ep0 [ethernet]
%ping penguin
PING penguin ( 56 data bytes
64 bytes from icmp_seq=0 ttl=64 time=1.536 ms
64 bytes from icmp_seq=1 ttl=64 time=0.691 ms
64 bytes from icmp_seq=2 ttl=64 time=0.673 ms
--- penguin ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.673/0.967/1.536/0.403 ms
%arp -an
? ( at 00:08:74:c0:5e:69 on ep0 [ethernet]
? ( at 00:a0:24:75:04:49 on ep0 [ethernet]
? ( at 00:a0:cc:40:55:cf on ep0 [ethernet]

As you can see only the gateway and one other box (5 total on my lan) were cached. After pinging penguin it got into the cache but this looks like arp is unreliable for a canonical list of plugged in ip's.

Curious about what would work. Nmap(8) isn't installed on my system now, is this the way to go? Nothing in my base install to do it?

Marty Landman Face 2 Interface Inc 845-679-9387 This Month's New Quiz --- Past Superbowl Winners Make a Website:

[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to