The rule doesn't work

Discussion in 'Other Ghost Security Software' started by Pr()ZaC, Feb 15, 2006.

Thread Status:
Not open for further replies.
  1. Pr()ZaC

    Pr()ZaC Registered Member

    Joined:
    Feb 15, 2006
    Posts:
    2
    ...as I'm a noob and possibly doing something wrong.
    Anyway, with GW enabled, Azureus can't access the NAT capabilities inside the program.
    The NAT TCP is set to 49152, if I create a rule for that port (TCP/UDP allow for port 49152), GW still blocks it.
    Once I select Allow All from the GW interface, Azureus receives the OK from the NAT protocol.

    Any idea?
    Thanks!
     
  2. pbajoe

    pbajoe Registered Member

    Joined:
    Feb 13, 2006
    Posts:
    3
    Where in your rule list do you have this rule? By default, when you create a rule, it goes to the bottom. Rules are processed, in order, from top to bottom. It's likely the packets from your Azureus program are matching another rule before they get to your Allow rule. Make sure after you create the rule, you move it up in the list. Also, by default, the last rule is to block all. Your new rule needs to be above that rule.

    hth,

    Joe
     
  3. Pr()ZaC

    Pr()ZaC Registered Member

    Joined:
    Feb 15, 2006
    Posts:
    2
    Thanks.
    I'll try that ASAP.
     
Thread Status:
Not open for further replies.