dumbasPL
commented
1 year ago I haven't used windscribe for a while, but now that mullvad nuked port forwarding, I might return to it.
As for adding support for other torrent clients, well, this project was initially meant to be a quick and dirty hack, but now that there is interest in it, I think it would be a good idea to re-brand it to just windscribe-ephemeral-port, add support for all kinds of torrent clients, maybe add a generic webhook, maybe an ability to run a program/bash script with the new port as an argument, and maybe even re-write it in rust ;)
some time ago @EnumC forked it and added qbittorrent support.
Would it be possible to add support for transmission to set peer-port? Either using transmission-remote by installing transmission-cli package and passing the proper command line something like: $ transmission-remote $TRANSMISSION_HOST:$TRANSMISSION_PORT --auth=$TRANSMISSION_USERNAME:$TRANSMISSION_PASSWORD -p $WINDSCRIBE_PORT
You would need to export the Windscribe port found as an environment variable but it would make it easier to add support for other BT clients.
Or another option is through an rpc call to http://host:9091/transmission/rpc
RPC would not require a client but may be a little more to configure than using the transmission-remote client.
Some references: https://www.reddit.com/r/selfhosted/comments/rzzn3q/cronjob_for_updating_transmissions_peerport_to/ https://linux.die.net/man/1/transmission-remote
Thanks!