???? Why is "ping" depending on the Date????
Is NetBSD looking for a "pong" in the same year?

Nic

-----Original Message-----
From: Daniel Eggert [mailto:danieleggert@mac.com]
Sent: Donnerstag, 15. August 2002 18:04
To: Andy R
Cc: Jeremy C. Reed; netbsd-help@netbsd.org
Subject: Re: Can't ping 127.0.0.1 -- finally solved!


Hi all,

First of all: Thanks for the loads of help. You rock. I finally found =
the solution. My date was set to something too old (1956). After =
changing it to the present day, everything is just fine, and I am (very) =
happy with my NetBSD box. Time to install applications. Thanks again.

/Daniel


On Thursday, Aug 15, 2002, at 05:39PM, Andy R <quadreverb@yahoo.com> =
wrote:

>--- Daniel Eggert <danieleggert@mac.com> wrote:
>> =20
>> On Wednesday, Aug 14, 2002, at 09:46PM, Jeremy C.
>> Reed <reed@reedmedia.net> wrote:
>>=20
>> >What does "netstat -rn -f inet | grep ^127" report?
>>=20
>> Here's what the box says:
>>=20
>> 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
>>=20
>>=20
>> >And I am curious, what does "tcpdump -i lo0" tell
>> you while you ping?
>> >
>>=20
>> And for the tcpdump is just as sad:
>>=20
>> 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
>>=20
>> 0 packets received by filter
>> 0 packets dropped by kernel
>> [2]    Done                   tcpdump -i lo0
>>=20
>> 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
>
>