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!). 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.
0 kommentar(er)
