Ability to pass through arguments on UDP and TCP ports.#41
Ability to pass through arguments on UDP and TCP ports.#41omerinero wants to merge 1 commit intongosang:masterfrom
Conversation
|
Hey, maybe this is not the best place to ask but I haven't found so many peeps using vpn on aMule. May I ask which vpn provider are you using which gets high id when connecting to a server? Tried with PrivateInternetAccess vpn but no luck, and I was considering AirVPN. Thanks! |
|
I utilize ProtonVPN Plus, consistently choosing servers that support P2P. To maintain a secure and anonymous connection, I launch an additional container (Gluetun) that establishes the VPN connection, enabling aMule to utilize this network configuration. |
|
I do not oppose but I don't think this will be useful for most users. If I understand you well:
aMule has 3 ports than must be open to the Internet, not 2. The second is related to the first and it's not configured in aMule.conf. You have to change that port in the "ports" section too and that is hard to explain if other users mess with the ports... Since you are already updating the docker-compose.yml and you have the aMule.conf file mounted in the container (you can access to it from the host). Why don't you create a personal script to replace the docker-compose.yml, the aMule.conf and restart the docker-compose? You can also extend this Docker image to add VPN support. |
Since I need to run aMule on random ports generated by my VPN I had to provide those ports in the aMule preferences before aMule started. Maybe this feature will be useful to someone else.
Sometimes I need to do manual configuration, like when my VPN container restarts and the random port is re-generated, I'm thinking about integrating VPN and aMule all in one container ( something like this https://github.com/haugene/docker-transmission-openvpn )