Date: Sun, 24 Apr 2016 23:15:41 -0700 (PDT) From: "Jeffrey Bouquet" <jbtakk@iherebuywisely.com> To: "current" <current@freebsd.org> Cc: "jbtakk" <jbtakk@iherebuywisely.com>, "kernel" <kernel@dollarmusicdownload.com> Subject: Re: nfe0 connection not as reliable; a few questions... Message-ID: <E1auZo5-0004ao-SC@rmm6prod02.runbox.com> In-Reply-To: <E1auA6I-0000fp-5h@rmm6prod02.runbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 23 Apr 2016 19:48:46 -0700 (PDT), "Jeffrey Bouquet" <jbtakk@iherebu= ywisely.com> 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...=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1auZo5-0004ao-SC>