On onsdag, aug 14, 2002, at 19:24 Europe/Copenhagen, Andy R wrote:

> --- Nicolas Saurbier <Nicolas.Saurbier@biodata.de>
> wrote:
>> I also some strange behavior when I tried pinging
>> something.
>> Try the following, delete /etc/resolv.conf
>>
>> I know this sounds strange, but just try it.
>>
>>
>> -----Original Message-----
>> From: Daniel Eggert [mailto:danieleggert@mac.com]
>> Sent: Mittwoch, 14. August 2002 18:25
>> To: Andy R
>> Cc: netbsd-help@netbsd.org
>> Subject: Re: Can't ping 127.0.0.1
>>
>>
>>
>> On Wednesday, Aug 14, 2002, at 02:52PM, Andy R
>> <quadreverb@yahoo.com> wrote:
>>
>>> --- Daniel Eggert <danieleggert@mac.com> wrote:
>>>> This is puzzling me:
>>>>
>>>> I've done a fresh install of 1.5.2. I set up
>>>> defaultrouter, hostname, and configured (one of
>> my
>>>> 4) NIC. Nothing else -- standard install without
>>>> X11. But when I try to
>>>>     ping 127.0.0.1
>>>> nothing happens. I hope someone can point out to
>> me,
>>>> what I'm doing wrong.
>>>
>>> What does the output of ifconfig -a (or ifconfig
>> lo0)
>>> show?
>>>
>>> Did you attempt to set up firewalling? Blocking
>> ICMP?
>>>
>>> Andy
>>>
>>
>> I have no firewall and hence no ICMP blocking --
>> just a clean install. I setup my ip-number, router,
>> and dns.
>>
>> My NIC is configured as follows (pingvin is my
>> hostname):
>> pingvin# ifconfig mc0
>> mc0:
>>
> flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
>> mtu 1500
>>         address: 00:a0:40:24:d4:8c
>>         media: Ethernet manual
>>         inet 130.225.92.238 netmask 0xffff0000
>> broadcast 130.225.255.255
>>         inet6 fe80::2a0::40ff:fe24:d48c%mc0
>> prefixlen 64 scopeid 0x1
>> and my loopback interface as follows:
>> pingvin# ifconfig lo0
>> lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33228
>>         inet 127.0.0.1 netmask 0xff000000
>>         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
>>         inet6 ::1 prefixlen 128
>> When i do a ping to the loopback it looks like this:
>> pingvin# ping 127.0.0.1
>> PING localhost (127.0.0.1): 56 data bytes
>> ^C
>> ----localhost PING Statistics----
>> 0 packets transmitted, 0 packets received,
>> I press <ctrl>-C after 30 sec. That's it. It looks
>> very strange, but hope you can help me.
>
> Hmm. Not too sure about what deleting resolv.conf
> would do in this case, but I guess it's worth a try to
> rename it...
>
> What gets me is that 0 packets were sent, there has to
> be some meaning for that. Usually when you start
> pinging, it sends them but you just don't get anything
> back. I think this is probably the avenue you need to
> follow. Can you ping your ethernet interface using the
> IP?
>
> Any nutty entries in your /etc/hosts file or
> something?
>

I quite agree with you, that the strangest of all of it is the fact, 
that no packets get SEND. That of course explains why no packets get 
received, but not what solution to choose.

Also, I'm certain, that it is not a problem with resolv.conf. If you 
look at the ping result, you can see, that ping correctly maps 
'localhost' to 127.0.0.1. If it couldn't the 1st line wouldn't show up. 
I also tried to rename resolvconf into resolv.conf.old. Same story -- 
no result.

When I try to ping any NIC with its own IP same thing happens.

Only new part of info I have, is that when I do a
	pingvin# route flush
strange things happen. First the box hangs for a while, and then the 
driver (mc) complains about some watchdog. Something like wcwatchdog: 
resetting chip appears on the console. So I guess, that it might be 
some problem with the NIC and/or driver. Then again it's difficult to 
download via ftp with no internet conection.

I hope someone figures this out. Thanks.

Daniel