- Individual Applications
Protect
Filter
Perform
Connect
Add-Ons
- Software Packages
- Complete Appliances
|
|
#12 (permalink) |
|
Untangle Junkie
![]() Join Date: Nov 2006
Location: San Mateo, CA
URLs submitted: 10
Posts: 10,611
![]() |
Untangle is shutdown until Tuesday for Christmas.
Someone will probably get back to you after that.
__________________
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 |
|
|
|
|
#13 (permalink) |
|
Newbie
Join Date: Jan 2012
Posts: 5
![]() |
I too am having problems getting this new 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. Is it that ICMP always works from internal to external? Or am I doing something wrong? My Primary gateway is 192.168.1.254, Id like the internal network to continue to have internet access outbound. I am only trying to limit access into the 192.168.1.x network Last edited by ghernandez; 01-10-2012 at 10:26 AM.. Reason: more information. |
|
|
|
|
#14 (permalink) | |
|
Untangle Junkie
![]() Join Date: Nov 2006
Location: San Mateo, CA
URLs submitted: 10
Posts: 10,611
![]() |
Quote:
__________________
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 |
|
|
|
![]() |
| Thread Tools | |
|
|