Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hello,
I'm using MLDonkey as torrent client, but some torrent sites do not support this client and incorrectly counts ratio (or do not count ratio at all). So what clients are compatible with most torrent sites? Say what you think...
Regards,
alpha
Offline
Try Transmission and you'll never want something else.
http://dns323.kood.org/forum/t2719-%5BR … ssion.html
regards, jarek
Offline
I love MLDonkey for just few things:
1. Multiprotocol support (BitTorrent, eDonkey, FTP).
2. Posibility to use SSH and GUI called sancho. You don't need WEB which is not so secure as SSH
So I just found that MLDonkey version 2.9.7 has too much issues with seeding files and trackers, so I downgraded to stable 2.9.6 (which is compilled by shadowandy) and all problems dissapeared. It seems that 2.9.7 is not officialy released and has some major issues.
Regards,
alpha
Offline
alpha wrote:
I love MLDonkey for just few things:
1. Multiprotocol support (BitTorrent, eDonkey, FTP).
2. Posibility to use SSH and GUI called sancho. You don't need WEB which is not so secure as SSH
I'm glad you're happy with MLDonkey. In case someone else is thinking about Transmission (or you do in the future), there are a number of ways it can be used via SSH by using port forwarding:
1. Command-line client 'transmission-remote', comes with the base install.
2. Multi-platform GUI client 'transmission-remote-gui', http://code.google.com/p/transmisson-remote-gui/
3. The web interface 'Clutch', which is part of the base install. Clutch runs its own webserver, so you can have lighttpd open to the world, but still have Clutch accessible only via SSH port forwarding.
Offline
Hi,
I have installed transmission 1.51 and all your 3 ways is working except one issue. I can use SSH port which is 22, but it will never be true SSH protocol. Its just WEB server on 9091 port or whatever you set it. That is not very good. I hope that it will be true SSH protocol support. So in general I can't open 9091 or 22 port to outside world because password is not encrypted and it not SSH. The only way is to use SSH to DNS323 and then use transmission-remote.
Regards,
alpha
Offline
You don't have to use the web server that's built into Transmission. You can use a different one (lighttpd for example) and set it up so it uses https.
Offline
Hi,
Thanks for supporting. I use lighttpd for my website and its chrooted. The best way is to disable transmission totaly and leave only 'transmission-remote'. I think it's the most secure. Maybe you have some suggestions for security ?
Regards,
alpha
Offline
Hi,
KyleK wrote:
You don't have to use the web server that's built into Transmission. You can use a different one (lighttpd for example) and set it up so it uses https.
Can you give me some info on how to set up transmission with lighttpd ? As I understand this new version of transmission has its own integrated web server. How to deintegrate/disable it and how to setup it for use with lighttpd?
Regards,
alpha
Offline
alpha wrote:
Hi,
Can you give me some info on how to set up transmission with lighttpd ? As I understand this new version of transmission has its own integrated web server. How to deintegrate/disable it and how to setup it for use with lighttpd?
You'll need to setup lighttpd as proxy. http://redmine.lighttpd.net/wiki/lightt … #mod_proxy
Transmission 1.22 is the latest version without internal web server, so personal I have used it without any problems.
Offline
alpha wrote:
I have installed transmission 1.51 and all your 3 ways is working except one issue. I can use SSH port which is 22, but it will never be true SSH protocol. Its just WEB server on 9091 port or whatever you set it. [...] So in general I can't open 9091 or 22 port to outside world because password is not encrypted and it not SSH.
I suggested using SSH with port forwarding. So you connect using SSH to port 22 (password required, password is never transmitted in plaintext). Then you set up your SSH connection to create a tunnel, so that the HTTP traffic (or RPC in the case of transmission-remote-gui) is encrypted.
Essentially, you can create a port-specific VPN using your SSH connection. If you Google "SSH port forwarding" or "SSH tunneling" you should find lots of explanations. Sorry to RTFM you, but I don't think I can explain it succintly.
Offline
MCGlausa wrote:
I suggested using SSH with port forwarding. So you connect using SSH to port 22 (password required, password is never transmitted in plaintext). Then you set up your SSH connection to create a tunnel, so that the HTTP traffic (or RPC in the case of transmission-remote-gui) is encrypted.
Essentially, you can create a port-specific VPN using your SSH connection. If you Google "SSH port forwarding" or "SSH tunneling" you should find lots of explanations. Sorry to RTFM you, but I don't think I can explain it succintly.
Thanks for some directions. I'll try to look for it...
Regards,
alpha
Offline
Hi,
Thanks again for sugesting SSH tunelling. I just tried it and discovered huge capabilities on it I'm very happy now. Thank you very mush !!!
Regards,
alpha
Offline
rTorrent, its not pretty, but who sits there looking at their torrent client all day.
Offline