Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt 3.8.8-4 released
Date: Sun, 2 Jun 2013 20:00:44 +0200	[thread overview]
Message-ID: <CAMZR1YDFOwN=2x3d14buBNNXfHB7G1yhUko2LL0=pBGL2m6O4Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4VER2eQ_ak+SZQtGrBNbpmm-WZyA5Shehqq86mFy-MdA@mail.gmail.com>

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

Hi Dave,

I installed 3.8.8-4 more than a month ago but it took me this long to give
up  trying to get DLNA working.
For some reason those DLNA discovery (SSDP) multicasts seem not forward
between se00 and sw00 or sw10 so the devices cannot find themselves. This
is supposed to be done by minissdpd.

I know previously we've had it broken but you fixed it by adding some
missing config in the kernel for IGMP I believe.
But I'm unable to find the cause this time.

Would you suggest I have a go with a more recent cero release or does
anything come to mind when I describe the issue?

Best regards,
Maciej Soltysiak

On Wed, Apr 24, 2013 at 10:55 AM, Dave Taht <dave.taht@gmail.com> wrote:

> + Refresh to openwrt barrier breaker head
>
>    this now contains nearly all the patches formerly separately in cerowrt!
>
>    ++ fq_codel is on by default on ALL interfaces with default quantum of
> 300
>         (yes, openwrt has obsoleted pfifo_fast!)
>    ++ unaligned access patches, etc, etc
>    + dhcp-pd SERVER support
>  the usual multitude of other openwrt fixes... all tested extensively
> at the battlemesh conference.
>
> + Update to dnsmasq 2.67test2
>
> Toke got really busy in building his own version of cero and adding
>
> + AQM scripts and gui
> + tahoe-lafs added (untested)
> + uftp4 updated
>
> - no upnp/ssdp fix because I'm clueless
>
> Yep, "AQM" gui now. /deep hat tip to toke for writing that. No need to
> fiddle with any scripts now....
>
> I guess of largest import here, underlying the gui, is that I had a
> chance to deeply look at simple_qos.sh. There are several bugs in it,
> that appear actually in the underlying tc subsystem.On ingress, the
> priority queue was not being used properly, and a few other things
> were odd in ipv6.
>
> Out of frustration with that, and based on the data we'd got back from
> cablelabs, I wrote the simplest possible rate limited fq_codel
> implementation, using a reduced number of flows and a single tier of
> htb only - and that works surprisingly well.
>
> It's called "Simplest" in the new AQM screen. Give it a shot.
>
> Secondly, the exercise of writing that and comparing it to the simple_qos
> script
>
> .... seems to have exposed a bug in htb at low bandwidths.
>
> http://snapon.lab.bufferbloat.net/~d/dsl384k-htb-bug.svg
>
> Here I was trying at 384k up and 8Mbit down, and the middle portion of
> the upload graph there is kind of... impossible. At higher rates I
> haven't seen this happen.
>
> --
> 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: 3731 bytes --]

  parent reply	other threads:[~2013-06-02 18:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  8:55 Dave Taht
2013-04-24  8:55 ` Dave Taht
2013-04-24 14:07 ` Maciej Soltysiak
2013-04-24 15:56   ` Dave Taht
2013-04-25  0:06     ` Rich Brown
2013-04-25  5:56       ` Dave Taht
2013-04-25 14:04         ` Maciej Soltysiak
2013-04-25  7:45       ` Toke Høiland-Jørgensen
2013-06-02 18:00 ` Maciej Soltysiak [this message]
2013-06-02 18:12   ` 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='CAMZR1YDFOwN=2x3d14buBNNXfHB7G1yhUko2LL0=pBGL2m6O4Q@mail.gmail.com' \
    --to=maciej@soltysiak.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