From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id E2DF621F0FA for ; Wed, 11 Dec 2013 10:30:38 -0800 (PST) Received: by mail-oa0-f47.google.com with SMTP id k1so7694287oag.6 for ; Wed, 11 Dec 2013 10:30:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=cz5ZBF3sLm3TZVzKNbgHN7rKYAmTrZqiUlnAwLzmst4=; b=hoBucQPd3ke4BlPqyPuTV1A+f12T3/zcY9ip/UUSGuTFO3ykT06a9Yn06GLzaC/v/H pFrUNxRV5vA7/qVtGG8Q4crkRDSMTQoY+mLoF7F+dy9VwqPDA+h7/iAiipnKqeRRy5RJ gm1UKAYddSaug2lAYBlE1T9UtJT0v/EBARbHdhmD8rF/FPYw8bFm/kWmoS5HoItnGbr/ Tc5L8LRGrWD3hQMLKHaBqQ6+SstqBFLDgoGFjpokQatgA56pNR2ZHiD5ju+KLv81Blnn 8H70mskER9XOVikq+ZeaezOEKMdFuweGxec5Ze6HjZUBrVxywRIXDQNnJipcb4847HoO ZW4Q== X-Received: by 10.182.29.66 with SMTP id i2mr2250700obh.23.1386786637847; Wed, 11 Dec 2013 10:30:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.38.194 with HTTP; Wed, 11 Dec 2013 10:30:17 -0800 (PST) In-Reply-To: <20131211085813.57b27abe@nehalam.linuxnetplumber.net> References: <20131211085813.57b27abe@nehalam.linuxnetplumber.net> From: David Personette Date: Wed, 11 Dec 2013 13:30:17 -0500 Message-ID: To: Stephen Hemminger Content-Type: multipart/alternative; boundary=001a11c2bbdceda51d04ed466c33 Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Wireless failures 3.10.17-3 X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2013 18:30:39 -0000 --001a11c2bbdceda51d04ed466c33 Content-Type: text/plain; charset=UTF-8 I've seen similar (not necessarily on 3.10.17-3) on earlier versions of cerowrt and openwrt. And a co-worker has had it happen on dd-wrt. The solution (band-aid / work around / hack) was to restart dnsmasq on the router. I added a line to crontab (included below) to do it preemptively and haven't seen the problem manifest in close to a year now. # restart dnsmasq at 03:17 every morning: 17 3 * * * /etc/init.d/dnsmasq restart I never found anything useful in the logs, or any better way to reproduce it than wait between 2-7 days for devices to stop working. If I'd had better luck coming up with a cause / error message, I'd have logged an error, but felt embarrassed to. Not I'm sorry that I didn't share what I found to help others that it was affecting. I initially just rebooted the router when it flared up, but eventually got fed up and tried restarting daemons one at a time till things worked again. Hope this helps. -- David P. On Wed, Dec 11, 2013 at 11:58 AM, Stephen Hemminger < stephen@networkplumber.org> wrote: > Has anyone seen wireless failing after several days with 3.10.17-3? > > The symptoms are devices fall off the net several days (or a week) after > router has been running. I saw the bg AP go away, but the 5 Ghz AP still > working. Wired attachment works. > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > --001a11c2bbdceda51d04ed466c33 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've seen similar (not necessarily on 3.10.1= 7-3) on earlier versions of cerowrt and openwrt. And a co-worker has had it= happen on dd-wrt.

The solution (band-aid / work around / hack= ) was to restart dnsmasq on the router. I added a line to crontab (included= below) to do it preemptively and haven't seen the problem manifest in = close to a year now.

# restart dnsmasq at 03:17 every morning:
17 3 * * *= =C2=A0=C2=A0=C2=A0 /etc/init.d/dnsmasq restart

I never found anything u= seful in the logs, or any better way to reproduce it than wait between 2-7 = days for devices to stop working. If I'd had better luck coming up with= a cause / error message, I'd have logged an error, but felt embarrasse= d to. Not I'm sorry that I didn't share what I found to help others= that it was affecting. I initially just rebooted the router when it flared= up, but eventually got fed up and tried restarting daemons one at a time t= ill things worked again. Hope this helps.

--
David P.


On Wed, Dec 11, 2013 at 11:58 AM, St= ephen Hemminger <stephen@networkplumber.org> wrote:=
Has anyone seen wireless failing after sever= al days with 3.10.17-3?

The symptoms are devices fall off the net several days (or a week) after router has been running. I saw the bg AP go away, but the 5 Ghz AP still working. Wired attachment works.
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel

--001a11c2bbdceda51d04ed466c33--