WebUI for headless device

Discussion of the Web Interface for Transmission, formerly known as Clutch. This applies to all version of Transmission
Aqualung
Posts: 21
Joined: Mon Oct 12, 2009 12:07 am

WebUI for headless device

Postby Aqualung » Mon Oct 12, 2009 12:12 am

Running latest Transmission 1.75 on a headless AirLive WMU-6500FS box. So far I've been using only the web interface, and I take it this doesn't unlock all the Transmission functionality, does it? Also, the Inspector "Information" and "Activity" tabs show no information: is that how it's supposed to be?

demons33derxx
Posts: 60
Joined: Tue Sep 08, 2009 12:34 am

Re: WebUI for headless device

Postby demons33derxx » Mon Oct 12, 2009 10:07 am

Seems about the same to me except for fine-tuning individual transfer rates and ratio.
I mean what other functionality do you mean?

Those tabs should show some sort of information. They shouldnt be blank.

Aqualung
Posts: 21
Joined: Mon Oct 12, 2009 12:07 am

Re: WebUI for headless device

Postby Aqualung » Mon Oct 12, 2009 2:06 pm

demons33derxx wrote:Seems about the same to me except for fine-tuning individual transfer rates and ratio.
I mean what other functionality do you mean?

Well, I don't see anything about a blocklist, I don't see any options about DHT, UPnP, proxy etc. Where are all of these? Aren't they supposed to be accessible/tweakable? I see, on the other hand, that the settings.json has some lines that might be relevant in this respect. Well, let's say that I don't really need all these in the WebUI, but I can simply change them manually in the settings.json file. Trouble is that I don't really know what they mean, and how to tweak these settings. Care to explain, for example, what the following mean?:

"blocklist-enabled": false,
"port-forwarding-enabled": false,
"preallocation": 1,

Can you at least point to some website that explains all the settings.json settings?

Those tabs should show some sort of information. They shouldnt be blank.

It looks like my particular Transmission build may be faulty. Some say this is, as a matter of fact, an issue with all Transmission 1.75 releases/builds. See also the bottom comments here: http://filodej.blogspot.com/2009/04/wmu-6500fs-deluge-115.html.

demons33derxx
Posts: 60
Joined: Tue Sep 08, 2009 12:34 am

Re: WebUI for headless device

Postby demons33derxx » Mon Oct 12, 2009 4:31 pm

http://trac.transmissionbt.com/wiki/Support is the support wiki in general with documentation.
Here's the relevant section to the json file editing. http://trac.transmissionbt.com/wiki/EditConfigFiles

Blocklist is the like a list of IPs that could be bad sources for data. Like PeerGuardian.
Port-Forwarding is the UPnP forwared/NAT traversal for computers behind routers
I dont know what the pre-allocation is, though most likely it deals with memory. I dont know if its RAM or hard-drive tho.

Are you running transmissioncli, transmission-remote, or transmission? I find some of the config settings can easily be changed using the transmissioncli. Here is the online man page for that http://linux.die.net/man/1/transmissioncli

It looks like my particular Transmission build may be faulty. Some say this is, as a matter of fact, an issue with all Transmission 1.75 releases/builds. See also the bottom comments here: http://filodej.blogspot.com/2009/04/wmu ... e-115.html.


Maybe. Im using Transmission 1.75 (9117) from the Ubuntu Repository. I have no issues viewing the data on Internet Explorer 6, Mozilla Firefox 3.5, Swiftfox 3.5, or Opera Mini 5 Beta. Seems like that site is using (9125) which is a later version

Aqualung
Posts: 21
Joined: Mon Oct 12, 2009 12:07 am

Re: WebUI for headless device

Postby Aqualung » Thu Oct 15, 2009 1:12 am

demons33derxx wrote:http://trac.transmissionbt.com/wiki/Support is the support wiki in general with documentation.
Here's the relevant section to the json file editing. http://trac.transmissionbt.com/wiki/EditConfigFiles

Thanks, but so far none of these websites offers much detail and/or explanation. What, e.g., are all those options that start with "rpc"? What's rpc-authentication-required"? What is "rpc" itself, and what's its use?

