oleo please can you add another features to transmission?
I'd like a buttom that make 'http download' directy in target directory.
In this way the transmission package goes versus a perfect download machine.
Thanks in advantage.
I do not have such problems with r4567. Upload speed limit is exact!
oleo please can you add another features to transmission?
I'd like a buttom that make 'http download' directy in target directory.
In this way the transmission package goes versus a perfect download machine.
Thanks in advantage.
Explain more clearly this feature. I do not understand what you meant.
Hi. I compliment for transmission. And' possible to add a script for the download of file http? or for rapidshare free download? Thanks in advance.
Hi.
Perhaps a little tutorial for kamikaze flash + transmission oleo ?
If you find some spare time ofcourse and my router is free to experiment on too ^^
Happy new year btw
Ok Oleo.
Today the trasmission package allow to manage only the torrent.
I'd like that the transmission package is able to manage also http download and eventually ftp download.
So we have a complete download machine.
Try to look this one:
http://wl500g.info/showthread.php?t=10591
I think that this new functionality is not difficult to be implemented.
I hope to have been clear and to have succeeded in making me understand.
Thanks in advantage
For Kamikaze follow http://www.nslu2-linux.org/wiki/Optw...RT-brcm24Build
For fetching non-torrent files I need some daemon features or maybe just wget . How to do this without breaking things needs a little thinking. Anyway Fetch itself now works without daemon. So you could easily issue non-torrent URL and get things into $SOURCE. But if you are using thttp then this process will die after 5 minutes. The problem with URL fetching is that is more error prone than torrent. And FTP is an old protocol. Then here is issue of username and password. HTTP fetch often needs cookie session reply. Recursive fetch? Do we really need this? For ftp I use ncftp that can store bookmarks with passwords. wget can be used fetching via http/ftp, but there is also wget-ssl.
I've seen screenshot for wget4web. It uses Perl which is not so lihtweight. Managment seems to be poor.
Thanks, this worked very well.
As far as the problem with speed goes, here is the update. With big torrents (4GB+) CPU gets quite busy, and swaping to disk occurs, so transmisson does not update torrent status. I am not really sure, but it looks that at the begining, speed looks good because only download takes place. But after enough data is downloaded to start creating files, router becomes too busy and download speed drops until files are created. After that, speed picks up again but the status is not updated. Hitting Update button helps if downloading only one or two big torrents simultaneously. If there are more big torrents, Update button becomes unreliable - it does not work more often than it does.
Bottom line, in my case the problem was not slow download speed, but rather slow processor/not enough RAM. The router with this software is a great device, but one needs to get to know the limitis. I am still very happy with it and wish to thank all who took part in development.
Status is designed to be unreliable. Queued requests are flushed away. It is non blocking. And it comes eventually. So sugestion for big torrent is that one must take care about memory requrements and not to take parallel downloads .
Hello. I wondered if it is possible to file transmission.conf increase the number of seed to connect. Thanks in advance.
Last edited by morfy; 28-02-2008 at 16:06.
a)Number of peers is limited and not configurable.
b)I've saw that one guy seeds nearly 300 torrents.
Many clients now prefer encryption. Try to enable it in transmission.conf to see if that will help you.
Just uncomment the appropriate variable.Code:# uncomment the following if encryption is preferred ENCRYPTION=-e # uncomment the following if encryption is required # ENCRYPTION="-ee"