Transmission

etlunatic

Same problem here, QTransmission handshakes fine but cannot write or does not have permission to write on the Hard Drive.

Any idea, suggestion?
This thread is about a port of the transmission-daemon to Windows, QTransmission (a.k.a. QtTransmission or QTr) is a different animal.

It is a know bug ...

etlunatic

I am having problems with Transmission for Windows (I have tried all builds linked on the previous page, including 1.6). For some reason, even though my ports are forwarded fine, I really struggle to connect to any seeders - occasionally I will connect to one, but then after a short while the ...

etlunatic

This is a follow-up on this post.

Is there any good reason why transmission 1.72 (with DHT enabled) should repeatedly and stubbornly try to connect to specific peers on port 21 (ftp) or port 23 (telnet)?

File dht.dat available on demand.

Regards

etlunatic

1.71 builds fine on FreeBSD 7.2.

I send a pm to rtorrent/libtorrent developer but I got no response. I don't think it is related to rtorrent.

Last note, my honey pot is up and running in dmz, come on bees (especially RBN bees) show me what you got.

etlunatic

did you install transmission-gtk2?

run ./configure -h and look at the options.

I built transmission 1.71 (daemon plus cli plus www) without problem on FreeBsd 7.2.

etlunatic

UPdate: 1.70 doesn't compile on FreeBSD 7.2. Many errors in dht.c.

etlunatic

As I said, I experienced some security problems when I used rtorrent with DHT enabled.

I am going to build transmission 1.70 on FreeBSD 7.2, I will change however my peer id to that of utorrent, I am going to run it with DHT enabled and I wll post pertaining excerpts of my pflogs and logs logs.

etlunatic

Running transmission under root is not a very good idea, especially since dht is around the corner.

Despite and against what has been said in this forum, the dht protocole is not very secured. I am using both rtorrent and transmission in a jail with sshd and ftpd disabled. With dht-enabled ...

etlunatic

Hi there,

I am using transmission Transmission 1.61 (8385) from ports in a jail on FreeBSD 7.2 without any problem.

I connect to the daemon with transmission-remote, www/transmission-web in ports and http://code.google.com/p/transmisson-remote-gui/ .

Did you build from ports?

Under what user are ...

etlunatic

For the record, as I never got the TOS option to work (I suspect the NAT rule in pf reset the TOS although it is undocumented), I am moving to plan B which is to run the daemon under a dedicated user (e.g. transmission) and set out the parameter "user" in the packet filter rule as shown below ...

etlunatic

Here is what I get with tcpdump for a packet sent by the transmission daemon:

Code: Select all

Some_Time_Stamp IP (tos 0x0, ttl 64, id 29049, offset 0, flags [DF], proto TCP (6), length 60) My_IP.51480 > Some_IP.12071: [|tcp]

It doesn't look the packet tos is anything close to 0x20

etlunatic

I changed my pf.conf to this:

Code: Select all

pass out quick on $ext_if inet proto { tcp udp } from $ext_if to any tos 32 no state queue q_bittorrent 
pass out quick on $ext_if inet proto tcp from $ext_if to any tos lowdelay queue q_tcp_ack

Still no traffic.

etlunatic

Hi there,

I am new to transmission and I have a question about the use of the peer-socket-tos option.

In my settings.json, I have:
"peer-socket-tos": 32

I am using FreeBSD with PF and ALTQ. In my pf.conf, I have something like:
pass out quick on $ext_if inet proto { tcp udp } from $ext_if to ...

Transmission

Search found 13 matches

Re: Transmission for Windows

Re: Transmission for Windows

transmssion 1.72 hammering peers on ports 21 and 23

Re: Problem with Daemon 1.61 and FreeBSD

Re: how to upgrade transmission to 1.71(Freebsd)

Re: Problem with Daemon 1.61 and FreeBSD

Re: Problem with Daemon 1.61 and FreeBSD

Re: Problem with Daemon 1.61 and FreeBSD

Re: Problem with Daemon 1.61 and FreeBSD

Re: Question on peer-socket-tos

Re: Question on peer-socket-tos

Re: Question on peer-socket-tos

Question on peer-socket-tos