eMule kad firewalled

Comodo Internet Security - CIS Firewall Help - CIS
1

Hello everyone,
I use Comodo internet security premium 10 and I have a problem with eMule and firewall comodo.
I used the rules written below.

But the kad is firewalled.(test on TCP port is ok. Test on UDP port is failed)
If i try to disable the firewall, the kad is ok. So the problem is the firewall.

I checked the register of comodo, but there isn’t request of input on UDP port. Never.
If there isn’t request of input, how do it block UDP port?

Rule 1
• Action : Allow
• Protocol : TCP
• Direction : In
• Description : Rule for incoming TCP connections
• Source Address : Any Address
• Destination Address : Any Address
• Source port : A Port Range : (Start Port = 1025 / End Port = 65535)
• Destination port : A Single Port : (Port : Your TCP port of Shareaza/Emule)
Rule 2
• Action : Allow
• Protocol : UDP
• Direction : In
• Description : Rule for incoming UDP connections
• Source Address : Any Address
• Destination Address : Any Address
• Source port : A Port Range : (Start Port = 1025 / End Port = 65535)
• Destination port : A Single Port : (Port : Your UDP port of Shareaza/Emule)
Rule 3
• Action : Allow
• Protocol : TCP or UDP
• Direction : Out
• Description : Rule for outgoing TCP and UDP connections
• Source Address : Any Address
• Destination Address : Any Address
• Source port : A port range : (start port = 1025 / end port = 65535)
• Destination port : A port range : (start port = 1025 / end port = 65535)
Rule 4
• Action : Ask (Also select the check box ‘Log as a firewall event if this rule is fired’)
• Protocol : TCP
• Direction : Out
• Description : Rule for HTTP requests
• Source Address : Any Address
• Destination Address : Any Address
• Source port : A port range : (start port = 1025 / end port = 65535)
• Destination port : Type : Single Port; (Port : 80)
Rule 5
• Action : Block (Also select the check box ‘Log as a firewall event if this rule is fired’)
• Protocol : IP
• Direction : In/Out
• Description : Block and Log All Unmatching Requests
• Source Address : Any Address
• Destination Address : Any Address
• IP Details : IP Protocol : Any

2

I had forgotten one thing: days ago I had the same problem on TCP port. To solve the problem on TCP I added a global rule. I saw the green arrow on emule and I thought I had solved.

Today I realized that the kad was firewalled. Not remembering the solution of global rule I wrote the post.

Then i checked in the firewall and i found the global rule on TCP port.

Now, using the global rule for UDP port, emule works fine: the arrow of Kad is Green and kad is connected.

Last question: The system is safe with this 2 global rules?

Rule 1 in global
• Action : Allow
• Protocol : TCP
• Direction : In
• Description :
• Source Address : Any Address
• Destination Address : MAC address of PC
• Source port : A Port Range : (Start Port = 1025 / End Port = 65535)
• Destination port : A Single Port : (Port : Your TCP port of Emule)

Rule 2 in gloabal
• Action : Allow
• Protocol : UDP
• Direction : In
• Description :
• Source Address : Any Address
• Destination Address : MAC address of PC
• Source port : A Port Range : (Start Port = 1025 / End Port = 65535)
• Destination port : A Single Port : (Port : Your UDP port of Emule)

here are some post where it is spoken of this problem:
https://forums.comodo.com/firewall-help-cis/low-id-emule-comodo-firewall-problem-t92037.5.html
https://forums.comodo.com/firewall-help-cis/emule-low-id-and-firewalled-kad-t113418.0.html

3

The rules are fine but you really don’t need to define source port for each rule and instead you can set source port to any. It doesn’t really provide much of a benefit when you set a specific port range for the source port.