aMule Forum
English => en_Bugs => Topic started by: Festor on June 27, 2008, 11:55:19 AM
-
Installed: 2.2.0~svn20080218-0ubuntu4
Router is a ZyXel Prestige 660H
Actual info from the router System Status page:
System Name: P660H-T1
ZyNOS F/W Version: V3.40(AGB.1) | 08/08/2006
DSL FW Version:DMT FwVer: 3.4.1.0_A_TC, HwVer: T14F7_0.0
Standard:ADSL_G.dmt
2008-06-26 02:04:57: ExternalConn.cpp(169): External connections disabled in config file
2008-06-26 02:04:57: MuleUDPSocket.cpp(78): Created Server UDP-Socket at port 4665
2008-06-26 02:04:57: MuleUDPSocket.cpp(78): Created Client UDP-Socket at port 4672
2008-06-26 02:04:57: UPnP.cpp(91): Universal Plug and Play: Successfully opened libixml.so.2.
2008-06-26 02:04:57: UPnP.cpp(91): Universal Plug and Play: Successfully opened libupnp.so.2.
2008-06-26 02:04:57: UPnP.cpp(87): Universal Plug and Play: error(CDynamicLibHandle): Unable to dlopen libupnp.so.3. Check PATH and LD_LIBRARY_PATH.
2008-06-26 02:04:57: UPnP.cpp(1063): Universal Plug and Play: bound to 192.168.1.34:50000.
2008-06-26 02:05:00: UPnP.cpp(1134): Universal Plug and Play: UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.
So I get a lowid. Also even if I forward ports in my routers firewall I still get a lowid. Ktorrents upnp works fine.
From: https://bugs.launchpad.net/bugs/243055
-
One suggestion, would it not be better to make aMule look for UPnP 3 library and once found not look for version 2? But, if it does not find libpunp3 should look for libupnp2
-
Festor,
I will remove this dlopen code and do it at linking time.
Could you please enable the UPnP debug log and repost the log? Notice that it will be a long listing.
The WAN service was not detected, maybe your router is using a different service string.
-
This problem has not occurred to me, I just reported from the launchpad.
Ubuntu 8.04 not have a package of UPnP with debugging information...
-
He means in aMule.
-
Yes, I mean check:
aMule->Preferences->Debugging->Disable/Enable->Enable Verbose Debug-Logging
aMule->Preferences->Debugging->Message Categories->Universal Plug and Play
Restart aMule and see the log messages. But if that does not happen to you, there is no point. It must be done at the machine that does not work.