Yes, I am also very familiar with this problem. If you run a tcpdump
process on the dead interface it comes back to life again. (As Darren
also found out according to the PR he submitted.)

I've got about ten of these cards here and plenty of firewalls to put
them in, would be nice to get this prob. fixed up since they detect
and seem to work so nicely otherwise.

It especially becomes apparent if you run two of them in the same
machine (as in a firewall et al.)

marc

On Fri, 2 Mar 2001, Darren Reed wrote:

> Date: Fri, 2 Mar 2001 18:28:50 +1100
> From: Darren Reed <darrenr@reed.wattle.id.au>
> To: Ben Elliston <bje@air.net.au>
> Cc: tech-net@netbsd.org
> Subject: Re: iy driver problems
>
> In some email I received from Ben Elliston, sie wrote:
> > I'm using the iy (Intel EtherExpress PRO/10) driver.  After periods of heavy
> > traffic through this interface, the interface stops responding--ping, the
> > works.  If I `ifconfig iy0 down' and then reconfigure the interface, it's
> > fine again.
> >
> > Is this a known problem?  Should I just get a different model of net card?
>
> Familiar problem to me, at least.  That was with NetBSD-1.4.  What version
> of NetBSD are you using ?
>
> Darren
>