http://bugzilla.suse.com/show_bug.cgi?id=1132829 http://bugzilla.suse.com/show_bug.cgi?id=1132829#c3 --- Comment #3 from Sebastien Chavaux <seb95passionlinux@opensuse.org> --- The trouble comes from upnp (libupnp 13), see the bug for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932460 https://github.com/mrjimenez/pupnp/issues/91 due to the --enable-reusaddr option ...

When libupnp is configured with --enable-reuseaddr, it does not retry with a different port if the default one (49152) is busy.

This makes it difficult to run multiple apps (e.g. renderer + control point or multiple control points) on the same host. The second libupnp-based application fails if it tries to use the default port. The only workaround would be to manually configure different ports, but this is a major regression compared to the current situation where the next available port is just used.

There is no contradiction between setting reuseaddr, so that a restart of a single application will use the same port (which can help with firewalls etc.), and also trying the next available value if the first one is actually busy.

Debian and Ubuntu already package the library with --enable-reuseaddr so this is a major issue.

You have to patch upnp to fill this known bug. In the archive for debian de deb-multimedia, christian made a patch: https://deb-multimedia.org/dists/unstable/main/binary-amd64/package/libupnp1... I took it back to put it in the openSUSE package. I am not sure of myself, so I allow myself to transmit here the original patch. Thanks for correcting the worries on libupnp13. -- You are receiving this mail because: You are on the CC list for the bug.