UPNP does not start correctly

[gdupasqu]

Hello,

Details for:

1) Ubuntu: 8.04
2) Package: libupnp2:
  Installed: 1.4.3-2
  Candidate: 1.4.3-2
  Version table:
 *** 1.4.3-2 0
3) Discovering of devices on the network
4) No device discovered

I call the function upinit and then wait for events on the network such as new devices.
After a while nothing happened.

But as soon as I start wireshark and make capture on eht0 network interface then
the devices are discovered in upnp.

Then I close my program, close wireshark and start my program again and it works
discovering new devices.

I have also tried to run my program with root priveleges (sudo) but it did not fix the bug.

It might be related to a driver loaded by wireshark which is not done by default.
I work on ubuntu 8.04 with libunp2.

Thank in advance for your help,

Guillaume

[Nick Leverton (nick-leverton)]

Sounds like it could be a multicast problem. I have had similar with a Broadcom Wifi chipset whose drivers don't properly do multicast.

I realise this is an old bug, I didn't check for historical ones last time I tidied up this package, but in case I can still help -

- first thing to check, have you set up your multicast interface correctly ? If you are running libupnp as part of a server so that it can advertise itself, then you need to do this. You should have a route to 239.0.0.0/8, or possibly 224.0.0/4. Do "sudo ip route ls" to check. (If you use multicast in your network for purposes other than service discovery then you will need both, in this case give me more details).

- second thing to check - is it a problem with your network adaptor's multicast handling ? Some WLAN cards, for instance, don't support multicast unless placed into promiscuous mode. Check this by repeating your wireshark test but make sure "promiscuous mode" is unticked in the interface selection dialogue. If this *doesn't* cause libupnp to detectyour devices then you need to look into your network drivers

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.