- Individual Applications
Protect
Filter
Perform
Connect
Add-Ons
- Software Packages
- Complete Appliances
|
|
#1 (permalink) |
|
Newbie
Join Date: Jan 2012
Posts: 5
![]() |
I am having problems getting the latest Untangle Firewall version to work correctly.
Ive created several rules to explicitly block traffic from internal to external where destination address is 192.168.1.1. Ive tried blocking all of 192.168.1.0 subnet with the following destination addresses: 192.168.1.50/255.255.255.0 (Taken from your example on blocking a range of IP's) 192.168.1.0/255.255.255.0 192.168.1.0/24 192.168.1.1-253 192.168.1.1-192.168.1.253 All of the rules I have ran independent of any others set to explicitly block. Internal network is 10.20.0.0/24, External is 192.168.1.0/24. Is it that ICMP always works from internal to external? Or am I doing something wrong? Last edited by ghernandez; 01-10-2012 at 01:15 PM.. Reason: Fixed |
|
|
|
|
#2 (permalink) |
|
Master Untangler
Join Date: Aug 2008
Location: Brazil (Sao Paulo)
Posts: 417
![]() |
Take a look here: http://wiki.untangle.com/index.php/IP_Matcher
Also, after add a rule to firewall give it a time, rules are not effective as soon they are created |
|
|
|
|
#3 (permalink) |
![]() ![]() Join Date: Jul 2010
Location: sfba
URLs submitted: 1
Posts: 1,137
![]() |
Firewall doesn't scan ICMP, you'll need to use the Packet Filter if you want to stop pings.
just try to RDP or something, the Firewall should block it..
__________________
Attention: Support on the Untangle Forums is provided by volunteers and community members. If you need official Untangle support please call or email support@untangle.com. |
|
|
![]() |
| Thread Tools | |
|
|