I hope someone can help me with this because it driving me nuts I'm running the latest RC on Kubuntu Linux using the guarddog interface to iptables which I really love but for some reason, it doesn't like deluge and will stop it from functioning. Even though I have enabled a custom tcp protocol in the advanced tab and enabled it. Do I have to enable other ports for the DHT and deluged to get it to work.
Please help me because if a disable the firewall rules within guarddog- it works a treat with just the tcp port forwarded through my router hardware firewall.
have you opened the listening port?
under the preferences, you can test to see if the active listening port is open - my guess is that you haven't allowed a rule for that.
I was being a complete idiot, doh!!!! I was opening the port on for local but not remote access, cannot believe how stupid I can be at times, thanks for the help.
Another question, now the port is open and receiving connections but the DHT is not working, is there a specific port or protocol that I should enable to allow this to function.
Another question, now the port is open and receiving connections but the DHT is not working, is there a specific port or protocol that I should enable to allow this to function.
Once again, cheers for the help.
DHT uses UDP, so you need to open that protocol as well as just TCP.
Thanks for that, I seem to have got it to work pretty well, but the DHT still doesn't seem to work with guarddog enabled but works when disabled. Does the DHT use a manually(during development) assigned port or does it use the same port assigned by TCP for UDP communications as well.
I would work this out myself but I cannot find where guarddog logs rejected packets and the like, any ideas
devil81 wrote:Thanks for that, I seem to have got it to work pretty well, but the DHT still doesn't seem to work with guarddog enabled but works when disabled. Does the DHT use a manually(during development) assigned port or does it use the same port assigned by TCP for UDP communications as well.
I would work this out myself but I cannot find where guarddog logs rejected packets and the like, any ideas