Comment 11 for bug 201624

>
> Thank you for providing an updated build.
> This time upnp worked, despite amule complaining for libupnp2
>
> 2008-05-26 14:13:33: UPnP.cpp(87): Universal Plug and Play:
> error(CDynamicLibHandle): Unable to dlopen libupnp.so.2. Check PATH and
> LD_LIBRARY_PATH.
> 2008-05-26 14:13:33: UPnP.cpp(91): Universal Plug and Play: Successfully
> opened libupnp.so.3.
>

aMule amule - 2.2.0~svn20080525-0ubuntu1 for Intrepid use libupnp3 not
libupnp2

| * debian/control:
| - Require libupnp3 for uPnP support

I also noticed a weired behavior: I cannot use amule with ufw. Despite
> allowing all three ports set in amule preferences I cannot get a HIGH ID
> unless I shut down the firewall.
> Syslog prompts an incoming connection has been blocked when the firewall is
> enabled, the strange side is that the port blocked changes each time I start
> amule!
>
> Here is a bit of my logfile (where 192.168.1.1 is my UPNP enabed router)
>

I do not know if I understood you well, but I think that is something
normal. Many clients do not use the ed2k network ports by default what you
can get more connections than expected. Yet this is not really good, since
many of these connections can not be trusted ed2k clients.

Use only the ports "official" aMule may be the best option, but this may
cause you have fewer sources (or low id) in your downloads.

Moreover, using unofficial ports can promote the speed of downloading as
many of ed2k servers aMule / eMule reduce traffic information to ports
officials to avoid overloading.