From: Stephen Walker <stephendwalker@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] next cerowrt release plan (of sorts)
Date: Mon, 17 Sep 2012 22:35:23 -0400 [thread overview]
Message-ID: <CAH7PtXz899094HoySu8RSd63wdoxAr++09BYaPNXZoGQrri8wQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6z9D2+1gRJgzPyG+CppxahuNf8MHB=C_u30BBp=Qu9LQ@mail.gmail.com>
On Mon, Sep 17, 2012 at 3:53 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Sun, Sep 16, 2012 at 11:48 AM, Maciej Soltysiak <maciej@soltysiak.com> wrote:
>> On Sun, Sep 16, 2012 at 4:02 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>> Other things in my backlog are two multicast responder-like daemons -
>>> but can't remember their names mldna?
>> It was minissdpd and miniupnpd, which are pre-requisites for allowing
>> minidlna to work between multiple network segments like we have in
>> cerowrt with 172.30.42.X/Y/Z...
>>
>> What needs to be done is:
>> 1) add minissdpd and miniupnpd to the build
>> 2) patch their default configs to cater for lan->se00 sw00 sw10 and wan->ge00
>>
>> miniupnpd will also allow portforwarding negotiation for things like
>> IM clients and, say, uTorrent. Also, it will score in netalyzr support
>> for UPNP.
>>
>>> If you have trivial feature requests, please make 'em now!
>>> If you have code you want to check in, please get them in by tuesday!
>> See attached CRLF file. Since I had trouble and low patience for
>> getting a normal cero build to even get a new package in, sorry for
>> sending non-patch file with instructions. If it's unacceptable, please
>> let me know, I'll try to juggle time to try again.
>>
>> p.s. have fun in Sugarland :-)
>
> I see that a minidlna package is in the main package feed for openwrt,
> but it doesn't want to feeds install. The version you pointed me at in
> the previous mail is someone's checkout of another feed. It would be
> more fruitful to have this be working in openwrt first....
>
> It could be that my feeds database is borked?
>
> same goes for sdpd. I'd kind of prefer the maintainer of the package
> push it out into openwrt mainline, or make it available as an official
> alternate feed I can pull a checkout from in cerowrt, rather than copy
> directly into ceropackages.
>
> Does "trondah" have a public email addy?
>
> cc-ing our packager emeritus...
Cshore would be the person to ask as he maintains miniupnpd and also
owns https://dev.openwrt.org/ticket/8988 for minissdpd.
>>
>> Regards,
>> Maciej
>
>
>
> --
> Dave Täht
> http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
> with fq_codel!"
next prev parent reply other threads:[~2012-09-18 2:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 14:02 Dave Taht
2012-09-16 18:48 ` Maciej Soltysiak
2012-09-17 19:53 ` Dave Taht
2012-09-18 2:35 ` Stephen Walker [this message]
2012-09-17 17:02 ` Török Edwin
2012-09-17 17:04 ` Török Edwin
2012-09-17 17:24 ` Dave Taht
-- strict thread matches above, loose matches on Subject: below --
2012-07-26 16:28 Dave Taht
2012-07-30 17:31 ` Michael Richardson
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=CAH7PtXz899094HoySu8RSd63wdoxAr++09BYaPNXZoGQrri8wQ@mail.gmail.com \
--to=stephendwalker@gmail.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