What I am concretely looking for, at this point, is a way to ask for authentication/password for accessing the Transmission WebUI. How would I do that? Otherwise anyone can stumble accidentally into my Transmission WebUI, and wreak havoc... Need to ask for some form of authentication. How do I enable that?

Blocklist is the like a list of IPs that could be bad sources for data. Like PeerGuardian.

Yes, I know what that is, but how do I use a blocklist w/Transmission? I have not been able to find any instructions on how to do that.
Are you running transmissioncli, transmission-remote, or transmission? I find some of the config settings can easily be changed using the transmissioncli. Here is the online man page for that http://linux.die.net/man/1/transmissioncli

transmission-daemon
Maybe. Im using Transmission 1.75 (9117) from the Ubuntu Repository. I have no issues viewing the data on Internet Explorer 6, Mozilla Firefox 3.5, Swiftfox 3.5, or Opera Mini 5 Beta. Seems like that site is using (9125) which is a later version

It looks like the particular 1.75 builds that I was using are faulty. I reverted to an earlier build, and now everything works fine.

Thanks for the reply btw. :)

demons33derxx
Posts: 60
Joined: Tue Sep 08, 2009 12:34 am

Re: WebUI for headless device

Postby demons33derxx » Fri Oct 16, 2009 1:23 pm

Thanks, but so far none of these websites offers much detail and/or explanation. What, e.g., are all those options that start with "rpc"? What's rpc-authentication-required"? What is "rpc" itself, and what's its use?

Remote Procedure Call. Simplest way for me to understand this is that RPC is the protocol that allows for a remote device/computer/client to access your local computer/server. Basically, its the protocol that allows for you to control your computer from different location by talking to the program in a way the program understands to take action as if the commands were produced locally on the server. Think of it as the backend, it does the work behind the scenes.

What I am concretely looking for, at this point, is a way to ask for authentication/password for accessing the Transmission WebUI. How would I do that? Otherwise anyone can stumble accidentally into my Transmission WebUI, and wreak havoc... Need to ask for some form of authentication. How do I enable that?

AND
how do I use a blocklist w/Transmission?

