Date: Sat, 11 Mar 2000 10:24:16 -0500 (EST) From: Bryan Liesner <bleez@netaxs.com> To: freebsd-current@freebsd.org Subject: Unexplained network outages Message-ID: <Pine.BSF.4.21.0003111023370.409-100000@dyn-43.blackbox-2.netaxs.com>
next in thread | raw e-mail | index | archive | help
I have a win98 box connected to a 4.0-current box via an ethernet connection. The connection will go dead after about 20 minutes. I'm unable to ping the win98 box and cannot ping the FreeBSD box from the win98 box. No error/console messages. I can bring it back to life by doing an ifconfig dc1 down/up, then pinging the win98 box. Has anyone experienced this behavior? The strange thing is that the network never goes down if I run tcpdump in promiscuous mode on the interface - it's a workaround, but I don't like it. Any ideas would be greatly appreciated. Here's the output from ifconfig and dmesg: dc1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:80:c6:f9:70:ec media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback> none dc1: <Macronix 98715/98715A 10/100BaseTX> port 0xec00-0xecff mem 0xebfbff00-0xebfbffff irq 10 at device 5.0 on pci0 dc1: Ethernet address: 00:80:c6:f9:70:ec miibus1: <MII bus> on dc1 dcphy1: <Intel 21143 NWAY media interface> on miibus1 dcphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@netaxs.com Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003111023370.409-100000>