a separate thread seems reasonable, but...
isn't the upnp stuff needed when sending the inf? or we could treat a client as 
passive until upnp has done its magic and then switch any already logged in 
hubs to active when upnp is done...

as to native vs included, it's a matter of settings in the build script,
and linux isn't using our build script anyway so it's really up to
them...

what was/is wrong with miniupnp? ugly code? bad api? unstable?

-- 
UPnP does not work
https://bugs.launchpad.net/bugs/230973
You received this bug notification because you are a member of LinuxDC++
Team, which is subscribed to LinuxDC++.

Status in ApexDC++ - The Pinnacle of File-Sharing: New
Status in DC++: In Progress
Status in Linux DC++: New

Bug description:
Version 0.706.

I have UPnP configured correctly in my OS (Windows XP) and my router (Linksys 
WRT54GL). eMule, Miranda, Skype, uTorrent all work fine and correctly setup 
ports. However, dc++ does not. It used to work few times, but now it just 
complains that failed to setup ports. I've run upnp sniffer, and it seems that 
it doesn't even send out UPnP packets.

If you need additional information, please tell what kind and how to get it :)



_______________________________________________
Mailing list: https://launchpad.net/~linuxdcpp-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~linuxdcpp-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to