Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt 3.7.1-1 released
Date: Thu, 3 Jan 2013 13:50:05 -0500 (EST)	[thread overview]
Message-ID: <1357239005.383531290@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw5ykg34quKAc2dDEM7HbyrGZ+-ZEstvJjkKe4YnFORaYA@mail.gmail.com>

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


Perhaps this is premature, but I have installed 3.7.1-1 on my experimental router as well.  It seems to be working fine but now I'd like to start capturing monitoring data from the AQM (nfq_codel is enabled by default?) layer.
 
I'd also like to change the "WAN interface" to be one of its 2.4 Gig radios.  That's because I want to put the Cerowrt experimental router "in front of" a mobile hotspot that is operating using LTE to provide my internet access.  (Yes, I know that "in general" WLAN's need something better than nfq_codel, but in this case, it's a single device and a single hop - i.e. cable equivalent).  Alternatively, maybe I can connect the mobile hotspot to the router using USB.
 
Best way to do that?  I have not delved deep into OpenWRT/Cerowrt config files.
 
-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Wednesday, January 2, 2013 5:03am
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] cerowrt 3.7.1-1 released



Two formerly back-ordered 3800s arrived yesterday!

They barely had time to power on before I reflashed them with:

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.1-1/

I still regard this series as heavily development oriented and
unsuitable for general use. In particular I'd like to wait for dnsmasq
to come out of beta, fix AHCP, add a gui for the ceroshaper, etc, etc.

But: This is the first devel release I've been able to test in the
real world as a default gw in a while. So far, so good.

I have some issues with how the new network6 configuration stuff
interacts with ahcp, but aside from that... I saw upnp work for the
first time... saw the ula auto code work... analyzed some dropbox and
netflix traffic, ran a couple android boxes through it, fiddled with
nfq_codel...

some notes:

+ resync with openwrt head
+ update to Linux 3.7.1 with unaligned patches from robert bradley
+ A QFQ+ update
+ mildly improved nfq_codel
- Missing cups support (didn't compile
- no ipv6 npt yet

Merry New Year!

-- 
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: 2895 bytes --]

  parent reply	other threads:[~2013-01-03 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02 10:03 Dave Taht
2013-01-03 16:54 ` Ketan Kulkarni
2013-01-03 18:50 ` dpreed [this message]
2013-01-03 19:30   ` Dave Taht
2013-01-03 19:44     ` dpreed
2013-01-03 20:02       ` Dave Taht
2013-01-03 23:47         ` dpreed
2013-01-04  0:31           ` 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=1357239005.383531290@apps.rackspace.com \
    --to=dpreed@reed.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