From owner-freebsd-net@FreeBSD.ORG Thu Jun 5 09:10:59 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98108106564A for ; Thu, 5 Jun 2008 09:10:59 +0000 (UTC) (envelope-from freebsd-net@pp.dyndns.biz) Received: from proxy3.bredband.net (proxy3.bredband.net [195.54.101.73]) by mx1.freebsd.org (Postfix) with ESMTP id 4B1728FC25 for ; Thu, 5 Jun 2008 09:10:59 +0000 (UTC) (envelope-from freebsd-net@pp.dyndns.biz) Received: from ironport.bredband.com (195.54.101.120) by proxy3.bredband.net (7.3.127) id 481183EA00C4DB68 for freebsd-net@freebsd.org; Thu, 5 Jun 2008 10:50:08 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvUxABBGR0hV4juxPGdsb2JhbACBVYcMiR0BAQEBLZ1M Received: from c-b13be255.107-1-64736c10.cust.bredbandsbolaget.se (HELO gatekeeper.pp.dyndns.biz) ([85.226.59.177]) by ironport1.bredband.com with ESMTP; 05 Jun 2008 10:50:08 +0200 Received: from [192.168.69.67] (phobos [192.168.69.67]) by gatekeeper.pp.dyndns.biz (8.14.2/8.14.2) with ESMTP id m558o6Z7085892 for ; Thu, 5 Jun 2008 10:50:07 +0200 (CEST) (envelope-from freebsd-net@pp.dyndns.biz) Message-ID: <4847A8BE.4010201@pp.dyndns.biz> Date: Thu, 05 Jun 2008 10:50:06 +0200 From: PP User-Agent: Thunderbird 2.0.0.14 (X11/20080521) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: network keep droping X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2008 09:10:59 -0000 Izwan Mohd wrote: > Hi, > > I have being encountering a weird problem on my freebsd 6 , one of my remote > machine being down frequently lately for no particular reason, when I go to > the remote site to check then machine it was in good running condition but > no network, it even can't ping the server on the same subnet, the only way > to restore it back is by running: > > route -n flush && /etc/netstart > > but because it a remote machine it really troublesome to do that each time > the machine is down, I resorted to use a crontab scripts to automatically > run the previous command when it down, even tho that partial of the problem > is solve I still need to know what causing it. can anyone could advise me > where to start digging?? they is no any particular error in the log or dmseg > when the machine dropped it connection so I'm stuck here don't know where to > start, some help should clear something up for me > > TQ This sounds vaguely similar to what I've experienced myself with an onboard em0 on a Supermicro mainboard. NIC suddenly stopped working for no appearent reason. Believing the NIC was bad I throw in an extra NIC and ran the machine from that. But within a month a capacitor blew in the PSU and when I replaced the PSU the onboard NIC worked again. This scenario repeated 3 times in exactly the same way before I switched to another PSU brand and haven't had any problems since. In my case I couldn't get the NIC running with a simple flushing of the routes though. But if nothing has changed in the software on the machine you should probably start looking at the hardware. /PP