From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (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 5D9F821F231 for ; Thu, 3 Apr 2014 15:54:46 -0700 (PDT) Received: by mail-pb0-f46.google.com with SMTP id rq2so2516726pbb.5 for ; Thu, 03 Apr 2014 15:54:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+OhGKZMZWiZ0rniAZz/ujFc9nKHvbghZPa6s+lmuSZo=; b=hwoVCrSU/G3XLWO+B8FLWaAki07Q+zNs57/ppIGNry/zsWVE1J083VSmGxLe96Wy9e vWIJ3EHaPzN/NIGcFKRSzEeKdjLbQeM5m/lva6sl7qzeAPOjnR74rTVG30wuBolb4dbZ 4BsUYZXr3D8jp+pFh9jrnDzvgGX2YOiQN8Ih+f79pYxFuUpqO8l0t0qZi2Kf3Z27DA43 v6E0U6GilEeyJhvTa85k+7QlxUnw6bSZH8Trf3Efn+fMizqN9KQIJUGpsHW3DuZd0XB6 iMNCTVhnONPcMHzuNJrfKEXXTH/myB1IP/Trz3uWDnrudIouPgldOSo+GJt1nccf4/as eNcA== MIME-Version: 1.0 X-Received: by 10.68.249.195 with SMTP id yw3mr10669187pbc.134.1396565685952; Thu, 03 Apr 2014 15:54:45 -0700 (PDT) Received: by 10.70.10.197 with HTTP; Thu, 3 Apr 2014 15:54:45 -0700 (PDT) In-Reply-To: References: <533DA665.2050305@gmail.com> Date: Thu, 3 Apr 2014 15:54:45 -0700 Message-ID: From: Dave Taht To: Maxim Kharlamov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] cerowrt-3.10.34-4 dev build released 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: Thu, 03 Apr 2014 22:54:46 -0000 For starters, let me suggest commenting out the multicast_rate parameter from /etc/config/wireless and rebooting. Given an issue with dhcp reported earlier today, that an issue with multicast. On Thu, Apr 3, 2014 at 3:51 PM, Maxim Kharlamov wrote: > The last release without wifi issues was 3.8.something (I think it was > called Berlin). The whole 3.10.x branch seems to have broken wifi (will s= ee > how 3.10.24-4 goes, it seems OK, but it's been working less than 24hours > yet). > I'm using only 2.4Ghz (5Ghz dead in the water - devices couldn't connect = at > all, so I disabled it). Guest and babel disabled. > > > Regards, > Max > > > On Fri, Apr 4, 2014 at 11:36 AM, Dave Taht wrote: >> >> Is there a recent version that people had that was seemingly stable for >> wifi that we could step back to and bisect from? Something where >> you had heavy wifu use for week(s) without a problem? >> >> (I know that until we got focused on this, and people focused on >> reporting it, that maybe it was happening in releases I'd otherwise >> considered to be "pretty good"... so please report in on your "best" >> releases this year...) >> >> Worst case we can step back to that kernel for a while and proceed forwa= rd >> on all the other stuff. I know I crave stability at this point, and I'm >> unhappy that everyone here is unhappy, too... >> >> Regrettably since losing my lab I have not been in a position to easily >> test wifi to any huge extent. I'm slowly building that up (but for examp= le >> no longer have a mac to test with) >> >> >> On Thu, Apr 3, 2014 at 11:20 AM, Neil Shepperd >> wrote: >> > I just flashed 3.10.34-4 to my new WNDR3800 and experienced the exact >> > wifi hang described by Toke H=F8iland-J=F8rgensen. But I'm on the 2.4G= Hz >> > network (with guest and babel disabled). Unfortunately I didn't think = to >> > try tracing anything from the router side before resetting the wireles= s. >> >> cool you disabled guest and babel. So far we've sort of ruled out >> 6in4 tunnelling, and syn flood protection. >> >> Sounds like you are going to stick with -4 for a bit? >> >> what I've been doing is mounting a usb stick, and just running >> continuously >> on the stick >> >> tcpdump -s 128 -i ge00 -w ge00.cap & >> tcpdump -s 128 -i sw00 -w sw00.cap & >> >> This definately hurts performance... >> >> And it's probably time to do a tcpdump on the connected device as well. >> >> In terms of other diags... (any suggestions?) >> >> > Syslog was filled with a lot of >> > >> > DHCPDISCOVER(sw00) [MAYBE IP] [MAC ADDRESS] >> > DHCPOFFER(sw00) [IP] [MAC ADDRESS] >> >> Hmm. OK, this brings back the device driver into the equation... I >> WAS seeing dhcp and arp requests "getting through" from the captures, >> and it seemed like arp in particular was getting through... >> >> > >> > but the offers aren't being received at my laptop. >> > >> > Just another data point I guess. >> >> Well, I'd hoped it would be a confirming one rather than one opening >> up more questions. >> >> > Neil >> > _______________________________________________ >> > Cerowrt-devel mailing list >> > Cerowrt-devel@lists.bufferbloat.net >> > https://lists.bufferbloat.net/listinfo/cerowrt-devel >> >> >> >> -- >> Dave T=E4ht >> >> Fixing bufferbloat with cerowrt: >> http://www.teklibre.com/cerowrt/subscribe.html >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel > > --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html