[mythtv-commits] Ticket #10243: "No UPnP" error appears on every other PPA update
MythTV
noreply at mythtv.org
Sat Jan 21 23:04:30 UTC 2012
#10243: "No UPnP" error appears on every other PPA update
-------------------------------------+-------------------------
Reporter: tehowe@… | Owner: dblain
Type: Bug Report - General | Status: closed
Priority: minor | Milestone: unknown
Component: MythTV - UPnP | Version: 0.24.1
Severity: medium | Resolution: Invalid
Keywords: upnp | Ticket locked: 0
-------------------------------------+-------------------------
Comment (by tehowe@…):
It took me a while to make some new observations, but I didn't think the
packaging had anything to do with it.
So sure enough, once the most recent update for MythTV was pushed out, my
backend was again no longer visible to the remote frontends on the
network. This time I had gupnp handy, and was able to watch the uPNP
activity on each box.
On this most recent version of MythTV (0.24.1-126) switching my VPN on or
off is *another* way to disable MythTV's uPNP functionality. However,
running the gupnp control monitor is enough to somehow kick the connection
into an active state again, and all my frontend devices can see it.
Installing an update is probably disruptive in the same way flipping my
VPN on is. (Once gupnp is running, however, I can use my server box either
on the VPN or off, it seems irrelevant to the local network IP)
That doesn't seem like a downstream error, but a uPNP implementation issue
- this bug should be open.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/10243#comment:2>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list