Bug 179570

Version:           3.1.4 (using Devel)
OS:                Linux
Installed from:    Compiled sources

Hi,

I'm having a strange upnp behaviour ktorrent (kde4) when it's used with an a/v upnp media server, in this specific case, mediatomb.

I have:
- KDE4 4.1.85 (4.2 Beta2), Ktorrent 3.1.5
- KDE3 3.5.10, Ktorrent 2.2.7
- Portable UPnP library, pupnp 1.6.6
- aMule 2.2.3 (latest stable) compiled with pupnp 1.6.6
- mediatomb 0.11.0 compiled with pupnp 1.6.6

Symptoms:

A) When ktorrent of KDE4 is already running and has captured udp port 1900, and if I start  mediatomb afterwards, mediatomb fails to run.

This behaviour does not occur if I run the ktorrent of KDE3 with upnp plugin. So the bug is definetely in the implementation of upnp in KDE4 ktorrent.

B) When amule is already running and has captured udp port 1900 (ssdp), and if I start mediatomb afterwards, no problems.

C) When mediatomb is already running and has captured udp port 1900, and if I start ktorrent or aMule, all run perfectly OK.

My guess is that ktorrent is capturing UDP port 1900 (SSDP) exclusively that Mediatomb can't bind to it afterwards, to serve as an A/V UPnP Media Server on the lan.

If mediatomb is started before ktorrent, then I can see these lines in netstat output:

udp        0      0 0.0.0.0:1900            0.0.0.0:*                           18781/mediatomb
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           18880/ktorrent

However, if ktorrent (kde4) is started earlier, than mediatomb refuses to run.

Thanks,

Emre (Pardus 2008)