Re: hosts.allow does not resolve names
- From: Bit Twister <BitTwister@xxxxxxxxxxxxxxxx>
- Date: Thu, 29 Nov 2007 02:24:32 GMT
On Wed, 28 Nov 2007 19:36:25 -0600, Moe Trin wrote:
On Wed, 28 Nov 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <slrnfkpuk7.5sj.BitTwister@xxxxxxxxxxxxxxx>, Bit Twister wrote:
Moe Trin wrote:
Quick look - is there anything obvious in a packet dump?
Not to my untrained eye. Here is fail followed by works.
arp reply m2008 is-at 00:a0:cc:e6:de:71 (oui Unknown)
[compton ~]$ etherwhois 00:a0:cc
00-A0-CC (hex) LITE-ON COMMUNICATIONS, INC.
00A0CC (base 16) LITE-ON COMMUNICATIONS, INC.
720 S. HILLVIEW DRIVE
MILPITAS CA 95035
UNITED STATES
[compton ~]$
Your sniffer is old - that OUI has been out there for at least 8 years.
What can I say, used wireshark saved run to file. It was binary.
Installed tcpdump and had it convert to ascii. :)
No obvious difference in the first conversation, but this continues.
Several of the lines look weird, but the stuff is working. (I haven't
sniffed NFS in several years - so I'm awfully rusty. Sorry)
That's Ok, and I do apprecate your time and effort. Guess I'll settle
for using ip numbers.
.
- References:
- hosts.allow does not resolve names
- From: Bit Twister
- Re: hosts.allow does not resolve names
- From: Moe Trin
- Re: hosts.allow does not resolve names
- From: Bit Twister
- Re: hosts.allow does not resolve names
- From: Moe Trin
- Re: hosts.allow does not resolve names
- From: Bit Twister
- Re: hosts.allow does not resolve names
- From: Moe Trin
- hosts.allow does not resolve names
- Prev by Date: Re: hosts.allow does not resolve names
- Next by Date: confuse for arp response
- Previous by thread: Re: hosts.allow does not resolve names
- Next by thread: Re: hosts.allow does not resolve names
- Index(es):