As requested by various responders, here is some additional
information:

From dmesg:

ep0 at isa0 port 0x340-0x34f irq 5: 3Com 3C509 Ethernet
ep0: address 00:a0:24:ec:81:f9, 8KB byte-wide FIFO, 5:3 Rx:Tx split
ep0: 10baseT, 10base5, 10base2 (default 10baseT)

From ifconfig ep0:

ep0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu
1500
	address: 00:a0:24:ec:81:f9
	media: Ethernet 10baseT
	inet 192.168.0.8 netmask 0xffffff00 broadcast 192.168.0.255
	inet6 fe80::2a0:24ff:feec:81f9%ep0 prefixlen 64 scopeid 0x1

From netstat -rn -f inet:

Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use    Mtu 
Interface
default            192.168.0.1        UGS         0        0   1500 
ep0
127                127.0.0.1          UGRS        0        0  33228 
lo0
127.0.0.1          127.0.0.1          UH          1        0  33228 
lo0
192.168            link#1             UC          1        0   1500 
ep0
192.168.0.1        link#1             UHLc        1        9   1500 
ep0


Thanks,

Jeff
08.18.2002


--- "Brian A. Seklecki" <lavalamp@spiritual-machines.org> wrote:
> On Sat, 17 Aug 2002 @ 6:42pm (-0700), Jeffrey Ohlmann wrote:
> 
> JO> I have a new installation of NetBSD 1.5.3 i386. I have used
> earlier
> JO> versions of NetBSD on the mac68k platform, but this is my first
> JO> experience with 1.5.x and the i386 port.
> JO>
> JO> I have read all of the documentation repeatedly, and as far as I
> can
> JO> tell I have made all the necessary network
> configurations--ifconfig,
> JO> mygate, hosts, nsswitch.conf, resolv.conf--but I am unable to
> reach any
> JO> other hosts on my internal network.
> JO>
> JO> The i386 can ping itself at the loopback and at its own assigned
> static
> JO> IP, but any attempts to ping other machines result in "send to:
> host is
> 
> 	This error is a result of the inability to ARP for a host.
> 
> JO> down". I have tried two different cables to no effect. I can see
> JO> activity on the hub at the port for the i386. The i386 cannot be
> JO> reached by other hosts either. The hardware is known to have been
> JO> working under other operating systems previously.
> 
> 	include your NIC card info form dmesg (/var/run/dmesg.boot)
> 
> JO>
> JO> I am looking for suggestions of what to try next. The 1.5.3 rc.d
> method
> JO> is new to me, so perhaps I have overlooked something there and do
> not
> 
> 	use tcpdump(1) to have a look around.  Just:
> 
> 	# tcpdump | tee /var/log/tcpdump.out
> 
> JO> know it.
> JO>
> JO> Many thanks,
> 
>     debug debug debug.
> JO>
> JO> Jeffrey Ohlmann
> JO>
> JO> __________________________________________________
> JO> Do You Yahoo!?
> JO> HotJobs - Search Thousands of New Jobs
> JO> http://www.hotjobs.com
> JO>
> 
> later -           | _BonaFide[] = { coder, author, | /~\ The ASCII
> Ribbon
> Brian A. Seklecki | problem solver, scholar, BOFH, | \ / Campaign
> Against
>                   | vegetarian, runner, NetBSD     |  X  Exchange,
> Outlook
>                   | advocate, spiritual machine }; | / \ & HTML Email
> 
> PGP: 0111 4618 0111 4618 4AB2 24EB C853 6611 75C4 A91E A7A7 4973
> 


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