Date: Mon, 22 Jan 2007 11:30:38 +0800 From: David Schulz <mailinglists@tca-cable-connector.com> To: ceo@l-i-e.com Cc: questions@freebsd.org Subject: Re: Loosing Ethernet Connectivity Message-ID: <9A22D208-C86A-47FC-8AF6-0D7C071213AE@tca-cable-connector.com> In-Reply-To: <62460.209.254.223.2.1169435747.squirrel@www.l-i-e.com> References: <037FAB79-B890-46CE-9522-E0A7EE58661F@tca-cable-connector.com> <62460.209.254.223.2.1169435747.squirrel@www.l-i-e.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey, sure, i can do a script which does the up-down when it cant ping the router or something, but to be honest i think that is not a production solution. cheap nic..maybe, some of the nics in question where onboard ones, which are not the best ones out there, but others, such as the 3COM 3c90b5 Fast Etherlink XL PCI, is that also a shitty one? I also have a tried a simple D-LINK and a Realtek one. It seems that under a certain condition FreeBSD just shuts down its Networking, and if thats true i wonder if that can be done remotely, that would not be cool. David On Jan 22, 2007, at 11:15 AM, Richard Lynch wrote: > Sounds like flaky/cheap network card to me... > [But I'm no expert] > > Perhaps, however, just doing a cron job every day to do the ifconfig > down/up would be a simple work-around. > > On Sun, January 21, 2007 9:12 pm, David Schulz wrote: >> Hello all, >> >> every once in a while i have a machine (6.1) that out of the blue, >> sometimes after days, some after 6 months, looses Ethernet >> Connectivity. My Machines just run some Service, and have no >> Keyboard / Mouse or Monitor. When the Machine goes down, eg, i am >> unable to ping it from another Machine on the Network, even >> restarting the machine using "reboot" will not fix the Problem. The >> only way to fix it is to login as root, and issue a "ifconfig vr0 >> down && ifconfig vr0 up". Then a dmesg Message appears : "vr0: Using >> force reset command.", and after that i can successfully ping the >> machine again. I have had this Problem on different machines with >> different Network Cards, on different Ethernet Cables, and with >> FreeBSD Versions 5.5 until 6.1. >> >> Can anyone please help me to understand and possibly even fix this >> Problem? >> >> Thanks a lot, >> David >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > > > -- > Some people have a "gift" link here. > Know what I want? > I want you to buy a CD from some starving artist. > http://cdbaby.com/browse/from/lynch > Yeah, I get a buck. So? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9A22D208-C86A-47FC-8AF6-0D7C071213AE>