Re: [Cerowrt-devel] upnpd problem semi-solved

[Dave Taht <dave.taht@gmail.com>]

Well, I see ipv6 support in the current codebase, don't know if it's
in the codebase I'm trying now...

my understanding of the separate minissdp server was that it acted as
an arbitrator between
multiple possible users of the functionality (like dlna)

On Wed, Jan 29, 2014 at 9:25 AM, Paul Handly <paul@hand.ly> wrote:
> SSDP registration (server) and subsequent discovery (client) across
> subnets was what I needed minissdpd for, but the devices I was trying to
> drive (Sonos) are kind of pricey as a test case.
>
> Having an IPv6 address on the listen interface/s broke the old build of
> minissdpd, so I had to choose between IPv6 and Sonos.
>
> --
> Paul Handly <paul@hand.ly>
>
> On Wed, Jan 29, 2014, at 11:55, Dave Taht wrote:
>> The version I was carrying in ceropackages was obsolete and didn't
>> integrate
>> into fw3. Dropped that release, built from openwrt head, I can open ports
>> now
>> from the transmission bittorrent client and from dns-sd (on macos) now.
>>
>> the author tells me the latest version (not what I built, it's only a
>> few days old) does PCP also.
>>
>> 1) It's not clear to me why minissdpd was needed?
>>
>> 2) Are there any other test cases I could try?
>>
>> --
>> 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



-- 
Dave Täht

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