From owner-freebsd-current@freebsd.org Mon Apr 25 06:15:52 2016 Return-Path: Delivered-To: freebsd-current@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 A8A65B1B3FA for ; Mon, 25 Apr 2016 06:15:52 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 92D971CA7 for ; Mon, 25 Apr 2016 06:15:52 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 921F7B1B3F9; Mon, 25 Apr 2016 06:15:52 +0000 (UTC) Delivered-To: current@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 91C64B1B3F8 for ; Mon, 25 Apr 2016 06:15:52 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57FFD1CA6 for ; Mon, 25 Apr 2016 06:15:51 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.241] (helo=rmm6prod02.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1auZo5-0002qP-SW; Mon, 25 Apr 2016 08:15:41 +0200 Received: from mail by rmm6prod02.runbox.com with local (Exim 4.76) (envelope-from ) id 1auZo5-0004ao-SC; Mon, 25 Apr 2016 08:15:41 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Mon, 25 Apr 2016 06:15:41 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "current" CC: "jbtakk" , "kernel" Subject: Re: nfe0 connection not as reliable; a few questions... Date: Sun, 24 Apr 2016 23:15:41 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 06:15:52 -0000 On Sat, 23 Apr 2016 19:48:46 -0700 (PDT), "Jeffrey Bouquet" wrote: > Updated current { from Sept last year } to this week... and nfe0 now see= ms to require a reboot=20 > daily at least { no access to beyond-the-lan ... }=20 >=20 > Is there maybe some tunable (net.inet... ) related or sysctl { kern.ipc.= .. } similar, that > could be a cause? New code of ifconfig or the network stack within the l= ast seven > months or so? Usual fixes of MTU size to set?=20 >=20 > The coincidence of the daily network stack loss with the installkernel/wo= rld r298350 would > at first glance rule out hardware issues... Hadn't seen that type of netw= ork issue before > { I can connect to the gateway, but the modem { comtrend } in bridge mod= e seems > to fail. }. I checked some of the net@freebsd.org list to no avail...= The modem had worked > fine for about two weeks previously... at least. >=20 > Apologies for wasting anyone's time; there are tests I could run with mor= e machines on the > lan, but though to ask here first. And did not think of those setups un= til after I had half-completed > this email... >=20 > Thanks. >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Progress [still unsure]. On a hunch I ran a small .sh to ping a site perio= dically [ not constantly and within terms of its usage of course.] That .sh was set up some years back to keep a wifi conne= ction up [laptop]. On this desktop, which had a network disconnect at under two hours and unde= r 4 hours, within the last twenty-four hours or so, it has now, at least once, had the network reliable for over six hours.=20=20 I've yet to do two other tests ( outage wholly across the lan and a differe= nt driver ) but hoping for this workaround to be feasible...=