Re: Problem with ethernet i/f

["J.C. Roberts" <unknown@abac.com>]

On Sat, 15 Sep 2001 15:05:45 -0400, you wrote:

>You made a tiny `mistake' by hitting reply to another message on the
>list in order to post to this list. It causes a reference to the other
>message to be put in the message you're sending... That particular
>message was a complaint about the recent off topic posts and asked
>people not to reply to it... -Anyone who uses message threading
>without subject filters will see your post below the post that asked
>people not to reply to it.  ;-)
>
>**I did'nt realize that. I am creating a new thread here.
>

It's no big deal but being aware of message headers is really a good
thing. ;-)

>Check to make sure there's a light on your NIC and a light on the
>hub/switch. (e.g. possible cable problems)
>
>Light is there on the card but corresponding one on the hub is not on.
>Does it have any thing to do with the driver on openBSD. My ethernet
>card is 3Com509. There was no configuration during openbsd installation
>when i specified the ethernet card type.(3Com509)
>
>The other machines on the same subnet have the same net mask?
>Yes.
>
>if you can run the following and post the results
>
># ifconfig -m ep0
>
>ep0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu
>1500
>        media: Ethernet 10 BaseT
>        supported media:
>                          media 10baseT
>                          media 10Base5
>        inet 10.0.0.177  netmask 0xffffff00 broadcast 10.0.0.255
>


Below the "media:" line there should be a "status:" line which reads

	status: active


># netstat -rnf inet
>
>Destination        Gateway            Flags        Refs
>Use         Mtu        Interface
>default                10.0.0.155            UGS            0
>4            1500        ep0
>10.0.0/24               link#1                 UC
>0            0            1500        ep0
>10.0.0.155             link#1                  UHL
>1            0            1500        ep0
>10.0.0.177            127.0.0.1            UGHS          0
>0            32972        lo0
>

cool

># arp -an
>
>? (10.0.0.155) at (incomplete)
>
>

OK this is a bit more proof the system isn't talking to _ANYTHING_
including it's gateway. On a fresh boot the system will send out an
ARP-Request to get the MAC address of it's default gateway.

(more in the next email)...