Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Mar 2000 14:12:50 +0800
From:      "Jiawei Ye" <leafy@titan.seed.net.tw>
To:        <cjclark@home.com>, <freebsd-questions@freebsd.org>
Subject:   Re: Odd ex0 Problem in 4.0
Message-ID:  <001301bf987c$a65f18c0$040a0a0a@eurofront4>
References:  <20000327234659.F11538@cc942873-a.ewndsr1.nj.home.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I have exactly the same problem as you do, with my nic being DFE-500TX
(de0) and my system cannot be waken up by tcpdump unfortunately.
----- Original Message -----
From: Crist J. Clark <cjc@cc942873-a.ewndsr1.nj.home.com>
To: <freebsd-questions@freebsd.org>
Sent: Tuesday, March 28, 2000 12:47 PM
Subject: Odd ex0 Problem in 4.0


> I installed FreeBSD 4.0 onto a i486DX that has an Intel EtherExpress
> Pro NIC, ex0. The NIC has been acting weird with 4.0 where there
> previously were no problems with 3.x.
>
> After I boot up, if I try to connect to or ping the 486 from others on
> the LAN, there is no response, just,
>
> sendto: Host is down
>
> Messages. Likewise, if I go to the console of the 486 and try to ping
> out, nothing. tcpdump(8) on one of the other machines shows silence
> from the 486. However, this is where it gets strange...
>
> The 486 has,
>
> ex0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX> mtu 1500
>         inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
>         ether 00:aa:00:a5:af:91
>
> from ifconfig(8) and,
>
> ex0: <Intel Pro/10> at port 0x300-0x30f irq 10 on isa0
> ex0: Ethernet address 00:aa:00:a5:af:91
>
> >From dmesg(8), but like I said, networking does not work. I start a
> ping on one virtual console and get,
>
> sendto: Host is down
> sendto: Host is down
> sendto: Host is down
>
> On and on. Then, I go to another console and try turning on tcpdump. I
> get,
>
> ex0: promiscuous mode enabled
>
> A few seconds of silence and then, "Boom!" ping packets are flying. If
> I go back to the ttyv where I was pinging, suddenly things are
> alive. When I turn off tcpdump, thing continue to work fine after we
> switch back out of promiscuous mode.
>
> It seems like the network card is not being properly initialized by
> the system. I have tried re-ifconfiging it, but the tcpdump seems the
> only thing that wakes it up that I have found.
>
> Has anyone seen this? Anyone have a solution? Anyone have suggestions
> for documenting it so it can be debugged and fixed?
>
> Thanks.
> --
> Crist J. Clark                           cjclark@home.com
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001301bf987c$a65f18c0$040a0a0a>