--- Daniel Eggert <danieleggert@mac.com> wrote:
>  
> On Wednesday, Aug 14, 2002, at 09:46PM, Jeremy C.
> Reed <reed@reedmedia.net> wrote:
> 
> >What does "netstat -rn -f inet | grep ^127" report?
> 
> Here's what the box says:
> 
> pingvin# netstat -m -f inet
> 3 mbufs in use:
>         2 mbufs allocated to data
>         1 mbufs allocated to packet headers
> 0/10 mapped pages in use
> 28 Kbytes allocated to network (2% in use)
> 0 requests for memory denied
> 0 requests for memory delayed
> 0 calls to protocol drain routines
> 
> 
> >And I am curious, what does "tcpdump -i lo0" tell
> you while you ping?
> >
> 
> And for the tcpdump is just as sad:
> 
> pingvin# tcpdump -i lo0 & ping 127.0.0.1
> [2] 208
> tcpdump: listening on lo0
> PING localhost (127.0.0.1): 56 data byes
> ^C
> ----localhost PING Statistics----
> 0 packets transmitted, 0 packets received,
> pingvin# kill -HUP 208
> 
> 0 packets received by filter
> 0 packets dropped by kernel
> [2]    Done                   tcpdump -i lo0
> 
> Well, well... I'm downloading 1.5.3 and the sources
> to compile the kernel. Then I'll burn it on CD and
> upgrade the box to see if that or a custum kernel
> will help.

Well, before you do all of that, did you ping -n? (I
may have missed this because I didn't read the whole
thread.) This was important because it doesn't attempt
to do any resolution. Your /etc/nsswitch.conf file may
be the answer to all of this...

Andy

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com