From owner-freebsd-questions@freebsd.org Tue Jun 28 13:32:33 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18D6BB857FE for ; Tue, 28 Jun 2016 13:32:33 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from smtpb.telissant.net (smtpb.telissant.net [199.233.230.156]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E500E2E3F for ; Tue, 28 Jun 2016 13:32:32 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from barrida.3dresearch.com (localhost [127.0.0.1]) by smtpb.telissant.net (Postfix) with ESMTP id 7B6903AECB for ; Tue, 28 Jun 2016 09:32:25 -0400 (EDT) X-Virus-Scanned: amavisd-new at telissant.net Received: from smtpb.telissant.net ([127.0.0.1]) by barrida.3dresearch.com (barrida.3dresearch.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zsA_Yc-Ic41p for ; Tue, 28 Jun 2016 09:32:05 -0400 (EDT) Received: from almavivazfs.3dresearch.com (unknown [71.112.241.83]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtpb.telissant.net (Postfix) with ESMTPSA id 7A4E63ACDF for ; Tue, 28 Jun 2016 09:32:05 -0400 (EDT) Received: from almavivazfs.3dresearch.com (localhost [127.0.0.1]) by almavivazfs.3dresearch.com (Postfix) with SMTP id C967FAA25AF for ; Tue, 28 Jun 2016 09:32:04 -0400 (EDT) Date: Tue, 28 Jun 2016 09:31:56 -0400 From: Janos Dohanics To: FreeBSD Questions Subject: Re: LAN slow or dead, intermittently Message-Id: <20160628093156.f46f1d912f797ff75dd6f016@3dresearch.com> In-Reply-To: <57712130.2050603@gmail.com> References: <20160624112659.a9fd454b8d05166befb5876d@3dresearch.com> <57712130.2050603@gmail.com> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 13:32:33 -0000 On Mon, 27 Jun 2016 08:50:56 -0400 Ernie Luzar wrote: > Janos Dohanics wrote: > > Hello List, > > > > Please help me figure out what makes my LAN intermittently slow or > > just about dead. > > > > [...] > > I also had performance problems with 10.3 that did not happen with > 10.2 and older releases. When the lan went dead I had to reboot the > host system to get things working again because users were on my > back. I never let this condition exist to see if it would resolve it > self. > > My first solution was to go back to using 10.2 and everything was > fine. One evening I swapped the hosts 10.2 hard drive with the 10.3 > hard drive so I could test some more. Just by luck I checked the date > & time by issuing the "date" command. The date was correct but the > time was -2 hours off. I manually set the correct time using the > "date" command and let 10.3 run as production. With in 5 days the lan > network was having performance problems again. I checked the host > time and it was off by -30 minutes. I replaced the host motherboard > battery with a new one and manually set the correct time again. > Things ran ok for about 2 weeks when it happened again. This time the > time was off by -2 minutes. > > This time I enabled the base ntpd time daemon by adding this to > rc.conf ntpd_enable="YES" > ntpd_sync_on_start="YES" > > Since then 10.3 has been running ok [2 months now]. I think some > thing in the network stack code changed between 10.2 and 10.3 that > made the time sync between lan nodes and the host, time range > dependent. > > I would say that checking the time on your host and all the machines > on the lan would be a good place to start looking for your problem. > > Good luck Well, date(1) shows a time which seems reasonably correct... it didn't occur to me that an inaccurate clock could also be the cause of the kind of problem I described. Thanks anyway... -- Janos Dohanics