DSM-G600, DNS-3xx and NSA-220 Hack Forum

Kylek,
I would need some help.
I am trying to to create a package of another build of Transmission 1.21 because one of my private trackers accepts only an old build.

I got an error about PKG_CONGIG and OPENSSL _CFLAGS
In transmission forum they are suggesting to install openssl-dev.
Do you have this package for funplug 0.5 ?

Thanks for your help.

Thank you for your help, I will do that this evening.

greg1977,
I think we use the same tracker
I tried 2 or 3 times to create the package, but I have problems launching it. It fails to connect to the daemon socket.

Kylek ,
I would need your help

I have downloaded the build we need, extracted it, and I do :

              ./configure --prefix=/ffp/devel/releases/Toolname-ffp0.5/ffp
              make
              make install

as you posted elsewhere. It works fine. I have 2 more files on the install ( transmissioncli and benc2php )
I have copied the former transmission.sh file in a start directory
After that I have done

            tar cf - -C /ffp/devel/releases/Toolname --owner=root --group=root . | gzip - -c >toolname-0.1.0-ffp0.5.tgz

Did it missed something ?
Is there another option to put on the configure ?
When I launch that build, the log file indicated that option -V is invalid and that it cannot access to the socket.

Thanks for your help.

Last edited by ppahtde (2008-06-14 13:23:29)

It's Working !! thanks

New version of Transmission is out:

1.22 (2008/06/13)
http://trac.transmissionbt.com/query?group=component&milestone=1.22&order=severity
- All Platforms
  + Fix two separate BitTorrent unchoke bugs that could affect performance
  + Transmission now builds correctly on Sun Studio
  + Minor man page fixes
- CLI:
  + Fix scraping torrents with the -s command-line argument

I updated the first post with the proper links.

Could you elaborate on this? I haven't used transmission-proxy before, I don't actually know what it's useful for.

Yes, the current SVN version of Transmission adds proxy support, as that was a much requested feature.
The authors of T also made radical changes to the way the clients (GTK client, transmission-remote) communicate with Transmission. As a result, Clutch does not work with the new version yet.
For that reason I haven't produced any nightly builds of Transmission 1.22+ (to be 1.30).

As soon as Clutch is (at least somewhat) compatible with the new Transmission, I'll start making builds.

Just updated fun_plug to 0.5 and tried to install Transmission 1.22, but when I enter ffp/start/transmission.sh start I get "cannot create /mnt/HD_a2/.transmission/transmission-daemon.log: Permission denied". Can anybody help me out? I'm logged in via ssh / root.

can anyone help why i hv the following messages in the www/logs/error.log
am i doing something wrong? i have this message every 1-2 second and the error.log file size now is about 100mb.


/clutch/remote/index.php?action=refreshTorrents&param=0&filter=all&sort_method=queue_order&sort_direction=ascending&search=
2008-07-02 10:50:25: (http_auth.c.1006) algorigthm 
2008-07-02 10:50:25: (http_auth.c.1007) qop auth
2008-07-02 10:50:25: (http_auth.c.1008) cnonce c6e12b32e27b408a
2008-07-02 10:50:25: (http_auth.c.1009) nc 00000183
2008-07-02 10:50:25: (http_auth.c.1010) response d6f580ac8852797a43731ae3650c9633
2008-07-02 10:50:25: (http_auth.c.1156) digest: auth ok
2008-07-02 10:50:27: (http_auth.c.1002) username admin
2008-07-02 10:50:27: (http_auth.c.1003) realm Password Protected Area
2008-07-02 10:50:27: (http_auth.c.1004) nonce 2e0aa5381b7cba11581ec32704de97d7
2008-07-02 10:50:27: (http_auth.c.1005) uri /clutch/remote/index.php?action=refreshTorrents&param=0&filter=all&sort_method=queue_order&sort_direction=ascending&search=
2008-07-02 10:50:27: (http_auth.c.1006) algorigthm 
2008-07-02 10:50:27: (http_auth.c.1007) qop auth
2008-07-02 10:50:27: (http_auth.c.1008) cnonce 0ee1d56673147b7b
2008-07-02 10:50:27: (http_auth.c.1009) nc 00000184
2008-07-02 10:50:27: (http_auth.c.1010) response d442ba9134a1289f8d72b35ad6b697a7
2008-07-02 10:50:27: (http_auth.c.1156) digest: auth ok
2008-07-02 10:50:28: (http_auth.c.1002) username admin
2008-07-02 10:50:28: (http_auth.c.1003) realm Password Protected Area
2008-07-02 10:50:28: (http_auth.c.1004) nonce 2e0aa5381b7cba11581ec32704de97d7
2008-07-02 10:50:28: (http_auth.c.1005) uri /clutch/remote/index.php?action=refreshTorrents&param=0&filter=all&sort_method=queue_order&sort_direction=ascending&search=
2008-07-02 10:50:28: (http_auth.c.1006) algorigthm 
2008-07-02 10:50:28: (http_auth.c.1007) qop auth
2008-07-02 10:50:28: (http_auth.c.1008) cnonce 1a7c2ee4e642e66b
2008-07-02 10:50:28: (http_auth.c.1009) nc 00000185
2008-07-02 10:50:28: (http_auth.c.1010) response 2ba6ab1fa70c8a3ebbf8ca03fd8cc8b9
2008-07-02 10:50:28: (http_auth.c.1156) digest: auth ok

KyleK wrote:

mong736 wrote:

can anyone help why i hv the following messages in the www/logs/error.log
am i doing something wrong? i have this message every 1-2 second and the error.log file size now is about 100mb.

Looks like someone is trying to get into your Clutch interface, possibly by using a brute-force attack. Can you access Clutch when providing a username/password?
If your lighttpd runs on port 80, a port change might be a good idea.

yes, i can access clutch with my username/password.
BTW, how to change port for lighttpd?

Thanks

KyleK wrote:

The etc/lighttpd.conf has an option "server.port = 80", change it to any number higher than 1024. If you want to access your web server from outside your LAN, make sure to forward the port in your router as well.

ok, just change the port already, restarted lighttpd, but the error.log file size still increasing and show the same thing as before.
but if i close the web access to clutch, the error.log seem to stop logging. is this normal?

KyleK wrote:

Dang, I didn't look closely enough at that log of yours. Basically, it's harmless. Lighttpd just logs any authentication attempts to your page (which your browser obviously has cached).

There's an option in your lighttpd.conf called "auth.debug = 2". You can set it to 0 to disable authentication logging completely, to 1 for just basic log entries (access failed/access ok), or to 2 for detailed log (as it is now).

You can change the port back if you want, there wasn't any issue with it.

And you can also delete the logfile to free some space (but stop the server first).

yes, it works!

thanks for your help.