aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 [2]

Author Topic: Slackware 12.0/12.1  (Read 29650 times)

jman

  • Guest
Re: Slackware 12.0/12.1
« Reply #15 on: June 26, 2008, 09:44:26 PM »

You can savely remove all info about <2.2.1. It was just the old version why I've set this marker. I you update it to 2.2.1 and svn, and maybe a recent version of the distro, I can start the translation.

Ok, so I'll cut everything I think is not needed anymore and - upon approval of the new page - I can also provide Italian and (maybe) French translation.

jman
Logged

jman

  • Guest
Re: Slackware 12.0/12.1
« Reply #16 on: June 26, 2008, 11:48:40 PM »

You can savely remove all info about <2.2.1. It was just the old version why I've set this marker. I you update it to 2.2.1 and svn, and maybe a recent version of the distro, I can start the translation.

Hello,

I think I'm done. Please check the new page at your convenience, so we can start with translations.

Thanks!

bye,
jman
Logged

jman

  • Guest
Re: Slackware 12.0/12.1
« Reply #17 on: July 01, 2008, 11:08:08 PM »

I have added the Italian and French translation.

Now please someone update the main wiki page to notify their existence.

Thanks,
jman
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: Slackware 12.0/12.1
« Reply #18 on: July 07, 2008, 01:36:53 AM »

The final problem is that I get

UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.
I need info on this problem to fix it. If someone is able to provide me the UPnP logs (enable it in preferences) and the libupnp debug logs (must compile it by hand and provide the files IUpnpErrFile.txt and IUpnpInfoFile.txt that are generated at the directory where aMule is run), I would be glad.

Cheers!
Logged

jman

  • Guest
Re: Slackware 12.0/12.1
« Reply #19 on: July 08, 2008, 09:44:14 PM »

I need info on this problem to fix it. If someone is able to provide me the UPnP logs (enable it in preferences) and the libupnp debug logs (must compile it by hand and provide the files IUpnpErrFile.txt and IUpnpInfoFile.txt that are generated at the directory where aMule is run), I would be glad.

Hello,

I'll try to shed some light on the issue. The upnp package I've used (downloaded and
compiled with debug msgs) is 1.6.6 from upnp.sf.net.

Then I've recompiled aMule 2.2.1 with upnp support and enabling debug. Performing an
"ldd" on aMule binaries libupnp does not appear (don't know why but probably it is not
an issue).

On startup here it appears the messages hruotland mentioned:

Code: [Select]
2008-07-08 20:42:53: UPnP.cpp(87): Universal Plug and Play: error(CDynamicLibHandle): Unable to dlopen libupnp.so.2. Check PATH and LD_LIBRARY_PATH.
2008-07-08 20:42:53: UPnP.cpp(91): Universal Plug and Play: Successfully opened libupnp.so.3.
2008-07-08 20:42:53: UPnP.cpp(1063): Universal Plug and Play: bound to 10.0.0.254:49152.
2008-07-08 20:42:53: UPnP.cpp(1134): Universal Plug and Play: UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.

Apparently aMule at first is looking for the libupnp .so file belonging to a 1.4.x version
(libupnp.so.2), then correctly detects the installed version (libupnp.so.3 belonging to
libupnp 1.6.x).
I'll attach the file "IUpnpInfoFile.txt" as per your request. The file "IUpnpErrFile.txt"
is created but not populated (sticks to zero bytes).

I've noticed that on file upnp/src/genlib/miniserver/miniserver.c of libupnp srcs there's
such a statement:

Code: [Select]
#define APPLICATION_LISTENING_PORT 49152

this may be the reason why he's using that port in the first place. Opening the port on
the router doesn't change the erratic behaviour. I didn't find any trace of the other port
(60776), so maybe the choice is based on another logic.

Is it possible that some code in UPnp.cpp should be changed for newer libupnp?

This is as far as I can go :-), hope all this helps

Thanks for your help.

Jman
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: Slackware 12.0/12.1
« Reply #20 on: July 10, 2008, 04:58:05 AM »

Hi jman,

Could you please try with tomorrow svn tarball? I hope this problem has been fixed.

In fact, I needed the full log to understand what is going on. You must enable it on Preferences->Debug.

Cheers!
Logged

jman

  • Guest
Re: Slackware 12.0/12.1
« Reply #21 on: July 11, 2008, 08:23:48 PM »

In fact, I needed the full log to understand what is going on. You must enable it on Preferences->Debug.

Hello,

