aMule Forum
English => aMule Help => Topic started by: Obeliks on April 26, 2006, 06:06:51 PM
-
Hi. I installed aMule yesterday, so I can have it running on my fileserver all night long ;)
Now my problem is, that I'm behind a NAT (and if that wasn't enough, ed2k traffic is limited to 10k or something).
Since the server has a steady connection to an OpenVPN server, I was wondering if I can patch aMule through there? I tried googling and searching the usual suspects (including this forum), but I didn't exactly stumble across any regarding information.
Thanks for any advice you can give me!
Sincerely, Obeliks
-
just change the default route to go to the openvpn gateway...amule will use that aswell and all your traffic will go there...
-
Thanks, but that won't work... I can't have all the traffic going via the OpenVPN, for performance and financial (traffic) reasons...
I guess amule doesn't support binding to a certain IP or network interface? too bad...
-
It does. check preferences.
-
Originally posted by Kry
It does. check preferences.
Sorry I missed that. Is this option available in the amuled daemon config? Because I can't find it there... or am I being blind? ;)
-
grep -hi addr amule.conf
Address=
ECAddress=
-
Ok, I am being blind. Sorry! Thanks for your help!
-
Ok, I tried putting Address=172.20.0.6 (my openvpn address), but all connections still seem to be made locally, none via the vpn.
What could I be doing wrong?
EDIT: Ok, I'm postponing this question. Obviously just listening on the openvpn address doesn't route created connections through it. Hope I can figure out how to narrow an iptables rule down to all packages from amule. Any ideas?
-
Originally posted by Kry
It does.
But I guess aMule doesn't support binding to a certain interface/address for outgoing connections, does it? Because OpenVPN drops the packages for having a bad/unknown source address, and my efforts to mangle the address failed so far.