Bekijk de volledige versie : Transmission problem
I have installed and used Transmission for awhile now and it works pretty well.
One big problem though - I never got transmission accessible from the wan side!? I forwarded port 8008 to the local IP of my WL500 (10.0.0.4) from the routers webinterface (Virtual server) but nothing happens when I try to access my public IP xxx.xxx.xx.xx:8008 I can access my ouetr through port :8080 but not transmission or twonky either on port 9000?
All other forwarding work well.
- Any ideas - Regards Rasmus
Hi, How to access the Transmission Web interface without the need of disabling my firewall??
Thanks,:)
Is it possible to configure, when no one is connected to the Asus, put transmission downloading, and the oposite, stop transmission when someone is connected??
Thanks.
Is it possible to configure, when no one is connected to the Asus, put transmission downloading, and the oposite, stop transmission when someone is connected??
Thanks.
you most likely need to recompile the sources for that, after you added a little self made program that test this situation...
I guess oleo knows more about this...
it isn't really the meaning of transmission tho, it is supposed to download whithout any help of other pc's:p
... when no one is connected to the Asus...
What do you mean? When all LAN devices are offline, or when nobody is using the web-interface on the router, or there is no LAN to WAN traffic?
You could run a cron-job that checks your preferred condition, and blocks/unblocks all transmission-related traffic via iptables rules. You could stop and start the transmission-daemon as well.
Another idea is to change the maximum upload/download bandwidth with transmission-remote.
examiner
26-11-2008, 00:59
how to start and stop transmission daemon properly - without any data loss?
http://trac.transmissionbt.com/wiki/HeadlessUsageDebian
I am using the attached script on ubuntu server, slightly modified with a umask addition to allow r/w access of regular users to the downloaded files.
You should read the man pages of transmission-daemon and transmission-remote for further information.
You can start/stop/pause individual torrents as well...
What do you mean? When all LAN devices are offline, or when nobody is using the web-interface on the router, or there is no LAN to WAN traffic?
You could run a cron-job that checks your preferred condition, and blocks/unblocks all transmission-related traffic via iptables rules. You could stop and start the transmission-daemon as well.
Another idea is to change the maximum upload/download bandwidth with transmission-remote.
I mean when no computer is connected to the network.
Can you please explain better your solution. Thanks.
http://trac.transmissionbt.com/wiki/HeadlessUsageDebian
I am using the attached script on ubuntu server, slightly modified with a umask addition to allow r/w access of regular users to the downloaded files.
You should read the man pages of transmission-daemon and transmission-remote for further information.
You can start/stop/pause individual torrents as well...
This script resolve my problem ?
denimdemon
11-02-2009, 07:56
I can't get transmission working. I've used wengi's tutorial en installed all the packeges but i cannot get transmission working (when i trie to start up transmission i've got a syntex error)
linux newbie
Hi!
i upgraded to the latest transmission(1.5*) via ipkg upgrade, now transmission is very slow and it runs at 95-99% cpu load(with one torrent running), wich means that the web interface takes very long to load, sometimes a minute or more. when using transmission-remote to list torrents and/or files it usually takes about 20-30 seconds before results turn up. :(
is this an issue with transmission or with the firmware on my router?:confused:
any tips on how to make it play nice again?
//Heathen
how big is the file(s) your trying to download?
and maybe it's hashing (looking if the data is not corrupted), wich can take a while and needs quite a lot of cpu;)
Well if i download a file bigger then 10Mb the cpu load goes way up there, this happens every time and not just on one file. and it started after the upgrade.
would it help if i uninstall transmission and delete all its files and reinstall it?
//Heathen
Well if i download a file bigger then 10Mb the cpu load goes way up there, this happens every time and not just on one file. and it started after the upgrade.
would it help if i uninstall transmission and delete all its files and reinstall it?
//Heathen
maybe, but if you remove it, you have to do it properly to test it's effect, so also remove the ".settings" folder:)
i've removed it and reinstalled, this time i skipped using a blocklist and now it plays nicer, cpu load have not yet gone above 65% and the web interface loads quick and nice.
not sure if it was the blocklist that was the problem, I'll add that later to see if the problem comes back. just want to test it a bit more with out the block list first.
//Heathen
gu4rd1an
23-04-2009, 00:05
Every time I reboot my wl500gpV2 transmission starts to "verify" my torrents.
I've in pre-shutdown a row that kill the daemon.
It's possible to shutdown/reboot the system avoiding the verify of the torrents on next boot?
gouryella
23-04-2009, 09:07
Every time I reboot my wl500gpV2 transmission starts to "verify" my torrents.
I've in pre-shutdown a row that kill the daemon.
It's possible to shutdown/reboot the system avoiding the verify of the torrents on next boot?
you must pause torrents before rebooting like:
transmission-remote -t all -S
sleep 5
and start after rebooting:
transmission-remote -t all -s
u can add to:
/usr/local/sbin/post-boot
/usr/local/sbin/pre-shutdown
or to: S90transmission-daemon (/opt replace /tmp/harddisk/ if u have like wengi)
#!/bin/sh
case $1 in
start)
echo "starting transmission"
/opt/bin/transmission-daemon -g /opt/transmission/config
sleep 3
transmission-remote -t all -s
;;
stop)
transmission-remote -t all -S
sleep 5
if [ -n "`pidof transmission-daemon`" ]; then
kill -9 `pidof transmission-daemon`
fi
;;
restart)
$0 stop
$0 start
;;
*)
echo "usage: $0 (start|stop|restart)"
exit 1
esac
gu4rd1an
23-04-2009, 11:44
thanks for your reply! I've just done like this before reading the post but I'm glad to see that it's the right solution :)
I am following wengi's tutorial everything works fine up till when I point the browser to transmission I get nothing. The transmission deamons start I check it through ps it shows up. But it wont pop up on the browser.
I have the wl-500w and I have installed this firmware perfectly last week for someone else. I don't know why it's not working now. Is it the new transmission 1.60. I have found another post there is a problem with the browser at the moment giving 404 error. I think it is the same issue I am experiencing. Is there somehow I can revert to a previous versiion.
Thanks in advance
Hi kolp, I'm experiencing the same problem I was using transmission until 1.6 and every thing was working fine but after updating to 1.60-1 it wasn't the conf. file is changed and moved if some one knows how can fix this please help
I have a Asus500gp and works fine with transmission. I want to know how how to connect/route all traffic from transmission to a SSH host
Thanks
Transmission supports proxies only for communication with the tracker not for p2p communication.
i. e. you cannot tunnel your p2p traffic with a regular ssh tunnel.
You will need an IP or ethernet tunnel, like openvpn, vtun, ppp, ... with routing setup accordingly.
Thanks for the reply.
I understand that part that I need openVPN. I just need to know how to
configure transmission to use openvpn to the remote host.
You have to configure your routing rules that all traffic goes over the VPN tunnel.
That maybe difficult, if you do not want to route all traffic on the WL-500gp over the VPN tunnel (even the one, that is not generated by transmission).
Then you would have to use policy based routing.
I was trying to get Transmission Remote to work and in doin so I installed a new version of transmission and then that version wasn't allowing me to connect through the web interface.
Anyways cut a long story short I am now able to connect to transmission though the web interafce but my torrents arn't downloading. On the web interface it shows that I am downloading some torrents at a certain speed but leave it a few hours and no progress. Another reason why I know the torrents arn't downloading is that the harddrive light on my external isn't showing that it's writting to the harddrive. Im not sure what file I edited which made this problem happen.
I have installed transmission 1.71
Can anyone please help me with this problem?
I was trying to get Transmission Remote to work and in doin so I installed a new version of transmission and then that version wasn't allowing me to connect through the web interface.
Anyways cut a long story short I am now able to connect to transmission though the web interafce but my torrents arn't downloading. On the web interface it shows that I am downloading some torrents at a certain speed but leave it a few hours and no progress. Another reason why I know the torrents arn't downloading is that the harddrive light on my external isn't showing that it's writting to the harddrive. Im not sure what file I edited which made this problem happen.
I have installed transmission 1.71
Can anyone please help me with this problem?
What I had to do is start watchdog =) but the thing is now after a lil while it stops, y is that, it never use to happen before?
ENDer2000
21-06-2009, 22:17
Any news about this?
I've searched the forum and I did not find any answer.
If you want to access any service from WAN, you have to open the desired ports in the firewall settings, and not disable the firewall completely.
If you do not describe what firmware you use, you will not get any help specific to it.
ENDer2000
22-06-2009, 11:41
If you want to access any service from WAN, you have to open the desired ports in the firewall settings, and not disable the firewall completely.
If you do not describe what firmware you use, you will not get any help specific to it.
I use Oleg firmware (latest) + latest Transmission and Samba2.
I need to access http://192.168.1.1:9091/transmission/web/ from outside (WAN)
Thank you!
I need to access http://192.168.1.1:9091/transmission/web/ from outside (WAN)
First:
You need to find public IP - 192.x.x.x is accessible only from lan.
Use ifconfig (use putty or web interface --> system setup --> system command) and find your IP - depends on your connection type (e.g. ppp0 for DSL).
If you have public static IP use http://YOUR_PUBLIC_IP:9091/transmission/web/
If you have dynamic IP (your ISP changes your IP) - use ddns service (in web interface go to IP Config --> Miscellaneous and use http://something.dyndns.org:9091/transmission/web
If you do not have public IP - you need to talk to your ISP and find, if it is possible to change IP to public or forward port.
Second:
Open port in firewall
nano /tmp/local/sbin/post-firewall
Find something like
## Allow access to various router services from WAN
for P in 51413 9091; do
iptables -I INPUT 1 -p tcp --syn -i "$1" --dport $P -j ACCEPT
done
And add 9091 port to accepted list.
Save changes:
flashfs save && flashfs commit && flashfs enable && reboot
ENDer2000
24-06-2009, 04:57
This is strange.
I runt the latest Transmission on my Asus WL500gp v2 router with latest Oleg Firmware + an WD USB HDD.
I have an stable and routable IP.
On a private tracker i'm reported as Unconnectable.
If I run uTorrent on the computer (on the network), on the same port, I'm immediately reported as Connectable.
I'm also reported Connectable If I download something with the Transmission from the Router.
My custom port is reported open and its forwarded from Virtual Server for my static network IP (192.168.1.6) and Router ip (192.168.1.1).
Any ideeas how to be Connectable all the time? It's like a passive mode now on DC++.
ENDer2000
24-06-2009, 05:11
It's working now, thank you!
ENDer2000
03-07-2009, 23:19
So, nothing about this? :(
luisfmoreira
14-10-2009, 16:37
Hi, I'm having an issue with transmission web ui over wan.
I have dyndns working and if I type adress.dyndns.org:9091 from my lan it works, if i try to access it from outside the lan it doesn't find the web site, although I can access my router with adress.dyndns.org:8080.
Here is my Json file. Do I need to change smthing in the firewall?
{
"blocklist-enabled": true,
"dht-enabled": true,
"download-dir": "/tmp/harddisk/transmission/download",
"encryption": 2,
"lazy-bitfield-enabled": true,
"open-file-limit": 64,
"peer-limit-global": 250,
"peer-limit-per-torrent": 60,
"peer-port": 51413,
"peer-port-random-enabled": false,
"peer-port-random-high": 65535,
"peer-port-random-low": 1024,
"peer-socket-tos": 8,
"pex-enabled": true,
"port-forwarding-enabled": false,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"rpc-authentication-required": false,
"rpc-enabled": true,
"rpc-password": "PASSWORD",
"rpc-port": 9091,
"rpc-username": "USERNAME",
"rpc-whitelist": "*.*.*.*",
"rpc-whitelist-enabled": true,
"speed-limit-down": 500,
"speed-limit-down-enabled": false,
"speed-limit-up": 20,
"speed-limit-up-enabled": true
}
if you have activated virtual dmz , deactivate it !
gouryella
14-10-2009, 17:08
Add "one" line to /tmp/local/sbin/post-firewall
iptables -D INPUT -j DROP
iptables -A INPUT -p tcp --dport 9091 -j ACCEPT
iptables -A INPUT -j DROP
Do not forget:
flashfs save && flashfs commit && flashfs enable && reboot
You can test 9091 port on CanYouSeeMe.org
luisfmoreira
14-10-2009, 17:52
Thanks guys it worked with the iptables thingy!
Can you please explain me if there is any diference by opening the port on iptables or by webinterface in the virtual servers?
Thanks
Tamadite
14-10-2009, 22:36
There should not be any difference but the best answer is by trying it yourself.
luisfmoreira
15-10-2009, 11:29
I did try before posting ... but it didn't work. I was just trying to understand why :D
Hello,
I access my transmission from WAN vert rare. That is why I would like to just temporary open the ports for the torrent client ( I have SSH acccess all the time). So I don't want to change post-firewall file. My idea is to have script/command which opends/closes the ports needed for transmission web to work on demand
Is there any difference in the way I have to open the port from a script . Shall I just run "iptables -A INPUT -p tcp --dport 9091 -j ACCEPT" in command prompt ?
How after this to close the port /delete the rule ?
Hello,
I experimened and found the way to create a on/off script for opening/closing transmission port. When is on, transmission can be acessed from the WAN (and Internet). It seems that only port 9091 is needed for the web client and .Net client. I'm using transmission version 1.75
#!/bin/sh
case $1 in
"on") iptables -I INPUT -p tcp --syn --dport 9091 -j ACCEPT;;
"off") iptables -D INPUT -p tcp --syn --dport 9091 -j ACCEPT;;
*) echo "Please enter on/off as argument !!! !!! ";;
esac
iptables -L INPUT