I've just compiled and installed aMule from tarball aMule-CVS-20080711.tar.bz2
I've activated verbose debugging and selected the "Universal Plug And Play" tick.
The error concerning the old library (libupnp.so.2) has disappeared (cool), but the UPnP discovery still times out:

Code: [Select]
2008-07-11 19:59:55: UPnPBase.cpp(866): Universal Plug and Play: bound to a.b.c.d:49152.
2008-07-11 19:59:55: UPnPBase.cpp(1238): Universal Plug and Play: UPNP_DISCOVERY_SEARCH_TIMEOUT.
2008-07-11 19:59:55: UPnPBase.cpp(937): Universal Plug and Play: UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.

In case something's wrong with my router forwarding policy, here's a recap:
- TCP+UDP on port 49152 (mentioned in the above code and automatically chosen by aMule)
- Standard TCP port
- UDP for extended server requests (i.e. Standard TCP port +3)
- UDP for UPnP

Attached IUpnpInfoFile.txt debug file.

Hope this helps!

Please let me know if I can provide further info, thanks for your time!

jman
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: Slackware 12.0/12.1
« Reply #22 on: July 12, 2008, 05:14:31 PM »

Hi jman,

Thanks for the IUpnpInfoFile.txt, I appreciate your effort of compiling libupnp in debug mode.

But I still need the upnp debug aMule log. You need to enable debugging UPnP messages in preferences.

Cheers!
Logged

jman

  • Guest
Re: Slackware 12.0/12.1
« Reply #23 on: July 12, 2008, 08:23:24 PM »

But I still need the upnp debug aMule log. You need to enable debugging UPnP messages in preferences.

Hi,

I'm sorry for wasting your time with unhelpful posts, but I see no specific upnp log file. I only see the libpunp txt files and a "logfile" in my home (which relevant lines I quotes in my posts), I've also checked the /proc/$PID/fd directory to be sure I was not missing something.
I didn't find anything relevant to debug messages in the prefs of aMule, other the one that you suggested, nor at compile time.
I'll attach this logfile aMule writes, hoping this is what you mean, otherwise please be patient with me ^_^ and explain what I'm doing wrong, thanks!

jman
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: Slackware 12.0/12.1
« Reply #24 on: July 13, 2008, 05:53:46 AM »

jman,

Nevermind about unhelpfull posts, you are trying to help and I appreciate that.

Please, open aMule, go to Preferences, then click on "Debugging", make sure that "Enable Verbose Debug-Logging" is checked, and check "Universal Plug And Play" in the "Message Categories" box.

Then exit aMule and start it again. The file I need is exactly the file you have sent me, but now it will have the necessary debug messages.

Cheers!
Logged

jman

  • Guest
Re: Slackware 12.0/12.1
« Reply #25 on: July 13, 2008, 11:42:48 AM »

The file I need is exactly the file you have sent me, but now it will have the necessary debug messages.

Ok, then I confirm the logfile attached in my latest post has been generated following your instructions (enable uPnP, enable verbose debugging and tick "Universal Plug and Play"),  I just cannot get upnp to be more verbose, though.

jman
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: Slackware 12.0/12.1
« Reply #26 on: July 13, 2008, 01:12:39 PM »

Well, in this case, no device in your local network has answered the broadcast from the upnp library. That means that you have either one or both of the following conditions:

1 - Your router has its upnp feature disabled or does not have it at all. Check the router's documentation. There should be a web interface where you can control all of its features, then check for UPnP ability.

2 - You have a firewall blocking UPnP messages. Make sure you have opened the following ports:
    tcp destination 50000 - The UPnP port that is specified in your aMule general preferences, it could be a different number, please check there.
    udp destination 1900  - The libUPnP port
    udp source 1900  - Also libUPnP, if you enable this, things get faster.

Cheers!
Logged

jman

  • Guest
Re: Slackware 12.0/12.1
« Reply #27 on: July 13, 2008, 02:50:02 PM »

1 - Your router has its upnp feature disabled

*cough cough* /me blushes

Well, it turns out that it worked.
In order to earn the community's forgiveness, I'll update the aMule wiki page about UPnP, that still recommends libupnp 1.4.x :)

Thanks again for your effort (and your patience!)

jman
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: Slackware 12.0/12.1
« Reply #28 on: July 14, 2008, 12:03:55 AM »

lol :D

Thank you for your effort to put things to work, and your collaboration on the wiki is very much appreciated!

Cheers!
Logged
Pages: 1 [2]