The problem I am having is that Intrusion Prevention on the Sophos seems to be picking up and blocking inbound torrent traffic as it thinks it's a UDP flood. I have created an exception rule, but the specific problem with that is that the destination port keeps changing, even though I've specified (as noted above) that deluged should use a fixed port. Here are some example entries from my firewall log:
Code: Select all
2015:10:25-10:33:39 bob ulogd[27288]: id="2105" severity="info" sys="SecureNet" sub="ips" name="UDP flood detected" action="UDP flood" fwrule="60013" initf="eth1" srcmac="X" dstmac="Y" srcip="A" dstip="B" proto="17" length="1430" tos="0x00" prec="0x00" ttl="53" srcport="33373" dstport="60161"
2015:10:25-10:33:39 bob ulogd[27288]: id="2105" severity="info" sys="SecureNet" sub="ips" name="UDP flood detected" action="UDP flood" fwrule="60013" initf="eth1" srcmac="X" dstmac="Y" srcip="A" dstip="B" proto="17" length="48" tos="0x00" prec="0x00" ttl="109" srcport="11136" dstport="60161"
2015:10:25-10:33:39 bob ulogd[27288]: id="2105" severity="info" sys="SecureNet" sub="ips" name="UDP flood detected" action="UDP flood" fwrule="60013" initf="eth1" srcmac="X" dstmac="Y" srcip="A" dstip="B" proto="17" length="48" tos="0x00" prec="0x00" ttl="114" srcport="36262" dstport="60161"
2015:10:25-10:33:39 bob ulogd[27288]: id="2105" severity="info" sys="SecureNet" sub="ips" name="UDP flood detected" action="UDP flood" fwrule="60013" initf="eth1" srcmac="X" dstmac="Y" srcip="A" dstip="B" proto="17" length="48" tos="0x00" prec="0x00" ttl="116" srcport="36661" dstport="60161"
2015:10:25-10:33:40 bob ulogd[27288]: id="2105" severity="info" sys="SecureNet" sub="ips" name="UDP flood detected" action="UDP flood" fwrule="60013" initf="eth1" srcmac="X" dstmac="Y" srcip="A" dstip="B" proto="17" length="1430" tos="0x00" prec="0x00" ttl="51" srcport="12459" dstport="60161"
2015:10:25-10:33:40 bob ulogd[27288]: id="2105" severity="info" sys="SecureNet" sub="ips" name="UDP flood detected" action="UDP flood" fwrule="60013" initf="eth1" srcmac="X" dstmac="Y" srcip="A" dstip="B" proto="17" length="48" tos="0x00" prec="0x00" ttl="117" srcport="25282" dstport="60161"
Anyway, I was wondering if there is a way to fix the destination port for deluged. I actually thought that the settings noted above would make everything go through 56681 consistently, but apparently it doesn't. Of course, if anyone has any other suggestions on how to address this (short of turning of intrusion protection) I'd certainly be happy to hear them.
Another somewhat unrelated issue is that files downloaded seem to be set to read only for the group, which is a bit of a pain as I need to go in to chmod the permissions on all of them to move, rename, etc. This is a bit odd as my /etc/init/deluged.conf is configured with the default umask of 007. I otherwise basically followed the instructions on this site for configuration plus added something for logging. Here is the deluged.conf I use:
Code: Select all
# deluged - Deluge daemon
#
# The daemon component of Deluge BitTorrent client. Deluge UI clients
# connect to this daemon via DelugeRPC protocol.
description "Deluge daemon"
author "Deluge Team"
start on filesystem and static-network-up
stop on runlevel [016]
respawn
respawn limit 5 30
env uid=deluge
env gid=deluge
env umask=007
exec start-stop-daemon -S -c $uid:$gid -k $umask -x /usr/bin/deluged -- -d -l /var/log/deluge/daemon.log -L warning
When I check files that are downloaded, they are set to r only for the group. However, this doesn't seem to be consistent - sometimes the files are rwx. Any thoughts on what might be going on?
Any thoughts or suggestions would be most appreciated.