You should take a look at the manpage for transmission-daemon. Here are the relevant portions of the manpage (http://linux.die.net/man/1/transmission-daemon) that deal with that information.
-t --auth
Require clients to authenticate themselves. This doesn't do much
good unless username and password are also set.

-u --username username
Used for client authentication.

-v --password password
Used for client authentication.

-b --blocklist
Enable peer blocklists. Transmission understands the bluetack blocklist file format. New blocklists can be added by copying them into the
config-dir's "blocklists" subdirectory.

-B --no-blocklist
Disble blocklists.


You would have to pass these switches to the transmission-daemon when you execute it. So, if I was to execute transmission-daemon. I normally do something like:

transmission-daemon -b -t -u Bob -v Dobalina
What this command just did was start the transmission-daemon with blocklists enabled and authentication required. The valid authentication that will be accepted is the username of Bob and the password of Dobalina.
I hope you understand that. Good Luck.

Aqualung
Posts: 21
Joined: Mon Oct 12, 2009 12:07 am

Re: WebUI for headless device

Postby Aqualung » Fri Oct 16, 2009 11:46 pm

demons33derxx wrote:
You should take a look at the manpage for transmission-daemon.

Thanks, I managed to find the manpage on the transmissionbt website, though it wasn't very easy. I eventually settled for editing the Transmission setup file by hand.

Otherwise, how do you tell if the blocklist is working?

tanstaafl1963
Posts: 3
Joined: Mon Aug 31, 2009 10:02 pm

Re: WebUI for headless device

Postby tanstaafl1963 » Sun Oct 18, 2009 7:26 pm

demons33derxx

I followed the link below and it didn't include the blocklist parameters.

You should take a look at the manpage for transmission-daemon. Here are the relevant portions of the manpage (http://linux.die.net/man/1/transmission-daemon) that deal with that information.


However, when I run it as you suggest, a 'top' of the system shows the -b appearing in the command. Is that all we'll see, or will there be some entries in a log file somewhere?

BTW, By you username/password example, I'm guessing you're a Monkees fan :D

demons33derxx
Posts: 60
Joined: Tue Sep 08, 2009 12:34 am

Re: WebUI for headless device

Postby demons33derxx » Mon Oct 19, 2009 4:04 pm

tanstaafl1963 wrote:However, when I run it as you suggest, a 'top' of the system shows the -b appearing in the command. Is that all we'll see, or will there be some entries in a log file somewhere?

BTW, By you username/password example, I'm guessing you're a Monkees fan :D


The question is a bit of a snafu, as I dont use blocklists so I dont know if they "work" or not. Also, there is no effective way to know if the list is "working" unless you can test from a blocked IP.

Transmission does have a log that will verify that the blocklist was loaded. if you run the transmission-daemon in "foreground" mode with the '-f' switch. Which will print the log information to standard output, and will run in the foreground and you can redirect it to your own log file.

For example on my computer I can use the following command and redirect its output to translog.log
transmission-daemon -f -b -T 2> translog.log & && head translog.log

[11:53:26.190] Couldn't bind port 51413 on 0.0.0.0: Address already in use
[11:53:26.191] Couldn't bind port 51413 on ::: Address already in use
[11:53:26.191] RPC Server: Adding address to whitelist: 127.0.0.1
[11:53:26.191] RPC Server: Serving RPC and Web requests on port 8711
[11:53:26.191] Transmission 1.75 (9117) started
[11:53:26.316] Blocklist "level1.bin" contains 224221 entries
[11:53:26.341] Using libcurl 7.19.5
[11:53:26.441] Loaded 27 torrents

Line 6, I can only assume means that Transmission is blocking the IPs listed in Blocklist level1.bin, as you will not get this output on a normal non-blocklist run of transmission. I have not used extensively to know if the log file will output an actual occurence of a blocked IP unfortunately.

BTW, By you username/password example, I'm guessing you're a Monkees fan :D

Actually, they were a bit before my time. My reference was to the reference that the conscious hip hopper Del Tha Funkee Homosapien made.

Aqualung
Posts: 21
Joined: Mon Oct 12, 2009 12:07 am

Re: WebUI for headless device

Postby Aqualung » Mon Oct 19, 2009 4:14 pm

demons33derxx wrote:
You would have to pass these switches to the transmission-daemon when you execute it. So, if I was to execute transmission-daemon. I normally do something like:

transmission-daemon -b -t -u Bob -v Dobalina

Should I understand that if I do not specify, say, -b, as a command line parameter, Transmission won't load the blocklist regardless of what the settings.json file says? What if "blocklist" is enabled in the settings.json file? Would I still have to run the daemon with the -b parameter?

demons33derxx
Posts: 60
Joined: Tue Sep 08, 2009 12:34 am

Re: WebUI for headless device

Postby demons33derxx » Mon Oct 19, 2009 4:22 pm

Aqualung wrote:
demons33derxx wrote:
You would have to pass these switches to the transmission-daemon when you execute it. So, if I was to execute transmission-daemon. I normally do something like:

transmission-daemon -b -t -u Bob -v Dobalina

Should I understand that if I do not specify, say, -b, as a command line parameter, Transmission won't load the blocklist regardless of what the settings.json file says? What if "blocklist" is enabled in the settings.json file? Would I still have to run the daemon with the -b parameter?


I dont know you test it out and let us know.

Aqualung
Posts: 21
Joined: Mon Oct 12, 2009 12:07 am

Re: WebUI for headless device

Postby Aqualung » Mon Oct 19, 2009 4:38 pm

demons33derxx wrote:I dont know you test it out and let us know.

And there's another mysterious issue: Where does the blocklist come from? I noticed the livel1 file in the blocklist folder, though i certainly didn't put it there myself. Does it download in the background if you run Transmission with the -b directive?

demons33derxx
Posts: 60
Joined: Tue Sep 08, 2009 12:34 am

Re: WebUI for headless device

Postby demons33derxx » Mon Oct 19, 2009 4:49 pm

Aqualung wrote:
demons33derxx wrote:I dont know you test it out and let us know.

And there's another mysterious issue: Where does the blocklist come from? I noticed the livel1 file in the blocklist folder, though i certainly didn't put it there myself. Does it download in the background if you run Transmission with the -b directive?


Hmm... I dont know but now you have the X-Files music playing in my head.....


Well, actually I think I have semblance of an idea...but that still wouldnt satiate the question.


Return to “Web Interface”