On Tue, 17 Jun 2003, Bill Moran wrote: > What make/model of NIC are you using?
cerberus# ifconfig -a fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 10.0.3.2 netmask 0xffffff00 broadcast 10.0.3.255 ether 00:e0:81:21:45:8c media: Ethernet autoselect (10baseT/UTP) status: active fxp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 10.1.1.1 netmask 0xffff0000 broadcast 10.1.255.255 ether 00:e0:81:21:45:8d media: Ethernet autoselect (100baseTX <full-duplex>) status: active lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 The interface in question is 10.0.3.2. That interface has worked fine for over a year. That driver is in use on several other systems for several years each. No problems until now. > The only time I've ever seen this, the only thing that solved the problem > was swapping the network card out for a better one. > That's not to say it isn't a driver problem, as the new network card used > a different driver as well. I think that the NIC is on the logic board. I can try to install a PCI card and use that in its place to see if the problem goes away. Should I bother? FWIW, a reboot of the system did not help. Jaime _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"