*** This bug is a duplicate of bug 817412 ***
https://bugs.launchpad.net/bugs/817412
Oh, hey, this _is_ a duplicate!
Looks like gupnp is meant to autodetect a network interface, and that is
not working in this case. (It ends up using lxc's lxcbr0 interface).
There is another bug report where
@Dylan,
thanks for reporting this bug. Before I dive deeper, do you already
know why lxc-net is doing this? Is the other package installing a
dnsmasq that binds to all interfaces?
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu)
Status: New => I
I thought this might be some configuration file mixing things up, but
actually it's the lxc-net service. As long as lxc-net is running, this
problem occurs. As soon as I run service lxc-net stop, upnp-router-
control works happily.
I'll add lxc to this, because this effect doesn't appear to be
doc
