Controlling (torrent) downloads thru webpage

Printable View

Show 40 post(s) from this thread on one page

09-12-2007, 16:22
Zapt

I reinstalled my whole router and installed transmission but it won't start the webinterface but is running on the router:

Quote:

admin 203 1 0 17:09 ? 00:00:00 transmissiond -p 65534 -w 300 -u -1 -d -1 -i /opt/var/run/transmission.pid /tmp/harddisk/torr
admin 206 203 0 17:09 ? 00:00:00 transmissiond -p 65534 -w 300 -u -1 -d -1 -i /opt/var/run/transmission.pid /tmp/harddisk/torr
admin 207 206 0 17:09 ? 00:00:00 transmissiond -p 65534 -w 300 -u -1 -d -1 -i /opt/var/run/transmission.pid /tmp/harddisk/torr

There seems to be no network issue since I can't connect to it even on the router:

Quote:

[admin@(none) root]$ telnet localhost 8008
telnet: Unable to connect to remote host (127.0.0.1): Connection refused
09-12-2007, 17:40
wirespot

You sure it listens to the right interface? Try "netstat -plnt".
09-12-2007, 21:34
Zapt

Here the NEW netstat...

Quote:

[admin@(none) root]$ netstat -tln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:7776 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:7777 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:515 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9100 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5431 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:65534 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3838 0.0.0.0:* LISTEN
tcp 0 0 :::22 :::* LISTEN
tcp 0 0 :::23 :::* LISTE
09-12-2007, 22:27
wirespot

It's not really helping if you don't pass those arguments I've told you about (-ptln). If you haven't installed Oleg's netstat then try without the "p", just -tln.
10-12-2007, 16:22
Zapt

Here's the new response (see above)
10-12-2007, 16:31
wirespot

OK, I see what's going on. You seem to have confused transmission and its web interface. Transmission is running, as you see transmissiond running and it listens on port 65534, as you can see in netstat. But you still need to run a webserver and use the CGI interface to transmission. Transmissiond is the client, but without the web interface to control it, it doesn't do anything, just sits there.
10-12-2007, 18:32
Zapt

So what do I need to do? I thought that the webinterface was already running...
10-12-2007, 18:40
wirespot

Well apparently not. Look around here in the tutorial section, there should be at least a couple of good ones for the complete setup.
10-12-2007, 18:42
Zapt

Well thanks for this nonsense answer...
I did everything like the tutorial of wengi said...
20-12-2007, 00:06
jrosado

2GB file size limit

Is the 2GB file size limit problem solved?
20-12-2007, 08:38
oleo

From my testing, Yes. Post your experience here.
20-12-2007, 15:03
jrosado

yes, it's solved..pity i did not see this sooner. I had a 7.53GB torrent and had to leave the computer on so i could get it all :D

anyway, great work :cool:
25-12-2007, 11:53
jrosado

Well..it seems I to have spotted another bug with torrents bigger than 2GB:

The download speed is to slow. In fact even other torrents (smaller than 2GB) are affected. An no, it's not the number of seeds. I tried it on my computer and the speed is fine.

As my understanding goes, it seems that this kind of torrents uses alot of the asus CPU, so it affects the others :confused:
27-06-2008, 22:05
boss

Transmission not accepting connections

My transmission 1.2.2 is not accepting inbound connections.
I'm using oleg's latest fw on 500gP v2.

I tried telneting (port 65534) from outside, not working.
I tried telneting (port 65534) from LAN, not working
Then I tried telneting (port 65534) from router to itself, still not working:

Code:

[admin@router root]$ telnet localhost 65534 Connection closed by foreign host.

netstat -lnt gives me this:

Code:

[admin@router root]$ netstat -lnt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN tcp 0 0 192.168.1.1:139 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5431 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:65534 0.0.0.0:* LISTEN tcp 0 0 :::22 :::* LISTEN

So it is kind of listening on 65534, but still no luck.
Webinterface is working, download is working @ fine speed, but I'm not connectable, not even from lan :mad:

