0001039: Using Tor SOCKS proxy

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001039

aMule

External Conn

public

2007-01-14 00:48

2008-03-24 20:05

Reporter

dimdom

Assigned To

Xaignar

Priority

normal

Severity

block

Reproducibility

always

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

2.1.3

Target Version

Fixed in Version

SVN

Summary

0001039: Using Tor SOCKS proxy

Description

Fresh Tor install on LAN router (os x tiger) - listening on 127.0.0.1:9050 and 10.10.10.1:9050 for SOCKS connection
LAN client (os x tiger) with emule - config proxy 10.10.10.1 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 http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS. [^]
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

Additional Information

OK I found the problem dabbling around
it was the server.met list from :
http://ed2k.2x4u.de/index.html [^]

when pasting the http link to the .met file, the servers list made amule try to connect always on TCP port zero...

Tags

No tags attached.

Fixed in Revision

Operating System

OS X

Attached Files

Relationships

Notes
(0002765) Xaignar (manager) 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. Cheers.

Issue History
Date Modified	Username	Field	Change
2007-01-14 00:48	dimdom	New Issue
2007-01-14 00:48	dimdom	Operating System	=> OS X
2008-03-24 20:05	Xaignar	Status	new => resolved
2008-03-24 20:05	Xaignar	Fixed in Version	=> SVN
2008-03-24 20:05	Xaignar	Resolution	open => fixed
2008-03-24 20:05	Xaignar	Assigned To	=> Xaignar
2008-03-24 20:05	Xaignar	Note Added: 0002765