- |
+ |
@@ -96,7 +97,7 @@ easy"
-
+
What is it?
@@ -107,7 +108,7 @@ easy"
-
+
The Shoreline Firewall, more commonly known as "Shorewall", is a
Netfilter (iptables) based firewall
that can be used on a dedicated firewall system, a multi-function
@@ -121,26 +122,26 @@ easy"
-
+
This program is free software; you can redistribute it and/or modify
- it under the terms of Version 2 of the GNU General
Public License as published by the Free Software Foundation.
-
+
- This program is distributed in the hope
- that it will be useful, but WITHOUT ANY WARRANTY;
- without even the implied warranty of MERCHANTABILITY
- or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
+ This program is distributed in the
+ hope that it will be useful, but WITHOUT ANY
+ WARRANTY; without even the implied warranty of MERCHANTABILITY
+ or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
-
+
- You should have received a copy of the
- GNU General Public License along with
-this program; if not, write to the Free Software
-Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
+ You should have received a copy of
+the GNU General Public License along with
+ this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
USA
@@ -151,7 +152,7 @@ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
-
+
Copyright 2001, 2002, 2003 Thomas M. Eastep
@@ -162,28 +163,29 @@ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
-
+
+
- Jacques Nilo and Eric Wolzak
- have a LEAF (router/firewall/gateway on a floppy, CD
- or compact flash) distribution called Bering
- that features Shorewall-1.3.10 and Kernel-2.4.18.
+ Jacques Nilo and Eric Wolzak
+ have a LEAF (router/firewall/gateway on a floppy, CD
+ or compact flash) distribution called Bering
+ that features Shorewall-1.3.10 and Kernel-2.4.18.
You can find their work at: http://leaf.sourceforge.net/devel/jnilo
-
+
-
+
Congratulations to Jacques and Eric on the recent release of Bering
1.0 Final!!!
-
+
-
+
This is a mirror of the main Shorewall web site at SourceForge (http://shorewall.sf.net)
@@ -198,7 +200,7 @@ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
-
+
News
@@ -209,7 +211,7 @@ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
-
+
@@ -217,448 +219,456 @@ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
-
+
2/4/2003 - Shorewall 1.3.14-RC1 
-
-
+
+
Includes the Beta 2 content plus support for OpenVPN tunnels.
-
- The beta may be downloaded from:
-
-
+
+ The release candidate may be downloaded from:
+
+
http://www.shorewall.net/pub/shorewall/Beta
- ftp://ftp.shorewall.net/pub/shorewall/Beta
-
-
+ ftp://ftp.shorewall.net/pub/shorewall/Beta
+
+
1/28/2003 - Shorewall 1.3.14-Beta2
-
-
+
+
Includes the Beta 1 content plus restores VLAN device names of the
- form $dev.$vid (e.g., eth0.1)
-
+ form $dev.$vid (e.g., eth0.1)
+
The beta may be downloaded from:
-
-
+
+
http://www.shorewall.net/pub/shorewall/Beta
- ftp://ftp.shorewall.net/pub/shorewall/Beta
-
-
+ ftp://ftp.shorewall.net/pub/shorewall/Beta
+
+
1/25/2003 - Shorewall 1.3.14-Beta1
-
-
-
+
+
+
The Beta includes the following changes:
-
-
+
+
- - An OLD_PING_HANDLING option has been added to shorewall.conf.
- When set to Yes, Shorewall ping handling is as it has always been (see http://www.shorewall.net/ping.html).
-
- When OLD_PING_HANDLING=No, icmp echo (ping) is handled via rules and
-policies just like any other connection request. The FORWARDPING=Yes option
-in shorewall.conf and the 'noping' and 'filterping' options in /etc/shorewall/interfaces
-will all generate an error.
-
-
- - It is now possible to direct Shorewall to create a "label"
-such as "eth0:0" for IP addresses that it creates under ADD_IP_ALIASES=Yes
-and ADD_SNAT_ALIASES=Yes. This is done by specifying the label instead of
-just the interface name:
-
- a) In the INTERFACE column of /etc/shorewall/masq
- b) In the INTERFACE column of /etc/shorewall/nat
-
- - When an interface name is entered in the SUBNET column of
-the /etc/shorewall/masq file, Shorewall previously masqueraded traffic from
-only the first subnet defined on that interface. It did not masquerade traffic
- from:
-
- a) The subnets associated with other addresses on the interface.
- b) Subnets accessed through local routers.
-
- Beginning with Shorewall 1.3.14, if you enter an interface name in the
- SUBNET column, shorewall will use the firewall's routing table to construct
- the masquerading/SNAT rules.
-
- Example 1 -- This is how it works in 1.3.14.
-
-
+ - An OLD_PING_HANDLING option has been added to shorewall.conf.
+ When set to Yes, Shorewall ping handling is as it has always been (see http://www.shorewall.net/ping.html).
+
+ When OLD_PING_HANDLING=No, icmp echo (ping) is handled via rules and
+ policies just like any other connection request. The FORWARDPING=Yes option
+ in shorewall.conf and the 'noping' and 'filterping' options in /etc/shorewall/interfaces
+ will all generate an error.
+
+
+ - It is now possible to direct Shorewall to create a "label"
+ such as "eth0:0" for IP addresses that it creates under ADD_IP_ALIASES=Yes
+ and ADD_SNAT_ALIASES=Yes. This is done by specifying the label instead of
+ just the interface name:
+
+ a) In the INTERFACE column of /etc/shorewall/masq
+ b) In the INTERFACE column of /etc/shorewall/nat
+
+ - When an interface name is entered in the SUBNET column of
+ the /etc/shorewall/masq file, Shorewall previously masqueraded traffic
+from only the first subnet defined on that interface. It did not masquerade
+traffic from:
+
+ a) The subnets associated with other addresses on the interface.
+ b) Subnets accessed through local routers.
+
+ Beginning with Shorewall 1.3.14, if you enter an interface name in
+the SUBNET column, shorewall will use the firewall's routing table to
+construct the masquerading/SNAT rules.
+
+ Example 1 -- This is how it works in 1.3.14.
+
+
[root@gateway test]# cat /etc/shorewall/masq
#INTERFACE SUBNET ADDRESS
eth0 eth2 206.124.146.176
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE
-
+
[root@gateway test]# ip route show dev eth2
192.168.1.0/24 scope link
192.168.10.0/24 proto kernel scope link src 192.168.10.254
-
+
[root@gateway test]# shorewall start
...
Masqueraded Subnets and Hosts:
To 0.0.0.0/0 from 192.168.1.0/24 through eth0 using 206.124.146.176
To 0.0.0.0/0 from 192.168.10.0/24 through eth0 using 206.124.146.176
Processing /etc/shorewall/tos...
- When upgrading to Shorewall 1.3.14, if you have multiple local subnets
- connected to an interface that is specified in the SUBNET column of an
+ When upgrading to Shorewall 1.3.14, if you have multiple local subnets
+ connected to an interface that is specified in the SUBNET column of an
/etc/shorewall/masq entry, your /etc/shorewall/masq file will need changing.
In most cases, you will simply be able to remove redundant entries. In some
cases though, you might want to change from using the interface name to
listing specific subnetworks if the change described above will cause masquerading
to occur on subnetworks that you don't wish to masquerade.
-
- Example 2 -- Suppose that your current config is as follows:
-
+
+ Example 2 -- Suppose that your current config is as follows:
+
[root@gateway test]# cat /etc/shorewall/masq
#INTERFACE SUBNET ADDRESS
eth0 eth2 206.124.146.176
eth0 192.168.10.0/24 206.124.146.176
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE
-
+
[root@gateway test]# ip route show dev eth2
192.168.1.0/24 scope link
192.168.10.0/24 proto kernel scope link src 192.168.10.254
[root@gateway test]#
- In this case, the second entry in /etc/shorewall/masq is no longer
-required.
-
- Example 3 -- What if your current configuration is like this?
-
+ In this case, the second entry in /etc/shorewall/masq is no longer
+ required.
+
+ Example 3 -- What if your current configuration is like this?
+
[root@gateway test]# cat /etc/shorewall/masq
#INTERFACE SUBNET ADDRESS
eth0 eth2 206.124.146.176
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE
-
+
[root@gateway test]# ip route show dev eth2
192.168.1.0/24 scope link
192.168.10.0/24 proto kernel scope link src 192.168.10.254
[root@gateway test]#
- In this case, you would want to change the entry in /etc/shorewall/masq
- to:
-
+ In this case, you would want to change the entry in /etc/shorewall/masq
+ to:
+
#INTERFACE SUBNET ADDRESS
eth0 192.168.1.0/24 206.124.146.176
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE
-
-
+
+
- The beta may be downloaded from:
-
+ The beta may be downloaded from:
+
http://www.shorewall.net/pub/shorewall/Beta
- ftp://ftp.shorewall.net/pub/shorewall/Beta
-
-
+ ftp://ftp.shorewall.net/pub/shorewall/Beta
+
+
1/18/2003 - Shorewall 1.3.13 Documentation in PDF Format
-
+
-
+
Juraj Ontkanin has produced a PDF containing the Shorewall 1.3.13
- documenation. the PDF may be downloaded from
-
+ ftp://slovakia.shorewall.net/mirror/shorewall/pdf/
- http://slovakia.shorewall.net/pub/shorewall/pdf/
-
+
1/17/2003 - shorewall.net has MOVED
-
+
Thanks to the generosity of Alex Martin and Rett Consulting, www.shorewall.net and
ftp.shorewall.net are now hosted on a system in Bellevue, Washington. A
big thanks to Alex for making this happen.
-
-
+
+
1/13/2003 - Shorewall 1.3.13
-
-
+
+
Just includes a few things that I had on the burner:
-
-
+
+
- - A new 'DNAT-' action has been added for entries in the
-/etc/shorewall/rules file. DNAT- is intended for advanced users who wish
-to minimize the number of rules that connection requests must traverse.
-
- A Shorewall DNAT rule actually generates two iptables rules: a header
- rewriting rule in the 'nat' table and an ACCEPT rule in the 'filter' table.
- A DNAT- rule only generates the first of these rules. This is handy when
- you have several DNAT rules that would generate the same ACCEPT rule.
-
- Here are three rules from my previous rules file:
-
- DNAT net dmz:206.124.146.177 tcp smtp - 206.124.146.178
- DNAT net dmz:206.124.146.177 tcp smtp - 206.124.146.179
- ACCEPT net dmz:206.124.146.177 tcp www,smtp,ftp,...
-
- These three rules ended up generating _three_ copies of
-
- ACCEPT net dmz:206.124.146.177 tcp smtp
-
- By writing the rules this way, I end up with only one copy of
-the ACCEPT rule.
-
- DNAT- net dmz:206.124.146.177 tcp smtp - 206.124.146.178
- DNAT- net dmz:206.124.146.177 tcp smtp - 206.124.146.179
- ACCEPT net dmz:206.124.146.177 tcp www,smtp,ftp,....
-
-
- - The 'shorewall check' command now prints out the applicable
- policy between each pair of zones.
-
-
- - A new CLEAR_TC option has been added to shorewall.conf.
- If this option is set to 'No' then Shorewall won't clear the current traffic
- control rules during [re]start. This setting is intended for use by people
- that prefer to configure traffic shaping when the network interfaces come
- up rather than when the firewall is started. If that is what you want to
- do, set TC_ENABLED=Yes and CLEAR_TC=No and do not supply an /etc/shorewall/tcstart
- file. That way, your traffic shaping rules can still use the 'fwmark' classifier
- based on packet marking defined in /etc/shorewall/tcrules.
-
-
- - A new SHARED_DIR variable has been added that allows distribution
- packagers to easily move the shared directory (default /usr/lib/shorewall).
- Users should never have a need to change the value of this shorewall.conf
- setting.
-
-
+ - A new 'DNAT-' action has been added for entries in the
+ /etc/shorewall/rules file. DNAT- is intended for advanced users who wish
+ to minimize the number of rules that connection requests must traverse.
+
+ A Shorewall DNAT rule actually generates two iptables rules: a
+header rewriting rule in the 'nat' table and an ACCEPT rule in the 'filter'
+table. A DNAT- rule only generates the first of these rules. This is handy
+when you have several DNAT rules that would generate the same ACCEPT rule.
+
+ Here are three rules from my previous rules file:
+
+ DNAT net dmz:206.124.146.177 tcp smtp - 206.124.146.178
+ DNAT net dmz:206.124.146.177 tcp smtp - 206.124.146.179
+ ACCEPT net dmz:206.124.146.177 tcp www,smtp,ftp,...
+
+ These three rules ended up generating _three_ copies of
+
+ ACCEPT net dmz:206.124.146.177 tcp smtp
+
+ By writing the rules this way, I end up with only one copy of
+ the ACCEPT rule.
+
+ DNAT- net dmz:206.124.146.177 tcp smtp - 206.124.146.178
+ DNAT- net dmz:206.124.146.177 tcp smtp - 206.124.146.179
+ ACCEPT net dmz:206.124.146.177 tcp www,smtp,ftp,....
+
+
+ - The 'shorewall check' command now prints out the applicable
+ policy between each pair of zones.
+
+
+ - A new CLEAR_TC option has been added to shorewall.conf.
+ If this option is set to 'No' then Shorewall won't clear the current
+traffic control rules during [re]start. This setting is intended for
+use by people that prefer to configure traffic shaping when the network
+interfaces come up rather than when the firewall is started. If that
+is what you want to do, set TC_ENABLED=Yes and CLEAR_TC=No and do not
+supply an /etc/shorewall/tcstart file. That way, your traffic shaping
+rules can still use the 'fwmark' classifier based on packet marking defined
+in /etc/shorewall/tcrules.
+
+
+ - A new SHARED_DIR variable has been added that allows
+distribution packagers to easily move the shared directory (default /usr/lib/shorewall).
+ Users should never have a need to change the value of this shorewall.conf
+ setting.
+
+
-
+
1/6/2003 - BURNOUT
-
+
-
+
Until further notice, I will not be involved in either Shorewall
- Development or Shorewall Support
+ Development or Shorewall Support
-
+
-Tom Eastep
-
+
-
+
12/30/2002 - Shorewall Documentation in PDF Format
-
- Juraj Ontkanin has produced a PDF containing the Shorewall 1.3.12
- documenation. the PDF may be downloaded from
-
+
+ Juraj Ontkanin has produced a PDF containing the Shorewall 1.3.12
+ documenation. the PDF may be downloaded from
+
+
+
ftp://slovakia.shorewall.net/mirror/shorewall/pdf/
- http://slovakia.shorewall.net/pub/shorewall/pdf/
-
+
-
+
+
12/27/2002 - Shorewall 1.3.12 Released
-
+
Features include:
-
+
-
+
- - "shorewall refresh" now reloads the traffic shaping
- rules (tcrules and tcstart).
- - "shorewall debug [re]start" now turns off debugging
- after an error occurs. This places the point of the failure near
-the end of the trace rather than up in the middle of it.
- - "shorewall [re]start" has been speeded up by more
- than 40% with my configuration. Your milage may vary.
- - A "shorewall show classifiers" command has been
- added which shows the current packet classification filters. The
-output from this command is also added as a separate page in "shorewall
-monitor"
- - ULOG (must be all caps) is now accepted as a valid
- syslog level and causes the subject packets to be logged using the
- ULOG target rather than the LOG target. This allows you to run ulogd
- (available from "shorewall refresh" now reloads the traffic
+shaping rules (tcrules and tcstart).
+ - "shorewall debug [re]start" now turns off debugging
+ after an error occurs. This places the point of the failure near
+ the end of the trace rather than up in the middle of it.
+ - "shorewall [re]start" has been speeded up by
+more than 40% with my configuration. Your milage may vary.
+ - A "shorewall show classifiers" command has been
+ added which shows the current packet classification filters. The
+ output from this command is also added as a separate page in "shorewall
+ monitor"
+ - ULOG (must be all caps) is now accepted as a
+valid syslog level and causes the subject packets to be logged using
+the ULOG target rather than the LOG target. This allows you to run
+ulogd (available from http://www.gnumonks.org/projects/ulogd)
- and log all Shorewall messages to a separate log file.
- - If you are running a kernel that has a FORWARD
-chain in the mangle table ("shorewall show mangle" will show you
-the chains in the mangle table), you can set MARK_IN_FORWARD_CHAIN=Yes
-in shorewall.conf. This allows for marking
- input packets based on their destination even when you are using
- Masquerading or SNAT.
- - I have cluttered up the /etc/shorewall directory
- with empty 'init', 'start', 'stop' and 'stopped' files. If you already
+
- If you are running a kernel that has a FORWARD
+ chain in the mangle table ("shorewall show mangle" will show you
+ the chains in the mangle table), you can set MARK_IN_FORWARD_CHAIN=Yes
+ in shorewall.conf. This allows for
+marking input packets based on their destination even when you are
+using Masquerading or SNAT.
+ - I have cluttered up the /etc/shorewall directory
+ with empty 'init', 'start', 'stop' and 'stopped' files. If you already
have a file with one of these names, don't worry -- the upgrade process
won't overwrite your file.
- - I have added a new RFC1918_LOG_LEVEL variable
-to shorewall.conf. This variable
- specifies the syslog level at which packets are logged as a result
-of entries in the /etc/shorewall/rfc1918 file. Previously, these packets
- were always logged at the 'info' level.
-
+ - I have added a new RFC1918_LOG_LEVEL variable
+ to shorewall.conf. This
+variable specifies the syslog level at which packets are logged as
+a result of entries in the /etc/shorewall/rfc1918 file. Previously,
+these packets were always logged at the 'info' level.
+
-
+
-
+
12/20/2002 - Shorewall 1.3.12 Beta 3
-
- This version corrects a problem with Blacklist logging. In
- Beta 2, if BLACKLIST_LOG_LEVEL was set to anything but ULOG, the firewall
- would fail to start and "shorewall refresh" would also fail.
+
+ This version corrects a problem with Blacklist logging.
+In Beta 2, if BLACKLIST_LOG_LEVEL was set to anything but ULOG, the
+firewall would fail to start and "shorewall refresh" would also fail.
-
+
You may download the Beta from:
-
+
-
+
http://www.shorewall.net/pub/shorewall/Beta
- ftp://ftp.shorewall.net/pub/shorewall/Beta
-
-
-
-
- 12/20/2002 - Shorewall 1.3.12 Beta 2
-
- The first public Beta version of Shorewall 1.3.12 is
-now available (Beta 1 was made available to a limited audience).
-
-
- Features include:
-
-
-
-
-
- - "shorewall refresh" now reloads the traffic
- shaping rules (tcrules and tcstart).
- - "shorewall debug [re]start" now turns off
-debugging after an error occurs. This places the point of the failure
-near the end of the trace rather than up in the middle of it.
- - "shorewall [re]start" has been speeded up
-by more than 40% with my configuration. Your milage may vary.
- - A "shorewall show classifiers" command has
- been added which shows the current packet classification filters.
- The output from this command is also added as a separate page in
-"shorewall monitor"
- - ULOG (must be all caps) is now accepted as
- a valid syslog level and causes the subject packets to be logged
-using the ULOG target rather than the LOG target. This allows you to
-run ulogd (available from http://www.gnumonks.org/projects/ulogd)
- and log all Shorewall messages to a separate log file.
- - If you are running a kernel that has a FORWARD
- chain in the mangle table ("shorewall show mangle" will show you
-the chains in the mangle table), you can set MARK_IN_FORWARD_CHAIN=Yes
- in shorewall.conf. This allows for marking input packets based on
-their destination even when you are using Masquerading or SNAT.
- - I have cluttered up the /etc/shorewall directory
- with empty 'init', 'start', 'stop' and 'stopped' files. If you already
- have a file with one of these names, don't worry -- the upgrade process
- won't overwrite your file.
-
-
-
-
- You may download the Beta from:
-
-
-
- http://www.shorewall.net/pub/shorewall/Beta
- ftp://ftp.shorewall.net/pub/shorewall/Beta
-
-
-
-
- 12/12/2002 - Mandrake Multi Network Firewall 
-
- Shorewall is at the center of MandrakeSoft's recently-announced
- Multi
- Network Firewall (MNF) product. Here is the press
- release.
+
+ 12/20/2002 - Shorewall 1.3.12 Beta 2
+
+ The first public Beta version of Shorewall 1.3.12 is
+ now available (Beta 1 was made available to a limited audience).
+
+
+ Features include:
+
+
+
+
+
+ - "shorewall refresh" now reloads the traffic
+ shaping rules (tcrules and tcstart).
+ - "shorewall debug [re]start" now turns off
+ debugging after an error occurs. This places the point of the failure
+ near the end of the trace rather than up in the middle of it.
+ - "shorewall [re]start" has been speeded
+up by more than 40% with my configuration. Your milage may vary.
+ - A "shorewall show classifiers" command
+has been added which shows the current packet classification filters.
+ The output from this command is also added as a separate page in
+ "shorewall monitor"
+ - ULOG (must be all caps) is now accepted
+as a valid syslog level and causes the subject packets to be logged
+ using the ULOG target rather than the LOG target. This allows you to
+ run ulogd (available from http://www.gnumonks.org/projects/ulogd)
+ and log all Shorewall messages to a separate log file.
+ - If you are running a kernel that has a
+FORWARD chain in the mangle table ("shorewall show mangle" will
+show you the chains in the mangle table), you can set MARK_IN_FORWARD_CHAIN=Yes
+ in shorewall.conf. This allows for marking input packets based on
+ their destination even when you are using Masquerading or SNAT.
+ - I have cluttered up the /etc/shorewall
+directory with empty 'init', 'start', 'stop' and 'stopped' files.
+If you already have a file with one of these names, don't worry
+-- the upgrade process won't overwrite your file.
+
+
+
+
+ You may download the Beta from:
+
+
+
+ http://www.shorewall.net/pub/shorewall/Beta
+ ftp://ftp.shorewall.net/pub/shorewall/Beta
+
+
+
+
+ 12/12/2002 - Mandrake Multi Network Firewall
+
+ Shorewall is at the center of MandrakeSoft's recently-announced
+ Multi
+ Network Firewall (MNF) product. Here is the press
+ release.
+
+
+
12/7/2002 - Shorewall Support for Mandrake 9.0
-
+
Two months and 3 days after I pre-ordered Mandrake 9.0, it was finally
- delivered. I have installed 9.0 on one of my systems and I am
-now in a position to support Shorewall users who run Mandrake 9.0.
+ delivered. I have installed 9.0 on one of my systems and I am
+ now in a position to support Shorewall users who run Mandrake 9.0.
-
+
12/6/2002 - Debian 1.3.11a Packages Available
-
+
-
+
Apt-get sources listed at http://security.dsi.unimi.it/~lorenzo/debian.html.
-
+
12/3/2002 - Shorewall 1.3.11a
-
+
+
This is a bug-fix roll up which includes Roger Aich's fix for DNAT
- with excluded subnets (e.g., "DNAT foo!bar ..."). Current 1.3.11
- users who don't need rules of this type need not upgrade to 1.3.11.
+ with excluded subnets (e.g., "DNAT foo!bar ..."). Current 1.3.11
+ users who don't need rules of this type need not upgrade to 1.3.11.
-
+
+
11/25/2002 - Shorewall 1.3.11 Documentation in PDF Format
-
+
-
+
Juraj Ontkanin has produced a PDF containing the Shorewall 1.3.11
- documenation. the PDF may be downloaded from
+ documenation. the PDF may be downloaded from
-
+
ftp://slovakia.shorewall.net/mirror/shorewall/pdf/
- http://slovakia.shorewall.net/pub/shorewall/pdf/
-
+
-
+
11/24/2002 - Shorewall 1.3.11
-
+
In this version:
-
+
- - A 'tcpflags' option has been added
- to entries in /etc/shorewall/interfaces.
- This option causes Shorewall to make a set of sanity check on TCP
- packet header flags.
- - It is now allowed to use 'all'
-in the SOURCE or DEST column in a A 'tcpflags' option has been
+added to entries in /etc/shorewall/interfaces.
+ This option causes Shorewall to make a set of sanity check on TCP
+packet header flags.
+ - It is now allowed to use 'all'
+ in the SOURCE or DEST column in a rule. When used, 'all' must appear
by itself (in may not be qualified) and it does not enable intra-zone
traffic. For example, the rule
-
- ACCEPT loc all tcp 80
-
- does not enable http traffic from 'loc' to
-'loc'.
- - Shorewall's use of the 'echo' command
- is now compatible with bash clones such as ash and dash.
- - fw->fw policies now generate
-a startup error. fw->fw rules generate a warning and are
-ignored
+
+ ACCEPT loc all tcp 80
+
+ does not enable http traffic from 'loc'
+to 'loc'.
+ - Shorewall's use of the 'echo'
+command is now compatible with bash clones such as ash and dash.
+ - fw->fw policies now generate
+ a startup error. fw->fw rules generate a warning and are
+ ignored
-
+
-
+
More News
@@ -669,40 +679,41 @@ ignored
-
+
+
Donations
- |
+
- M |
-
+
-
+
- 
-
+
- 
- 
- 
-
-