Author Archives: lantean

I’ve just managed to solve a quite annoying glitch. After booting Raspbian, Transmission was immediately unable to connect to transmission-daemon on port 9091.

After much digging, i’ve found out that:

– Restarting the service just makes things work
– I was getting a bunch of error messages in /var/log/daemon.log (re: bind)
– Several posts in few forums suggested that the service was being initialized before the network adapter was actually ready.

Long story short:

1. Launch raspi-config
2. Select: 3. Boot Options
3. Select: B2 Wait for Network at Boot

That’s all you need, pretty much. Next time you boot, transmission-remote-cli will be able to connect immediately.

First off, you need to figure out the path of your flash drive:

fdisk -l

Then… edit /etc/fstab as follows:

/dev/sda1 /mnt/flash vfat rw,user,umask=0002,uid=1001,gid=121 0 0

Note that umask is… the “inverted” regular file mask. This represents 665 (because we’re evil). As per uid + gid, you can figure it out by means of this command:

id username

Update:

The best filesystem to use, if you need to maintain compatibility between the Flash Drive you’ll use with your Raspberry, and macOS, is probably ExFat. Now, problem is: Linux doesn’t really support ExFat by default.

So, we’ll need to install it, as follows:

sudo apt-get install exfat-fuse

In such case, your /etc/fstab file should look like this:

/dev/sda1 /mnt/flash exfat. rw,user,umask=0002,uid=1001,gid=121 0 0

Installing Samba:

apt-get install samba samba-common-bin

Once there, edit /etc/samba/smb.conf as follows:

workgroup = [your_workgroup_name]



[SHARE-NAME]

comment=Samba Share

path=/PATH/TO/YOUR/SHARE

browseable=Yes

writeable=Yes

only guest=no

create mask=0777

directory mask=0777

public=no

At last, setup the Samba password:

smbpasswd -a YOUR_USERNAME

sudo su
apt-get update
apt-get install toilet figlet lolcat
toilet -F metal Lantean Box -w 200 -f shadow | lolcat

Let’s begin with the basics. We’ll need to upgrade the system to the latest, and update the apt-get database. Once ready, we’ll proceed with the transmission’s daemon + cli binaries, as follows:

sudo

apt-get update

apt-get upgrade

apt-get install transmission-cli transmission-common transmission-daemon transmission-remote-cli

Authentication:
By default, transmission requires you to setup username / password. Since our goal is *not* to expose Transmission to the open internet (and we’ll only use it via SSH), we’ll simply neutralize any kind of authentication:

nano /etc/transmission-daemon/settings.json

Once there, edit this snippet:

rpc-authentication-required: false

Logging:
We want Transmission to keep an events log. Anything that goes wrong during setup… must be persisted, otherwise, debugging it will be a nightmare.

The only way i’ve found to set this up, is by means of the Daemon Service Descriptor:

nano /lib/systemd/system/transmission-daemon.service

Once there, you want to add the logfile’s path. Make sure that the file exists, and Transmission’s user has enough permissions to edit it:

OPTIONS="--config-dir $CONFIG_DIR --logfile /var/log/transmission.log"

Filesystem Permissions:

Transmission’s user is specified in the transmission-daemon.service descriptor (which is debian-transmission). So… you really wanna make sure whatever shared folder you end up using, belongs to Transmission’s group.

usermod -a -G debian-transmission YOUR_USER

chgrp debian-transmission /DOWNLOADS/PATH

chmod 770 /DOWNLOADS/PATH

Magnets!

In order to begin downloading a magned, try the following:

transmission-remote-cli

(And press 'A')

Restarting Stopped

Last tip: If you need to restart all of your downloads at once, this command becomes quite handy:

transmission-remote -t all -s