Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Issues with 5ghz after a couple of days' uptime
Date: Fri, 28 Mar 2014 17:51:09 +0100	[thread overview]
Message-ID: <CALQXh-OJxGDmQkxDmNqFZi1=fTC3njmM0vjtD9-yg-YRbtxUrg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4Wz_DywsbqCSyrcONZOezsxjaG=g8uf53pE94mHp+Brg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]

As a contra-datapoint:

4d uptime here, but without any ipv6.  A couple GB of data, both
WAN<->internal, and between 5GHz devices (pushing to an AppleTV).  No real
traffic between 2.4 and 5GHz, though.

WPA2 on all interfaces (babel and guest interfaces are disabled).

-Aaron

On Fri, Mar 28, 2014 at 5:39 PM, Dave Taht <dave.taht@gmail.com> wrote:

> This sounds like the problem jim gettys is having on 2.4ghz. It takes
> 1+ days to happen. We've ruled out ipv6 tunneling and syns as the
> cause... he is presently running without syn flood, ipv6, and now WPA
> support in the hope that that's a cause (there is a fix for WPA stuff
> in 3.10.34 pending)
>
> are you using WPA?
>
> taking a long term packet capture seems worthwhile.
>
>
> On Fri, Mar 28, 2014 at 1:04 AM, Toke Høiland-Jørgensen <toke@toke.dk>
> wrote:
> > So I've had a strange issue with the 5ghz network on my wndr after a few
> > days' uptime: Packets stopped getting through on the 5ghz network. I.e.
> > clients already connected could no longer connect to anything, and
> > trying to connect a new client resulted in the wlan association
> > succeeding, but the clients failing to get a DHCP lease.
> >
> > There's nothing in the logs to indicate what might be wrong (no DMA
> > errors or anything like that). 'logread' shows dnsmasq receiving and
> > replying to DHCP requests, but the answers never reach the clients.
> >
> > Restarting the wireless (i.e. running 'wifi') fixed it.
> >
> > Any ideas? I'm on 3.10.32-12(ish). Built from git commit
> > 9bbc728cb7508dce24c480ac63d6e4f63d5c02f5 from the cerowrt-3.10 repo. :)
> >
> > -Toke
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >
>
>
>
> --
> Dave Täht
>
> 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
>

[-- Attachment #2: Type: text/html, Size: 3239 bytes --]

  reply	other threads:[~2014-03-28 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28  8:04 Toke Høiland-Jørgensen
2014-03-28 16:39 ` Dave Taht
2014-03-28 16:51   ` Aaron Wood [this message]
2014-03-28 18:04     ` David Personette
2014-03-28 18:48   ` Toke Høiland-Jørgensen
2014-03-28 19:32     ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALQXh-OJxGDmQkxDmNqFZi1=fTC3njmM0vjtD9-yg-YRbtxUrg@mail.gmail.com' \
    --to=woody77@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox