Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
The official changelog is kind of misleading, since neither daemon nor CLI have blocklist functionality enabled. But, I've been compiling builds with that feature for a while now, just no public versions.
I'll post v1.20 Saturday evening or Sunday.
EDIT: Ok, I did a quick compile just now, you can get it here.
This is for funplug-0.5, obviously.
In order to use the blocklist functionality, you have to call transmission-daemon with the '-b' argument. Also, the blocklist file has to be put in TRANSMISSION_HOME/blocklist
Sleep now :)
Last edited by KyleK (2008-05-10 05:59:57)
Offline
tks again Kylek
running Transmission 1.20 in my ch3snas now ( funpkg -I transmission.1.20 ) all works it the same upload/download torrents that was in Transmission 1.11 version.
The Blocklist:
First i put the level1.txt in /mnt/HD_a2/.transmission/blocklist/ then i run the transmission-daemon -b, and the level1.txt move automatic to /mnt/HD_a2/.transmission/ and with the new name blocklist.
Last edited by Nasp (2008-05-11 00:44:54)
Offline
Did you remove 1.11 before installing 1.20? I did:
funpkg -r transmission-1.11svn-r5649-ffp0.5.tgz funpkg -i transmission-1.20-ffp0.5.tgz /ffp/start/transmission.sh start
and got a "No Transmission socket found". I re-installed 1.11 which is now running.
Offline
KRH wrote:
you need to install curl also try check the transmission log in .transmission
You're right - there says: /ffp/bin/transmission-daemon: can't load library 'libcurl.so.4'.
What is it? Where can I get it? How do i install it?
Offline
KRH wrote:
first post in this topic
Thanks, sometimes the tunnel vision is extra tunelly.
Offline
What router do you use? It either does not support UPnP or NAT-PMP, or it is not enabled. Try to forwared one specific port in your router to the CH3SNAS, and use that as port for Transmission (the default is 51413).
You can test with this link if the port is properly accessible: http://www.utorrent.com/testport.php?port=<your port> (replace <your port> with the actual port number).
Offline
KyleK wrote:
What router do you use?
The router is a Sweex Wireless Broadband Router 11G (LC000070)
KyleK wrote:
It either does not support UPnP or NAT-PMP, or it is not enabled.
In the Miscellaneous section of the modem the UPnp settings are enabled. Bit strange though to use the word Settings since I can't find any further settings for this UPnp service.
KyleK wrote:
Try to forwared one specific port in your router to the CH3SNAS, and use that as port for Transmission (the default is 51413).
I have forwarded both port 51413 and 8080 to the internal IP of the CH3SNAS
KyleK wrote:
You can test with this link if the port is properly accessible: http://www.utorrent.com/testport.php?port=<your port> (replace <your port> with the actual port number).
> Welcome to the µTorrent Port Checker.
> A test will be performed on your computer to check if the specified port is opened.
>
> Checking port 51413 on 82.75.218.29...
>
> OK! Port 51413 is open and accepting connections.
>
> You will be able to receive incoming BitTorrent connections.
Seems the port is open too.
Bit strange, ain't it?
Offline
I suggest you post about the problem (including the log) on the Transmission forums (http://forum.transmissionbt.com)
People there will be more of help.
Also, try first with a very popular torrent (Ubuntu CD image or a OpenOffice release), just to check if it's really a problem with the app and not the torrent.
Offline
KyleK wrote:
I suggest you post about the problem (including the log) on the Transmission forums (http://forum.transmissionbt.com)
People there will be more of help.
Also, try first with a very popular torrent (Ubuntu CD image or a OpenOffice release), just to check if it's really a problem with the app and not the torrent.
Thanx KyleK
I also tried putting the the CH3SNAS in the DMZ but still no response from trackers however trackers did show up in the log though. I'll try posting on the transmission forum
Offline
Just a little heads-up:
The Transmission developers are doing a complete overhaul of the communication protocols, i.e. a lot of code is being rewritten. While the current svn version compiles fine already and works as expected, Clutch won't be able to communicate with the new builds.
I'm closely following the development of both projects and will put up new builds as soon as it makes sense again.
Offline
does transmission works on filtered bandwidth by ISP?
Offline
Please fix this part of the first post instructions about defining the path to socket.txt as it is wrong (at least on Transmission 1.2 and fun_plug 0.5).
I was puzzled for a couple of hours by it, and now I just found somebody else solved it in the middle of the thread after finally I worked it out. Bummer..
KyleK wrote:
* Important: The file clutch/remote/data/socket.txt stores the path to the transmission-daemon socket file. You hence have to change this file:
Code:
# cd /mn/HD_a2/.transmission # pwd >/mnt/HD_a2/www/pages/clutch/remote/data/socket.txt
Not only is there a typo (cd /mn/HD_a2)
But it needs to be the full path to the socket file, not just a directory. This works:
echo /mnt/HD_a2/.transmission/daemon/socket > /mnt/HD_a2/www/pages/clutch/remote/data/socket.txt
Thanks for the rest - Transmission finally added https support in 1.2 so I can finally use it on my favourite private tracker.
Offline
egg_nostic wrote:
KyleK wrote:
What router do you use?
The router is a Sweex Wireless Broadband Router 11G (LC000070)
KyleK wrote:
It either does not support UPnP or NAT-PMP, or it is not enabled.
In the Miscellaneous section of the modem the UPnp settings are enabled. Bit strange though to use the word Settings since I can't find any further settings for this UPnp service.
KyleK wrote:
Try to forwared one specific port in your router to the CH3SNAS, and use that as port for Transmission (the default is 51413).
I have forwarded both port 51413 and 8080 to the internal IP of the CH3SNAS
KyleK wrote:
You can test with this link if the port is properly accessible: http://www.utorrent.com/testport.php?port=<your port> (replace <your port> with the actual port number).
> Welcome to the µTorrent Port Checker.
> A test will be performed on your computer to check if the specified port is opened.
>
> Checking port 51413 on 82.75.218.29...
>
> OK! Port 51413 is open and accepting connections.
>
> You will be able to receive incoming BitTorrent connections.
Seems the port is open too.
Bit strange, ain't it?
I'm having trouble with uploads. Downloads seems ok, but aren't at speeds I'm used to. Have opened the incoming port for transmission in my router and the http://www.utorrent.com/testport.php webpage is responding that the connection is OK. Very strange problem, anyone having a solution?
Using Clutch-0.4.tar.gz, ffp 0.5, php-5.2.6-1.tgz, transmission 1.21. I've changed the default port to 5141.
From transmission log file:
Bound socket 18 to port 5141
Opened port 5141 to listen for incoming peer connections
tracker response: 200
Got 8 peers from tracker
tracker response: 200
Nothing gets uploaded ... and it's a requested torrent.
Offline
First post updated. Transmission 1.21 was released because of a memleak and some bugfixes to prevent crashes.
Offline
Eskas wrote:
I'm having trouble with uploads. Downloads seems ok, but aren't at speeds I'm used to. Have opened the incoming port for transmission in my router and the http://www.utorrent.com/testport.php webpage is responding that the connection is OK. Very strange problem, anyone having a solution?
Using Clutch-0.4.tar.gz, ffp 0.5, php-5.2.6-1.tgz, transmission 1.21. I've changed the default port to 5141.
From transmission log file:
Bound socket 18 to port 5141
Opened port 5141 to listen for incoming peer connections
tracker response: 200
Got 8 peers from tracker
tracker response: 200
Nothing gets uploaded ... and it's a requested torrent.
I can't report of any speed problems here. I can download and upload at my lines maximum.
There may be multiple reasons for why you have slow downloads and no upload. For one, please note that Transmission does not have DHT support like Azureus or uTorrent. This means it solely relies on the tracker(s) to get peers and seeds. This might make quite a speed difference.
Also, your ISP may filter bittorrent traffic. Try with encryption enabled ("transmission-remote -c required" or "transmission-remote -c preferred").
You could also try to download a very fast torrent (OpenOffice, Ubuntu Live-CD etc.) to see if you reach full speeds.
Offline
I tried execute "transmission-remote -c required" in the SSH shell and here is the responce :
root@DNS-323:/mnt/HD_a2/ffp/start# transmission-remote -c required
transmission-remote: failed to connect to socket file: /home/root/.config/transmission/daemon/socket: No such file or directory
Looks like some conf file needs to be edited ? or there is something else ? I got ffp 0.5, Clutch , transmission on DNS 323
Offline
Before executing transmission-remote, you have to set the TRANSMISSION_HOME environment variable:
export TRANSMISSION_HOME=/mnt/HD_a2/.transmission
Use the appropriate path.
transmission-daemon has to be running.
Offline
KyleK wrote:
I suggest you post about the problem (including the log) on the Transmission forums (http://forum.transmissionbt.com)
People there will be more of help.
Also, try first with a very popular torrent (Ubuntu CD image or a OpenOffice release), just to check if it's really a problem with the app and not the torrent.
Hi, still no success I must say. I have tried downloading Ubuntu 8.04 and download speed was ok, not fantastic, but ok. It varied a little bit more than I'm used to with uTorrent in Vista. As far as downloads are concerned, I still face the problem with speed. I have managed to get it to start upload, but it doesn't seem to use all of the peers. At the moment I'm uploading to 6 of 8 peers for Ubuntu at 40 kB/s ... I have 10 mbit upload.
I've tried "transmission-remote -c preferred", but adding encryption didn't make any difference either.
I've also tried to disable the auto mapping of ports with transmission-remote -M, don't really know if this is enabled by default. But it hasn't opened any ports on my router automaticly, so I disabled it.
Any more suggestions?
Offline
Thanks ... that worked !!
Do I have to type "transmission-remote -c required" every time I want transmission to start with encryption support ? Or it is going to stay on always ?
Also , about "export TRANSMISSION_HOME=/mnt/HD_a2/.transmission" - I checked transmission.sh. It has such line there. So I was wondering, if I need to type it every time I start Transmission ?
Thank you for prompt answers !
Last edited by ka3ak (2008-05-23 19:49:59)
Offline
ka3ak wrote:
Thanks ... that worked !!
Do I have to type "transmission-remote -c required" every time I want transmission to start with encryption support ? Or it is going to stay on always ?
Also , about "export TRANSMISSION_HOME=/mnt/HD_a2/.transmission" - I checked transmission.sh. It has such line there. So I was wondering, if I need to type it every time I start Transmission ?
Thank you for prompt answers !:)
Transmission stores your encryption preference, so you only have to set it once.
the export command in transmission.sh is necessary so the daemon knows where to look for its configuration files on start-up.
Since you use transmission-remote from a telnet or ssh shell, it's a different environment where the variable has to be set separately.
If you use telnet, you can add the export line to your fun_plug script (just right at the beginning)
If you connect via ssh, put it in the /ffp/etc/profile file.
It should then be set automatically as soon as you connect via telnet/ssh (you can check by just typing "export").
Offline
Eskas wrote:
KyleK wrote:
I suggest you post about the problem (including the log) on the Transmission forums (http://forum.transmissionbt.com)
People there will be more of help.
Also, try first with a very popular torrent (Ubuntu CD image or a OpenOffice release), just to check if it's really a problem with the app and not the torrent.Hi, still no success I must say. I have tried downloading Ubuntu 8.04 and download speed was ok, not fantastic, but ok. It varied a little bit more than I'm used to with uTorrent in Vista. As far as downloads are concerned, I still face the problem with speed. I have managed to get it to start upload, but it doesn't seem to use all of the peers. At the moment I'm uploading to 6 of 8 peers for Ubuntu at 40 kB/s ... I have 10 mbit upload.
I've tried "transmission-remote -c preferred", but adding encryption didn't make any difference either.
I've also tried to disable the auto mapping of ports with transmission-remote -M, don't really know if this is enabled by default. But it hasn't opened any ports on my router automaticly, so I disabled it.
Any more suggestions?
Think I've got it to work now. The variable download rate seems to be because Transmission is hardcoded to just 50 peers.
How have you guys solved the problem of file and map permissions of torrent downloads?
Is there some way to automaticly set the user and group permissions of downloads to a samba user(User added in the d-link web UI)? By doing this a windows user could easy move or delete torrents.
Offline
Take a look at the start/transmission.sh
There, you can specify a user name with which Transmission will be executed.
Beforehand you have to make sure that A) the .transmission directory and all its content has full permission for this user (chown -R <username> /mnt/HD_a2/.transmission) and that the user has write access do the Downloads folder.
Offline