I have firewall enabled, but both lan to wan and wan to lan filters are disabled. And I guess firewall should not block router from connecting to itself on port 65534.

What am I doing wrong :confused:

By the way, can someone explain precisely how to open port 65534 ? Is it via " virtual server" or "wan to lan" settings in router's webinterface ? Or is it done by using something else ?

EDIT:

I just tried to telnet from router to itself using a port that I know that is not open. Immediately, i get this:

Code:

[admin@router root]$ telnet localhost 12654 telnet: Unable to connect to remote host (127.0.0.1): Connection refused

But when I do try to connect port 65534, the message does not appear instantly, I need to wait a few seconds before I get the error I already mentioned: Connection closed by foreign host.
So my guess is that some sort of communication IS being done, but still, transmission does not accept connections...
27-06-2008, 22:59
wirespot

Does the outside telnet say the same thing? Because "connection closed by remote host" does not mean it's not working. It means it got through, it connected, then transmission closed the connection. BTW, how fast does that happen? Instantly, after you type something, after a delay?

If it wasn't listening at all or if the firewall got in the way you would've seen something different:

Code:

Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused

Or a long wait with no reaction whatsoever.

Add a -p option to your netstat to make sure it's transmission listening to that port and not something else.

That's about all I can contribute, since I don't use transmission nowadays anymore.

Edit: OK, I read your edit. I would guess that transmission accepts the connection, waits for a moment, then sees you're not sending through what you're supposed to (BT protocol stuff) and closes it. So I'd go on to guess that there's another reason you don't get remote connections. Off the top of my head here's several, in no particular order.

* Your ISP blocks them, either in bulk (any incoming connection in state NEW) or filters specifically for BT peer connections.
* You've set transmission to only accept encrypted peer connections and the torrents you're on currently don't have any peers on them that are willing to do that.
* You haven't opened the firewall properly after all. uTorrent has a webpage you can use to test this: enter here and see if you get an OK. Replace the port number in the URL with yours.
27-06-2008, 23:22
boss

Umm.. Everything works fine when I use utorrent on my desktop.. so my ISP is not blocking BT... And I haven't set it even to prefer encrypted connecitons ... so that one's out, too :(

I used lynx on my router to access that utorrent's page but it says my port is closed. I don't know if it's closed b/c lynx can't support this kind of check, or is it closed for real :)

Anyways, what's the right place to set up a rule to allow 65534 to the router ?

"Virtual server" or "wan to lan filters" or maybe something else ?
27-06-2008, 23:37
wirespot

Not "Virtual server", that's for opening ports on computers in your LAN to the outside. (Which brings me to an interesting question; you say uTorrent on your computer works, but how does IT get remote connections? Use the port test button in the uTorrent config.)

I think the easiest way is to run this command on the router:

Code:

iptables -I INPUT 1 -p tcp -i vlan1 \ --syn --dport 65534 -j ACCEPT

If you want to run it automatically after reboot put it in /usr/local/sbin/post-firewall, and it's recommended to replace vlan1 with "$1" if you do.

What this does is tell the firewall to allow connections in state NEW (TCP flag "syn") on port 65534, on the external router interface (vlan1). The rest is already taken care of, the firewall by default will allow connections to work once they're established.

You sure you don't wanna consider rtorrent? You can run it in the background, is one of the most advanced console clients, there are remote graphical interfaces for it and I've had no trouble with it for a while now.
27-06-2008, 23:59
boss

Actually, the tracker I mainly download from has some client restrictions, so I'm stuck with transmission.

As of uTorrent, I did do the forward in "virtual server" section and it worked like charm.

I will do the iptables trick, but I think it is gonna turn bad luck too, since transmission is not responding on 65534 when testing with telnet (although it should do, as I red before somewhere here on the forums).....

EDIT:

I did set the iptables as instructed here, but still no outgoing traffic. I tried with openOffice torrent file, which has enough seeders and leechers, but no outgoing traffic from my side.

Transmission is still not accepting connection when I try to telnet on port 65534.
Is there something I'm missing here ?

