Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Paul Handly <paul@hand.ly>
To: Dave Taht <dave.taht@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] upnpd problem semi-solved
Date: Wed, 29 Jan 2014 12:25:31 -0500	[thread overview]
Message-ID: <1391016331.21340.76849577.4C0BB967@webmail.messagingengine.com> (raw)
In-Reply-To: <CAA93jw4tyvjEFgJowm3qm8w7K6DV-y857Fx9FDarGWy4+ic0wg@mail.gmail.com>

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

  reply	other threads:[~2014-01-29 17:25 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 [this message]
2014-01-29 18:19   ` Dave Taht
2014-01-29 19:54     ` Maciej Soltysiak
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=1391016331.21340.76849577.4C0BB967@webmail.messagingengine.com \
    --to=paul@hand.ly \
    --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