aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Running a SOCKS server for aMule (LowID problems)  (Read 4924 times)

Psy-Q

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 1
Running a SOCKS server for aMule (LowID problems)
« on: January 20, 2006, 10:04:52 AM »
Hello

I'm trying to set up a SOCKS v5 proxy server using Dante (http://www.inet.no/dante/) that would allow people from a private network to connect to public eDonkey/eMule servers using aMule. I've set up the proxy and doing things like HTTP over it works very reliably. aMule also connects successfully to some servers, but always with a LowID. Servers that only allow HighID connections will always kick the clients off.

I'm allowing both TCP and UDP connections to the clients, and I'm not restricting the ports they use, yet it seems aMule can't open the required ports on the proxy. Has anyone set up a SOCKS v5 proxy that gets its clients HighIDs? It would be great to compare notes :)

Is it even technically possible to achieve this? I haven't looked at SOCKS itself too much yet, but I know SOCKS allows clients to negotiate which ports are to be opened on the proxy, therefore it should be possible to run aMule through it with HighID, right?

Thanks for any hints!
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: Running a SOCKS server for aMule (LowID problems)
« Reply #1 on: January 20, 2006, 11:31:51 AM »
it should work with a socks proxy yes...but I have not tested it

the only one who probably tested this is phoenix, since he coded the proxy support....

I will point him to this thread
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

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: Running a SOCKS server for aMule (LowID problems)
« Reply #2 on: January 22, 2006, 04:11:42 PM »
Hi stefanero,

Just got home from a trip today, I still did not read all the e-mail that accumulated in my mail box... :(

Psy-Q,

Using a HTTP, SOCKS4, or SOCKS5 proxy will always lead to a low id. These protocols do not have provision for opening incomming TCP connections. Surprisingly enough, SOCKS5 allow incomming UDP connections... It is a protocol problem, not aMule fault. If someone releases TCP incomming support for, say, SOCKS6 :) we can implement that.

Cheers!
Logged

alexliz

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 19
Re: Running a SOCKS server for aMule (LowID problems)
« Reply #3 on: February 23, 2006, 08:44:47 PM »
So, are you saying it's impossible to connect to a server if I'm running aMule on a computer that hooked to a LAN (wired/wireless) using a proxy?

Right now, I'm on a MacOS X 10.4.4 machine, wirelessly picking up internet from a WinXP Vaio through AnalogX Proxy.

aMule won't connect, even though I specified the proxy address 10.0.0.1 (it's the Vaio's address) and port number 6588. I also tried SOCKS5, but no dice.
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: Running a SOCKS server for aMule (LowID problems)
« Reply #4 on: March 01, 2006, 08:45:27 PM »
Quote
Originally posted by alexliz
So, are you saying it's impossible to connect to a server if I'm running aMule on a computer that hooked to a LAN (wired/wireless) using a proxy?
No, I am not saying that. Please, read my last post again. "Lead to a low id" means connecting to a server, but with a low id.

Quote
Originally posted by alexliz
Right now, I'm on a MacOS X 10.4.4 machine, wirelessly picking up internet from a WinXP Vaio through AnalogX Proxy.

aMule won't connect, even though I specified the proxy address 10.0.0.1 (it's the Vaio's address) and port number 6588. I also tried SOCKS5, but no dice.
Dude, works fine here. Maybe you have a problem with the proxy configuration. Why don't you try a public SOCKS4 or SOCKS5 server to test?

Cheers!
Logged