Bit Tornado rule for Comodo

Discussion in 'other firewalls' started by Joliet Jake, May 16, 2006.

Thread Status:
Not open for further replies.
  1. Joliet Jake

    Joliet Jake Registered Member

    Joined:
    Mar 1, 2005
    Posts:
    911
    Location:
    Scotland
    Hi,
    I used this rule someone gave me for allowing Bit Tornado through Comodo...

    Allow TCP in from ANY to MY IP where source port is ANY and remote port is the ports I set Bit Tornado to use.
    Allow UDP in from ANY to MY IP where source port is ANY and remote port is the ports I set Bit Tornado to use.

    Despite this rule being above the block rule I am still having problems with inbound connections. Log message...

    Date/Time :2006-05-16 18:24:25
    Severity :Medium
    Reporter :Network Monitor
    Description: Inbound Policy Violation (Access Denied, IP = 172.xxxxxxxxxx, Port = 50000)
    Protocol: TCP Incoming
    Source: 193.xxxxxxxxxxxxxx
    Remote: 172.xxxxxxxxxxxxxx
    TCP Flags: SYN
    Reason: Network Control Rule ID = 3

    Rule ID = 3 is the block rule; Block and log IP in from IP ANY to IP ANY where IPPROTO is ANY

    I have posted a help on their forum but I wondered if anyone here could help.:D

    Thanks in advance...

    JJ:cool:
     
  2. Stem

    Stem Firewall Expert

    Joined:
    Oct 5, 2005
    Posts:
    4,948
    Location:
    UK
    Are these "network rules"?
    If yes, then change your "source port" to the one in your torrent client, and the "remote port" to any.
    I am just starting to look into this firewall more deeply. So I will be setting up a few apps to check the comms (on app will be a torrent client). But for now, change the ports as I mentioned to check.

    EDIT,
    Have just ran a torrent client with the "network" rules I suggested, but Comodo is still blocking the inbound.
     
    Last edited: May 16, 2006
  3. Joliet Jake

    Joliet Jake Registered Member

    Joined:
    Mar 1, 2005
    Posts:
    911
    Location:
    Scotland
    Thanks for the reply Stem.

    What does this mean in the log?....TCP Flags: SYN
     
  4. Stem

    Stem Firewall Expert

    Joined:
    Oct 5, 2005
    Posts:
    4,948
    Location:
    UK
    SYN flag= connection

    For TCP connections there is an handshake.
    -> SYN
    <- SYN ACK
    -> ACK
    Then the data flow.
     
Loading...
Thread Status:
Not open for further replies.