Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt@lists.bufferbloat.net,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bug #442] wifi fails to transmit traffic after a few hours
Date: Sat, 05 Apr 2014 22:54:11 -0400	[thread overview]
Message-ID: <67283.1396752851@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 05 Apr 2014 09:33:45 -0700." <CAA93jw6H2hDvEtiVgyBDOjT6VKXOBdaTAKfc7Rfk30uy6z0qSQ@mail.gmail.com>

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

On Sat, 05 Apr 2014 09:33:45 -0700, Dave Taht said:
> The  above  subject line and cc  will  get this conversation  into
> the bug  tracker.

I've never managed to have the wifi lock up on my 3800.

root@bogon-gateway-1:~# cat /etc/openwrt_release
DISTRIB_ID="CeroWrt"
DISTRIB_RELEASE="3.10.36-1"
DISTRIB_REVISION="r40387"
DISTRIB_CODENAME="toronto"
DISTRIB_TARGET="ar71xx/generic"
DISTRIB_DESCRIPTION="CeroWrt Toronto 3.10.36-1"
DISTRIB_TAINTS="no-all busybox"
root@bogon-gateway-1:~# uptime
 20:53:11 up  3:05,  load average: 0.16, 0.30, 0.39
root@bogon-gateway-1:~#  egrep -i "country|channel|htmode" /etc/config/wireless
        option channel '11'
        option country 'US'
        option channel '36'
        option country 'US'

(Upstream to comcast is a nominal 10mbit down/2 mbit up)

root@bogon-gateway-1:~# sh ./betterspeedtest.sh -H netperf6.richb-hanover.com
Testing against netperf6.richb-hanover.com while pinging gstatic.com (60 seconds in each direction)
.............................................................
 Download:  7.66 Mbps
  Latency: (in msec, 61 pings, 0.00% packet loss)
      Min: 16.824 
    10pct: 20.281 
   Median: 24.838 
      Avg: 25.469 
    90pct: 30.937 
      Max: 37.476
.............................................................
   Upload:  2.21 Mbps
  Latency: (in msec, 61 pings, 0.00% packet loss)
      Min: 19.125 
    10pct: 21.770 
   Median: 26.363 
      Avg: 26.392 
    90pct: 30.478 
      Max: 34.852
root@bogon-gateway-1:~# sh ./betterspeedtest.sh -H netperf.richb-hanover.com
Testing against netperf.richb-hanover.com while pinging gstatic.com (60 seconds in each direction)
............................................................
 Download:  8.09 Mbps
  Latency: (in msec, 61 pings, 0.00% packet loss)
      Min: 17.153 
    10pct: 20.290 
   Median: 24.304 
      Avg: 24.855 
    90pct: 29.817 
      Max: 40.293
.............................................................
   Upload:  2.24 Mbps
  Latency: (in msec, 61 pings, 0.00% packet loss)
      Min: 21.306 
    10pct: 23.127 
   Median: 25.968 
      Avg: 26.374 
    90pct: 30.681 
      Max: 33.517


[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

      parent reply	other threads:[~2014-04-06  2:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05 16:33 Dave Taht
2014-04-05 22:55 ` David Personette
2014-04-05 23:48   ` Chuck Anderson
2014-04-06  2:35 ` Neil Shepperd
2014-04-06  2:54 ` Valdis.Kletnieks [this message]

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=67283.1396752851@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt@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