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.3.8-1 and related
Date: Thu, 14 Jun 2012 19:36:11 +0200	[thread overview]
Message-ID: <CAMZR1YCPLTHkNZhZfNCFeSoEXzsuC2DBauMkS36s-1fGUZSgDQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7BigjWe1_RJQ1Hs-GMvsoOkZMGLvH00o9BoHcYaF_mGw@mail.gmail.com>

Hi Dave,

Cool, just flashed my router with the 3.3.8-3, going to use it at home.

About codel, does it mean that I shouldn't enable anything in AQM and
QOS tabs and just edit
/usr/sbin/simple_qos.sh to tune my down/up bandwidth?

Regards,
Maciej

On Fri, Jun 8, 2012 at 4:54 PM, Dave Taht <dave.taht@gmail.com> wrote:
> there is at least one mistake in the current firewall rules. the "lan" rule
> for se00, sw10, sw00 should have ACCEPT on input,output,and forward.
>
> Plenty more fixes to come by the end of the weekend.
>
> On Fri, Jun 8, 2012 at 5:19 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> I have updated cerowrt 3.3 to Linux version 3.3.8-1 and merged with
>> openwrt head.
>>
>> My goal for this release was simply to get caught up with openwrt, then push
>> out the remaining useful cerowrt stuff into openwrt. After taking 3 weeks
>> off it's amazing how difficult it was to get back in sync.
>>
>> Changes in this release:
>>
>> + Linux 3.3.8
>> + netifd support (more dynamic application startup/shutdown management)
>> + Bind 9.1.1-P1 (Fix for a CVE)
>> + transmission and transmission web server (uTP) added
>> + Jabber chat server added
>>
>> - I accidentally took a step back on dnsmasq (2.61 to 2.59)
>> - Firewall rules still need work (transmission support, block port 81, too)
>> - High performance hang (#379 and friends) untested (but possibly improved)
>> - UPnP work needs to be folded in
>> - quagga and gpsd didn't build
>>
>> There are exciting things happening on the quagga front with babel -
>> there is a security architecture being prototyped as I write that
>> looks promising.
>> As for the gpsd issue, there was a flurry of controversy over how best
>> to stick it in openwrt, and obviously whatever one I picked lost.
>>
>> And, of course, fq_codel is running on all interfaces.
>>
>> I will try to resolve these issues by sunday and get out a 3.3.8-2
>>
>> Let me know if any new ones have cropped up.
>>
>> --
>> Dave Täht
>> SKYPE: davetaht
>> http://ronsravings.blogspot.com/
>
>
>
> --
> Dave Täht
> SKYPE: davetaht
> http://ronsravings.blogspot.com/
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

  reply	other threads:[~2012-06-14 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 12:19 Dave Taht
2012-06-08 14:54 ` Dave Taht
2012-06-14 17:36   ` Maciej Soltysiak [this message]
2012-06-14 18:37     ` 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=CAMZR1YCPLTHkNZhZfNCFeSoEXzsuC2DBauMkS36s-1fGUZSgDQ@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