Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt 3.10.17-3 released
Date: Mon, 21 Oct 2013 19:10:36 -0700	[thread overview]
Message-ID: <CAA93jw5QfTvS7ZDeAWPY5h2OuXxxGSqaEiJQ1J0KOtDhm+ePBg@mail.gmail.com> (raw)
In-Reply-To: <20131021183429.4c79d8d8@nehalam.linuxnetplumber.net>

On Mon, Oct 21, 2013 at 6:34 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Mon, 21 Oct 2013 14:04:24 -0700
> Dave Taht <dave.taht@gmail.com> wrote:
>
>> On Mon, Oct 21, 2013 at 1:45 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> > + this fixes the lighttppd bug noted in -2.
>> > + has support for signed packages
>> > + better random support
>> > + tested long enough to check for the -2 regression
>> >
>> > - doesn't do https yet
>> > - still abuses rc.local for starting up late daemons
>> > - sysupgrade still busted, please use this to upgrade:
>> >
>> > mtd -r write openwrt-ar71xx-generic-wndr3700v2-squashfs-sysupgrade.bin
>> > firmware # but with the correct firmware name
>> >
>> > Get it at:
>> >
>> > http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.17-3/
>> >
>> >
>> > --
>> > Dave Täht
>>
>> Also, I added optional support for the mildly misnamed port-mirroring package
>>
>> http://code.google.com/p/port-mirroring/
>>
>> It's not very fast so I don't think it's useful for much on this arch.
>>
>> I have tagged and pushed out the sources for this release also. There
>> are very few things left that are truly bothersome (besides
>> sysupgrade), and most are landing this week (notably pie).
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
> This is the slowest way to implement SPAN, in userspace using libpcap.
> The fastest is to use tc mirred action but no one seems to know about it.

And still don't... unless you elucidate?! Do you mean the TEE target?

In this case I was looking to get data from the wifi interfaces to a
server on the
lan, and tzsp seemed the best approach... until it benchmarked out so
darn slow. I don't mind losing the raw data and using the TEE
target...

It would be cool to have a tzsp target though, as that can run on an AP far, far
away from the server.


-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2013-10-22  2:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 20:45 Dave Taht
2013-10-21 21:04 ` Dave Taht
2013-10-22  1:34   ` Stephen Hemminger
2013-10-22  2:10     ` Dave Taht [this message]
2013-10-22 23:12       ` Stephen Hemminger
2013-10-22 23:27         ` Dave Taht
2013-10-22 23:45           ` Stephen Hemminger
2013-10-22  1:27 ` Richard E. Brown

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=CAA93jw5QfTvS7ZDeAWPY5h2OuXxxGSqaEiJQ1J0KOtDhm+ePBg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=stephen@networkplumber.org \
    /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