From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (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 D5B1921F1B0 for ; Thu, 3 Apr 2014 15:56:37 -0700 (PDT) Received: by mail-ie0-f171.google.com with SMTP id ar20so2599004iec.16 for ; Thu, 03 Apr 2014 15:56:37 -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; bh=hM7zCERLWAMqiugKGGY43H6+tIWRi9hiW9Yl2TBIL0Y=; b=MhFJHenGqhWH+DnZyGxvps971GfUJ3aZJ3D7yXgjBeYqXHV2E4KpOOC8HtcjZgxPAh qhg+UjYb3ex0ZE3jF8ZdBN77kx49DlktgFBd8UDyBkC0vdmoQ3FhUJenjyaXDkJggKUG fSiyIefWtK2WWrbfw8BU8tZERyoyBl1Px2ST+nYKRropNbVyjJ8NNQIR27jYRlvfeKIl sHDynZQPpr2uRDQ0oXDXF8/AryIkN55LfCOQGqDe5ydEQ3e7tfUrdIctNI8xaVZ+zunl Dby30sCw3HIda1X30Kq3GwL/rYCrq821WOv9i7M9s2N4Zx5FGhs/j3XFFmeXAXctMB33 DvfA== MIME-Version: 1.0 X-Received: by 10.50.154.73 with SMTP id vm9mr5081759igb.14.1396565797060; Thu, 03 Apr 2014 15:56:37 -0700 (PDT) Received: by 10.64.238.70 with HTTP; Thu, 3 Apr 2014 15:56:36 -0700 (PDT) In-Reply-To: References: <533DA665.2050305@gmail.com> Date: Fri, 4 Apr 2014 00:56:36 +0200 Message-ID: From: Aaron Wood To: Maxim Kharlamov Content-Type: multipart/alternative; boundary=047d7bd75ecc3d4a5304f62b50d6 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:56:38 -0000 --047d7bd75ecc3d4a5304f62b50d6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Up for 10 days on 3.10.32-12 (WNDR3800). Only have 2 devices that run 2.4GHz, and it's only seen 2GB of traffic on SW00 in that time... The 5GHz radio has had >5GB of traffic on it in the same time. No problems at all. -Aaron On Fri, Apr 4, 2014 at 12:51 AM, 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 >> > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > --047d7bd75ecc3d4a5304f62b50d6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Up for 10 days on 3.10.32-12 (WNDR3800). =A0Only have 2 de= vices that run 2.4GHz, and it's only seen 2GB of traffic on SW00 in tha= t time... =A0The 5GHz radio has had >5GB of traffic on it in the same ti= me. =A0No problems at all.

-Aaron


On Fri, Apr 4, 2014 at 12:51 AM, Maxim Kharlamov <mcs@= podsolnuh.biz> wrote:
The last release without wi= fi issues was 3.8.something (I think it was called Berlin). The whole 3.10.= x branch seems to have broken wifi (will see how 3.10.24-4 goes, it seems O= K, but it's been working less than 24hours yet).
I'm using only 2.4Ghz (5Ghz dead in the water - devices couldn't co= nnect at all, so I disabled it). Guest and babel disabled.


Reg= ards,
Max


On Fri, Apr 4, 2014 at 11:36 AM, Dave Ta= ht <dave.taht@gmail.com> 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 &qu= ot;best"
releases this year...)

Worst case we can step back to that kernel for a while and proceed forward<= br> 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 exam= ple
no longer have a mac to test with)


On Thu, Apr 3, 2014 at 11:20 AM, Neil Shepperd <nshepperd@gmail.com> wrote:
> I just flashed 3.10.34-4 to my new WNDR3800 and experienced the exact<= br> > wifi hang described by Toke H=F8iland-J=F8rgensen. But I'm on the = 2.4GHz
> network (with guest and babel disabled). Unfortunately I didn't th= ink 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 continuo= usly
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 captu= res,
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/subscrib= e.html
_______________________________________________
Cerowrt-devel mailing list
Ce= rowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel


_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel


--047d7bd75ecc3d4a5304f62b50d6--