The action or set of actions configures what action is performed if the rule matches. This is discussed in more details in the next section. If all of the conditions are true for the given session then the rules matches. The set of conditions is the description of the traffic that should match the rule. Trying to troubleshoot a set of rules all named "" can be extremely difficult. It is highly suggested to give the rule a meaningful name. The description is for the user to document what the rule does. If the enable checkbox is not checked, the rule is simply skipped. The enable checkbox determines if the rule is evaluated. This means that the "Source Address" will be the initiator of the session and the "Destination Address" will be the server address the client is connecting to, and the same is true for "Source Port" and "Destination Port." Unlike some other firewalls, Untangle evaluates against sessions, not packets. Untangle rules are "quick" rules which means the first match is always used. If no matching rule is found the behavior is defined by the application, which is usually doing nothing. If a rule matches then the action from that rule is performed and no more rules are evaluated. Rules are evaluated in order from top to bottom against sessions (not packets!).
Untangle firewall who is taking all the bandwidth how to#
Bandwidth Control uses rules to determine how to prioritize a session.
For example, Firewall uses rules to determine whether to block or pass traffic. Rules are configured by the user to categorize and act upon traffic. All of these rules essentially share the same logic. Many applications use rules like Firewall, Captive Portal, Application Control, Bandwidth Control, etc. This documentation describes how rules work and gives some basic examples and some common mistakes to avoid. Rules are very powerful, but can sometimes be difficult to configure. Rules are used frequently in Untangle and many other firewalls.