aMule Forum
English => aMule Help => Topic started by: Aardvarh on June 23, 2008, 03:11:27 PM
-
Hi,
I've seen quite a few comments about this bug in Intrepid & it seems to have been fixed in 2.2.0 for Hardy but :-
UPnP.cpp(87): Universal Plug and Play: error(CDynamicLibHandle): Unable to dlopen libupnp.so.3. Check PATH and LD_LIBRARY_PATH.
UPnP.cpp(1063): Universal Plug and Play: bound to 192.168.1.66:50000.
UPnP.cpp(1134): Universal Plug and Play: UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.
Regards
-
You need either libupnp.so.2 or libupnp.so.3 . In your case the .2 - library exists and you can savely ignore this message.
The old version however seems not to support your router properly. Please upgrade to the latest version of lipupnp (pupnp.sf.net) and see if it supports your router now properly.
kind regards
-
Aardvarh, I think that I do not understand very well...
Ubuntu 8.10 Intrepid will use libupnp3 but Ubuntu 8.04 Hardy uses libupnp2... ¿where is the problem?
-
Hi all,
I'm using Festor`s repository
helio@hp-core:~$ cat /etc/apt/sources.list.d/amule.list
deb http://ppa.launchpad.net/festor90/ubuntu hardy main
... and today I have this warning in my daily report from rkhunter:
Warning: Network TCP port 2006 is being used by /usr/bin/amuled. Possible rootkit: CB
Use the 'lsof -i' or 'netstat -an' command to check this.
I have checked all my amule network config and don't have port 2006 for anything. Do I need to have attentions do anything?
Regards,
Helio Pereira
-
O.o guau...
Can anyone else confirm this?
you use a firewall tool? You should use a firewall tool like ufw or Firestarter
-
Festor,
I'm sorry - I'm confusing 2 issues here. The basic problem is that my router is not being seen. I thought that it was related to the dlopen failure (the messages appear together) but it seems that I was wrong. This does not seem to be a packaging issue.
Wuischke
Thank you for the suggestion but the router (ST780WL) is still not seen with the latest version. Ktorrent works fine BTW. I'm not sure now where the problem lies.
Regards
-
O.o guau...
Can anyone else confirm this?
you use a firewall tool? You should use a firewall tool like ufw or Firestarter
My firewall is on the router and in my PC I have some ports bloqued with iptables.
-
What are your aMule ports, Sharkypt?
-
The standards. From 4661 to 4669 TCP and 4672 UDP.
-
Maybe your rootkit detector is stupid enough to think that connecting to port 2006 on other user means you're rootkitted.
-
Maybe your rootkit detector is stupid enough to think that connecting to port 2006 on other user means you're rootkitted.
I have so many connections to other ports and the rootkit only detect error on port 2006?
-
It's not an error, it's that there is an specific rootkit that works on port 2006, CB.
Or maybe amule is sending data to other client over port 2006, which can also happen (you open your incoming ports, but outgoing ports can be different). That's actually the most likely scenario.
-
Yes... you are right.
Thanks for your help :-)
-
So, what is the situation of this thread? If the router problem still persists, please enable Debug UPnP log messages in the preferences and post the log.
Successfull dlopen does not mean that your router has been seen. Also you will always get an error, either for not finding libupnp2 or libupnp3. You should not have both in your system, and aMule searches for both. You just can't have both errors.
In a near future, I will remove the dlopen code.
-
dlopen code is removed from the svn code.