RuleSet

Currently Intelligent Ports support below Rules.

This rule will cause a delay before client will get connected to its destination. Delay is measured in milliseconds and the value will be GLOBAL for one Port, but you can activate this rule for specific IP range(s) or for single IP. You can repeat this rule in RuleSet as many times as you require.

This rule will work for both protocols (TCP/UDP).

This rule will reject the client connection. You can activate this rule for specific IP range(s) or for single IP. You can repeat this rule in RuleSet as many times as you require.

This rule will work for both protocols (TCP/UDP).

This rule will limit the simultaneous number of connections from single IP. You can activate this rule for specific IP range(s) or for single IP. You can repeat this rule in RuleSet as many times as you require.

This rule will work only for TCP Ports.

This rule will limit the total number of connections to one port. You can not specify this rule in RuleSet. That’s a global rule for one port. Each port can have its own MAXCONNECTIONS limit.

This rule will work only for TCP Ports.

5.  ROUTE

        This rule will override the default mapped port/ip of Intelligent Port,        You can activate this rule for specific IP range(s) or for single IP. You can repeat this rule in RuleSet as many times as you require.

5.  LOADBALANCERANDAM

        This rule will activate load balancing for the InelligentPort. As a result every client connection will be mapped to a random destination ip from load balancing ips list. You can activate this rule for specific IP range(s) or for single IP. You  can repeat this rule in RuleSet as many times as you require.