aMule Bug Tracker - aMule
View Issue Details
0001039aMuleExternal Connpublic2007-01-14 00:482008-03-24 20:05
0001039: Using Tor SOCKS proxy
Fresh Tor install on LAN router (os x tiger) - listening on and for SOCKS connection
LAN client (os x tiger) with emule - config proxy port 9050
Here are the Tor error log when trying o connect

with SOCKS4 or SOCKS4a :
Jan 13 23:39:38.567 [warn] fetch_from_buf_socks(): socks4: Port or DestIP is zero. Rejecting.
Jan 13 23:39:38.567 [warn] connection_ap_handshake_process_socks(): Fetching socks handshake failed. Closing.

with SOCKS5 :

Jan 13 23:23:27.678 [warn] fetch_from_buf_socks(): Your application (using socks5 on port 0) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead. For more information, please see [^]
Jan 13 23:23:27.678 [notice] connection_ap_handshake_rewrite_and_attach(): Application asked to connect to port 0. Refusing.

Tor proxy is working : i verified using other apps with SOCKS 4 and 5 support

OK I found the problem dabbling around
it was the server.met list from : [^]

when pasting the http link to the .met file, the servers list made amule try to connect always on TCP port zero...
No tags attached.
Issue History
2007-01-14 00:48dimdomNew Issue
2007-01-14 00:48dimdomOperating System => OS X
2008-03-24 20:05XaignarStatusnew => resolved
2008-03-24 20:05XaignarFixed in Version => SVN
2008-03-24 20:05XaignarResolutionopen => fixed
2008-03-24 20:05XaignarAssigned To => Xaignar
2008-03-24 20:05XaignarNote Added: 0002765

2008-03-24 20:05   
This should be fixed in current SVN. It was a problem with server.mets containing aux-ports with the value zero, which caused the actual port to be overwritten.