Re: Report of a number of problems

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Thanks for answering so quickly, I will try that. I have unfortunately
:discovered more problems. DragonFly (also FreeBSD 6.0) cannot
:communicate with the rest of the world. My NIC is Netgear FA311, which
:has a National Semiconductor DP83815 chip in it. I am able to ping
:127.0.0.1, also able to ping 192.168.1.50 (NIC's IP), but unable to ping
:everything else including the gateway. (192.168.1.1)
:
:once i do "ping 192.168.1.1" nothing happens, no time out, or no route
:to host, no destination unreachable and so on. tcpdump does not report
:any activity whatsoever. Logs do not indicate what the problem is,
:however I did notice my NIC sometimes goes to promiscuous mode in
:DragonFly. Theres positively nothing wrong with my configuration, or
:wrong with the NIC itself, since it works perfect in Linux and OpenBSD.
:
:> Can you try a kernel without atapicam?
:I will when I can fetch the source and recompile. 
:
:Or is there a boot-time command to do it also?

    I don't see the NIC in the dmesg output you posted.  Perhaps it is
    being loaded as a module?  If so then you probably need to post 
    the actual 'dmesg' output after the interface has been configured
    instead of /var/run/dmesg.boot.

    Also provide the output from 'ifconfig' after you have configured the
    interface.

    It's very odd that the loopback ping works when a remote ping does
    not.  It could be an interrupt routing issue.  The way to check is:

	sysctl kern.emergency_intr_enable=1

    If ping to another host on the LAN suddenly starts working, then we
    know its an interrupt routing issue.  If not, then we know its a driver
    issue.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>