From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] upnpd problem semi-solved
Date: Wed, 29 Jan 2014 20:54:26 +0100 [thread overview]
Message-ID: <CAMZR1YC2d9bg=JqiHOUaws54dFkV1QKh43eSYNXTkLiBxwt-uw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw78s5y176=pY_sYKuX=mV1EBXj4fmJUZerkuZy5454aJA@mail.gmail.com>
DLNA discovery is using SSDP. SSDP are multicasts which don't easily
traverse between interfaces.
minissdp is supposed to proxy between interfaces. I think it also
keeps track of the devices so it can respond on behalf of other
devices.
I'm running 3.10.18-1. If there's a build you would suggest I try, I'm
happy to do it.
On Wed, Jan 29, 2014 at 7:19 PM, Dave Taht <dave.taht@gmail.com> wrote:
> 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2014-01-29 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 16:55 Dave Taht
2014-01-29 17:25 ` Paul Handly
2014-01-29 18:19 ` Dave Taht
2014-01-29 19:54 ` Maciej Soltysiak [this message]
2014-01-30 15:06 ` 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='CAMZR1YC2d9bg=JqiHOUaws54dFkV1QKh43eSYNXTkLiBxwt-uw@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