random ports and firestarter eating up cpu cycles

[logos34]

I'm using the default 'random ports' setting but my Ubuntu linux firewall gui (irestarter) is constantly lit up with blocked (i.e. silently dropped) hits from everyone trying to access the port chosen by Deluge. It uses up more and more cpu % until I clear the list of blocked hits. I'm behind a wired router.

Should I go to port forwarding and can someone help me with configuring? Portforwarding.com only has a guide for uTorrent and my particular router.

If someone could walk me through this I'd appreciate it.

[loki]

I would say adding firestarter firewall adds an additional unnecessary layer and complication, is most likely unneeded if you already have a router with a built-in firewall. Personally it's going to be a lot better than any software firewall available and doesn't eat up any cpu cycles.

As far as setting the port in deluge just enter the network preferences and set a single port number for both and set that same port in the router setting and allow for both tcp and udp. I would suggest a port above 7000 or so to not interfere with anything else.