Edit #2:

I forgot to mention, after setting iptables in post-firewall, I do get port tested OK on utorrent port testing page. So my router is ready to receive packets but refuses to do so. Please help :(
29-06-2008, 15:21
boss

Is it possible that nobody ever had the similar problem ?

I really need some help on this one
29-06-2008, 15:41
wirespot

At this point I'd say it's most likely a problem with transmission itself. So double-check your settings and reread the transmission tutorials on the forum, that's about all the help I can give you.
29-06-2008, 16:49
boss

I think I'll reinstall everything from scratch, perhaps I made a mistake somewhere..
07-08-2008, 10:51
Tamadite

Quote:

Originally Posted by wengi

syslog is running and transmissiond is reporting to /opt/var/log/messages.
so far, so good.

The strange thing: There are no entries like

Code:

Feb 19 08:30:06 transmissiond[2078]: 1171870206 4 dl 145.39 ul 24.87 ld 1.23 Feb 19 08:35:06 transmissiond[2078]: 1171870506 4 dl 188.69 ul 25.14 ld 1.27 Feb 19 08:40:06 transmissiond[2078]: 1171870806 4 dl 172.64 ul 25.66 ld 1.48

I only see start and stop messages of transmissiond.
Webinterface shows 'Unable to find recent transfer stats in syslog'

Any idea?

I suffered from the same. It seems I had a uclibc-opt related problem. The following lines solved it.

Code:

mv /opt/etc/ipkg.conf /opt/etc/ipkg.old /bin/echo "src unslung http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable" > /opt/etc/ipkg.conf /bin/echo "dest root /" >> /opt/etc/ipkg.conf ipkg update && ipkg install uclibc-opt && /usr/bin/awk '/^Package:/{system("ipkg install -force-reinstall -force-defaults " $2)}' /opt/lib/ipkg/status
01-12-2008, 00:05
examiner

Is it normal to have transmission runnning three times - each time consuming 8MB of RAM?

Code:

PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 135 ? S 0:00 21 1179 1520 244 0.8 /sbin/syslogd -m 0 -O / 141 ? Ss 0:00 22 65 910 332 1.1 /opt/sbin/cron 150 ? Ss 0:00 50 174 1197 300 0.9 /opt/sbin/xinetd -pidfi 162 ? Ss 0:00 65 771 1500 636 2.1 /opt/sbin/nmbd -D 168 ? S 0:00 143 535 5292 3016 9.9 /opt/bin/transmission-d 169 ? S 0:00 0 535 5292 3016 9.9 /opt/bin/transmission-d 170 ? S 7:56 138 535 5292 3016 9.9 /opt/bin/transmission-d 280 ? Ss 0:00 20 1998 1601 284 0.9 /opt/sbin/smbd -D 393 ? Ss 0:01 57 327 1504 400 1.3 dropbear 394 pts/0 Ss 0:00 118 1179 1556 492 1.6 -sh 413 pts/0 R+ 0:00 105 69 1374 472 1.5 ps -xv

transmission is being started as

Code:

/opt/bin/transmission-daemon -g /opt/etc/transmision

(my config dir) - i used wpte's scripts from http://wl500g.info/showthread.php?t=15589 - start using script in /opt/etc/init.d

so is it normal that transmission consumes so much memory or am I doing something wrong?

Thanx
01-12-2008, 00:18
wirespot

Do you by any chance have 3 torrents running? If I recall correctly, it will spawn one instance for each one.

The memory readout is misleading. Much of it is shared among instances.
01-12-2008, 18:20
examiner

No...the readings are the same for none or 5 torrents running. Even just after the system boot when no torrent is running. Anyway, the memory consumption is quite bad - 30M with no significant difference between 0 or 5 torrents running.
01-12-2008, 19:09
wirespot

Filling up all the RAM and a couple dozen MB in swap is perfectly normal. It's being taken up by disk buffers and cache, no use having empty RAM. Run free and see what that tells you.

Show 40 post(s) from this thread on one page