- Individual Applications
Protect
Filter
Perform
Connect
Add-Ons
- Software Packages
- Complete Appliances
|
|
#1 (permalink) |
|
Newbie
Join Date: Oct 2010
Posts: 12
![]() |
I have a policy (see attachment) blocking port 0-79, 81-442, and 444-65535. It works great on blocking, but it is time consuming try to open another port the way I made this policy. Can someone advise me on an easier solution?
|
|
|
|
|
#3 (permalink) |
![]() ![]() Join Date: Apr 2008
Location: Phoenix, AZ
URLs submitted: 8
Posts: 15,454
![]() |
That default action is going away in the future.
The Firewall module blocks or passes things on a first rule match wins ideology. So make a general block rule that blocks everything, and just make sure your pass rules are above it. You don't need to fit everything into a single firewall rule.
__________________
Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879 |
|
|
|
|
#4 (permalink) |
|
Untangle Junkie
![]() Join Date: Nov 2006
Location: San Mateo, CA
URLs submitted: 10
Posts: 10,611
![]() |
That rule won't work unless you set source port to "any"
__________________
Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself. If you need Untangle support please call or email support@untangle.com |
|
|
|
|
#6 (permalink) |
|
Untangle Junkie
![]() Join Date: Nov 2006
Location: San Mateo, CA
URLs submitted: 10
Posts: 10,611
![]() |
If it helps, just assume that a rule with "source port" is set to anything besides ANY is effectively disabled.
edit: and you probably want to allow DNS traffic unless they are using the untangle server itself for DNS.
__________________
Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself. If you need Untangle support please call or email support@untangle.com Last edited by dmorris; 10-17-2011 at 11:52 AM.. |
|
|
![]() |
| Thread Tools | |
|
|