run_iptables -I rfc1918 -s 192.168.100.1 -j ACCEPT-
If you are running version 1.3.1 or later, simply add the - following to /etc/shorewall/rfc1918:
-- ++- -
+- -SUBNET -TARGET -- + +192.168.100.1 -RETURN -+ +SUBNET +TARGET ++ + + + + +192.168.100.1 +RETURN +
Be sure that you add the entry ABOVE the entry for 192.168.0.0/16.
+
Note: If you add a second IP address to your external firewall
+ interface to correspond to the modem address, you must also
+ make an entry in /etc/shorewall/rfc1918 for that address. For
+ example, if you configure the address 192.168.100.2 on your firewall,
+ then you would add two entries to /etc/shorewall/rfc1918:
+
+ +-+ +
-+ +SUBNET +
+TARGET +
++ +192.168.100.1 +
+RETURN +
++ + + +192.168.100.2 +
+RETURN +
+
Be sure that you add the entry ABOVE the entry for 192.168.0.0/16.
-
Note: If you add a second IP address to your external firewall
- interface to correspond to the modem address, you must also
- make an entry in /etc/shorewall/rfc1918 for that address. For
- example, if you configure the address 192.168.100.2 on your firewall,
- then you would add two entries to /etc/shorewall/rfc1918:
-
- --- -
-- -SUBNET -
-TARGET -
-- -192.168.100.1 -
-RETURN -
-- + + - - - - -192.168.100.2 -
-RETURN -
-
14a. Even though it assigns public IP addresses, my ISP's DHCP server has an RFC 1918 address. If I enable RFC 1918 filtering on my external interface, my DHCP client cannot renew its lease.
-The solution is the same as FAQ 14 above. Simply substitute - the IP address of your ISPs DHCP server.
-15. My local systems can't see out to - the net
+ the net +Answer: Every time I read "systems can't see out to - the net", I wonder where the poster bought computers with - eyes and what those computers will "see" when things are working - properly. That aside, the most common causes of this problem - are:
+ the net", I wonder where the poster bought computers with + eyes and what those computers will "see" when things are working + properly. That aside, the most common causes of this problem + are: +-
-
- +
-
-
+
+
The default gateway on each local system isn't set to - the IP address of the local firewall interface.
-
- - + the IP address of the local firewall interface. + +
-
-
+
+
The entry for the local network in the /etc/shorewall/masq - file is wrong or missing.
-
- - + file is wrong or missing. + +
-
-
+
+
The DNS settings on the local systems are wrong or the - user is running a DNS server on the firewall and hasn't - enabled UDP and TCP port 53 from the firewall to the internet.
-
-
-
16. Shorewall is writing log messages - all over my console making it unusable!
+ user is running a DNS server on the firewall and hasn't + enabled UDP and TCP port 53 from the firewall to the internet. + - + + + + +16. Shorewall is writing log messages + all over my console making it unusable!
+ +Answer: "man dmesg" -- add a suitable 'dmesg' command
- to your startup scripts or place it in /etc/shorewall/start.
- Under RedHat, the max log level that is sent to the console
- is specified in /etc/sysconfig/init in the LOGLEVEL variable.
-
+ +
17. How do I find out why this traffic is getting - logged?
- Answer: Logging occurs out of a number - of chains (as indicated in the log message) in Shorewall:- + logged? + Answer: Logging occurs out of a number + of chains (as indicated in the log message) in Shorewall:
+
-
-
- man1918 - The destination address - is listed in /etc/shorewall/rfc1918 with a logdrop target - -- see /etc/shorewall/rfc1918. -
- rfc1918 - The source address -is listed in /etc/shorewall/rfc1918 with a logdrop target - -- see /etc/shorewall/rfc1918. -
- all2<zone>, <zone>2all - or all2all - You have aman1918 - The destination address + is listed in /etc/shorewall/rfc1918 with a logdrop target + -- see /etc/shorewall/rfc1918. +
- rfc1918 - The source address + is listed in /etc/shorewall/rfc1918 with a logdrop target + -- see /etc/shorewall/rfc1918. +
- all2<zone>, <zone>2all
+ or all2all - You have a policy that specifies a log level
- and this packet is being logged under that policy. If you intend
- to ACCEPT this traffic then you need a rule to that effect.
-
- - <zone1>2<zone2> - -Either you have a policy for - <zone1> to <zone2> that specifies -a log level and this packet is being logged under that policy -or this packet matches a rule -that includes a log level. -
- <interface>_mac - The packet is
- being logged under the maclist
+
- <zone1>2<zone2> - + Either you have a policy for + <zone1> to <zone2> that specifies + a log level and this packet is being logged under that policy + or this packet matches a rule + that includes a log level.
+- <interface>_mac - The packet +is being logged under the maclist interface option.
-
-- logpkt - The packet is being -logged under the logunclean +
+- logpkt - The packet is being + logged under the logunclean interface option.
-- badpkt - The packet is being -logged under the dropunclean badpkt - The packet is being + logged under the dropunclean interface option as specified in the LOGUNCLEAN setting in /etc/shorewall/shorewall.conf.
-- blacklst - The packet is being - logged because the source IP is blacklisted in theblacklst - The packet is being + logged because the source IP is blacklisted in the /etc/shorewall/blacklist file.
-- newnotsyn - The packet is being - logged because it is a TCP packet that is not part of any current - connection yet it is not a syn packet. Options affecting the logging - of such packets include NEWNOTSYN and LOGNEWNOTSYN - in /etc/shorewall/shorewall.conf.
-- INPUT or FORWARD - The -packet has a source IP address that isn't in any of your defined -zones ("shorewall check" and look at the printed zone definitions) -or the chain is FORWARD and the destination IP isn't in any of your -defined zones.
-- logflags - The packet is being logged because - it failed the checks implemented by the tcpflags newnotsyn - The packet is being + logged because it is a TCP packet that is not part of any current + connection yet it is not a syn packet. Options affecting the logging + of such packets include NEWNOTSYN and LOGNEWNOTSYN + in /etc/shorewall/shorewall.conf.
+- INPUT or FORWARD - The + packet has a source IP address that isn't in any of your defined + zones ("shorewall check" and look at the printed zone definitions) + or the chain is FORWARD and the destination IP isn't in any of your + defined zones.
+- logflags - The packet is being logged +because it failed the checks implemented by the tcpflags interface option.
- +
-
18. Is there any way to use aliased ip addresses - with Shorewall, and maintain separate rulesets for different -IPs?
- Answer: Yes. You simply use the IP address - in your rules (or if you use NAT, use the local IP address in -your rules). Note: The ":n" notation (e.g., eth0:0) is deprecated - and will disappear eventually. Neither iproute (ip and tc) nor - iptables supports that notation so neither does Shorewall.-
- Example 1:
-
- /etc/shorewall/rules - + with Shorewall, and maintain separate rulesets for different + IPs? + Answer: Yes. You simply use the IP address + in your rules (or if you use NAT, use the local IP address in + your rules). Note: The ":n" notation (e.g., eth0:0) is deprecated + and will disappear eventually. Neither iproute (ip and tc) nor + iptables supports that notation so neither does Shorewall.
+
+ Example 1:
+
+ /etc/shorewall/rules +
# Accept AUTH but only on address 192.0.2.125- Example - 2 (NAT):
ACCEPT net fw:192.0.2.125 tcp auth
-
- /etc/shorewall/nat
- + Example + 2 (NAT):
+
+ /etc/shorewall/nat
+
192.0.2.126 eth0 10.1.1.126- /etc/shorewall/rules - + /etc/shorewall/rules +
# Accept HTTP on 192.0.2.126 (a.k.a. 10.1.1.126)- Example 3 (DNAT):
ACCEPT net loc:10.1.1.126 tcp www
- + Example 3 (DNAT):
+
# Forward SMTP on external address 192.0.2.127 to local system 10.1.1.127- +
DNAT net loc:10.1.1.127 tcp smtp - 192.0.2.127
19. I have added entries to /etc/shorewall/tcrules - but they don't seem to do anything. Why?
- You probably haven't set TC_ENABLED=Yes in /etc/shorewall/shorewall.conf - so the contents of the tcrules file are simply being ignored.- + but they don't seem to do anything. Why? + You probably haven't set TC_ENABLED=Yes in /etc/shorewall/shorewall.conf + so the contents of the tcrules file are simply being ignored.
+
20. I have just set up a server. Do I have
- to change Shorewall to allow access to my server from the internet?
-
- Yes. Consult the + + Yes. Consult the QuickStart guide that you used during your initial setup for information about how to set up rules for your server.
- +
21. I see these strange log entries occasionally;
- what are they?
-
-
+ what are they?+ +
+- 192.0.2.3 is external on my firewall... 172.16.0.0/24 -is my internal LANNov 25 18:58:52 linux kernel: Shorewall:net2all:DROP:IN=eth1 OUT= MAC=00:60:1d:f0:a6:f9:00:60:1d:f6:35:50:08:00-
SRC=206.124.146.179 DST=192.0.2.3 LEN=56 TOS=0x00 PREC=0x00 TTL=110 ID=18558 PROTO=ICMP TYPE=3 CODE=3
[SRC=192.0.2.3 DST=172.16.1.10 LEN=128 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=UDP SPT=53 DPT=2857 LEN=108 ]
-
- Answer: While most people associate the Internet - Control Message Protocol (ICMP) with 'ping', ICMP is a key piece -of the internet. ICMP is used to report problems back to the sender -of a packet; this is what is happening here. Unfortunately, where NAT -is involved (including SNAT, DNAT and Masquerade), there are a lot of -broken implementations. That is what you are seeing with these messages.
-
- Here is my interpretation of what is happening -- to confirm - this analysis, one would have to have packet sniffers placed a both - ends of the connection.
-
- Host 172.16.1.10 behind NAT gateway 206.124.146.179 sent - a UDP DNS query to 192.0.2.3 and your DNS server tried to send a -response (the response information is in the brackets -- note source -port 53 which marks this as a DNS reply). When the response was returned -to to 206.124.146.179, it rewrote the destination IP TO 172.16.1.10 and -forwarded the packet to 172.16.1.10 who no longer had a connection on -UDP port 2857. This causes a port unreachable (type 3, code 3) to be -generated back to 192.0.2.3. As this packet is sent back through 206.124.146.179, - that box correctly changes the source address in the packet to 206.124.146.179 - but doesn't reset the DST IP in the original DNS response similarly. - When the ICMP reaches your firewall (192.0.2.3), your firewall has no - record of having sent a DNS reply to 172.16.1.10 so this ICMP doesn't - appear to be related to anything that was sent. The final result is -that the packet gets logged and dropped in the all2all chain. I have also -seen cases where the source IP in the ICMP itself isn't set back to the -external IP of the remote NAT gateway; that causes your firewall to log -and drop the packet out of the rfc1918 chain because the source IP is reserved -by RFC 1918.
- + + 192.0.2.3 is external on my firewall... 172.16.0.0/24 + is my internal LAN
+
+ Answer: While most people associate the Internet + Control Message Protocol (ICMP) with 'ping', ICMP is a key piece + of the internet. ICMP is used to report problems back to the sender + of a packet; this is what is happening here. Unfortunately, where NAT + is involved (including SNAT, DNAT and Masquerade), there are a lot +of broken implementations. That is what you are seeing with these messages.
+
+ Here is my interpretation of what is happening -- to +confirm this analysis, one would have to have packet sniffers placed +a both ends of the connection.
+
+ Host 172.16.1.10 behind NAT gateway 206.124.146.179 +sent a UDP DNS query to 192.0.2.3 and your DNS server tried to +send a response (the response information is in the brackets -- note +source port 53 which marks this as a DNS reply). When the response was +returned to to 206.124.146.179, it rewrote the destination IP TO 172.16.1.10 +and forwarded the packet to 172.16.1.10 who no longer had a connection +on UDP port 2857. This causes a port unreachable (type 3, code 3) to +be generated back to 192.0.2.3. As this packet is sent back through 206.124.146.179, + that box correctly changes the source address in the packet to 206.124.146.179 + but doesn't reset the DST IP in the original DNS response similarly. + When the ICMP reaches your firewall (192.0.2.3), your firewall has +no record of having sent a DNS reply to 172.16.1.10 so this ICMP doesn't + appear to be related to anything that was sent. The final result is + that the packet gets logged and dropped in the all2all chain. I have also + seen cases where the source IP in the ICMP itself isn't set back to the + external IP of the remote NAT gateway; that causes your firewall to log + and drop the packet out of the rfc1918 chain because the source IP is + reserved by RFC 1918.
+
22. I have some iptables commands that - I want to run when Shorewall starts. Which file do I put them - in?
- You can place these commands in one of the run when Shorewall starts. Which file do I put them + in? + You can place these commands in one of the Shorewall Extension Scripts. Be sure that you look at the contents of the chain(s) that you will be modifying - with your commands to be sure that the commands will do what they are - intended. Many iptables commands published in HOWTOs and other instructional - material use the -A command which adds the rules to the end of the chain. - Most chains that Shorewall constructs end with an unconditional DROP, - ACCEPT or REJECT rule and any rules that you add after that will be ignored. - Check "man iptables" and look at the -I (--insert) command.- + with your commands to be sure that the commands will do what they +are intended. Many iptables commands published in HOWTOs and other +instructional material use the -A command which adds the rules to the +end of the chain. Most chains that Shorewall constructs end with an +unconditional DROP, ACCEPT or REJECT rule and any rules that you add +after that will be ignored. Check "man iptables" and look at the -I (--insert) +command.
+
23. Why do you use such ugly fonts on your - web site?
- The Shorewall web site is almost font neutral (it doesn't explicitly - specify fonts except on a few pages) so the fonts you see are largely -the default fonts configured in your browser. If you don't like them then -reconfigure your browser.- + web site? + The Shorewall web site is almost font neutral (it doesn't explicitly + specify fonts except on a few pages) so the fonts you see are largely + the default fonts configured in your browser. If you don't like them +then reconfigure your browser.
+
24. How can I allow conections to let's say - the ssh port only from specific IP Addresses on the internet?
- In the SOURCE column of the rule, follow "net" by a colon and a list - of the host/subnet addresses as a comma-separated list.- + the ssh port only from specific IP Addresses on the internet? + In the SOURCE column of the rule, follow "net" by a colon and a +list of the host/subnet addresses as a comma-separated list.
+
net:<ip1>,<ip2>,...- Example:
- + Example:
+
ACCEPT net:192.0.2.16/28,192.0.2.44 fw tcp 22+ - +
Copyright
© 2001, 2002, 2003 Thomas M. Eastep.
-
-
-
-
-
-
+ diff --git a/Shorewall-docs/News.htm b/Shorewall-docs/News.htm index ff1db5fdb..e27dd03e3 100644 --- a/Shorewall-docs/News.htm +++ b/Shorewall-docs/News.htm @@ -3,2047 +3,2158 @@ - +
| + |
-
+
Shorewall News Archive- |
-
2/4/2003 - Shorewall 1.3.14-RC1
-Includes the Beta 2 content plus support for OpenVPN tunnels.
-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)
- -1/25/2003 - Shorewall 1.3.14-Beta1
-
The Beta includes the following changes:
-
2/8/2003 - Shoreawll 1.3.14
+New features include
-
-
- An OLD_PING_HANDLING option has been added to shorewall.conf. When +
- 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.
-
- +
+ 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
+
+ - Support for OpenVPN Tunnels.
+
+
+ - Support for VLAN devices with names of the form $DEV.$VID (e.g., eth0.0)
+
+
+ - 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 /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:
-
- +
+ 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:
+
+[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
-
+
+2/5/2003 - Shorewall Support included in Webmin 1.060
Webmin version 1.060 now has Shorewall support included as standard. See
+http://www.webmin.com.
+
+ 2/4/2003 - Shorewall 1.3.14-RC1
Includes the Beta 2 content plus support for OpenVPN tunnels.
+ +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)
+ +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.
+
+ +[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 /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:
+
+ +[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?
+
+ +[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:
+ +#INTERFACE SUBNET ADDRESS
+
eth0 192.168.1.0/24 206.124.146.176
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE
+
+
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.
-
-
-
1/6/2003 - BURNOUT -
- -Until further notice, I will not be involved in either Shorewall Development - or Shorewall Support
- --Tom Eastep
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.
+
+
+
1/6/2003 - BURNOUT +
+ +Until further notice, I will not be involved in either Shorewall 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
- + 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 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 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. -
- I have added a new RFC1918_LOG_LEVEL variable to
+
- 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 + 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.
- + logged at the 'info' level.
-
+
+
12/20/2002 - Shorewall 1.3.12 Beta 3
-
- +
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 only to a limited audience).
-
- + 1 was made available only 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 +
- "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 +
- 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 
-
- + release.
+
12/7/2002 - Shorewall Support for Mandrake 9.0
- +Two months and 3 days after I 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.
- + 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.
- + 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/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 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 - +
- 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 +
11/14/2002 - Shorewall Documentation in PDF Format
- +Juraj Ontkanin has produced a PDF containing the Shorewall 1.3.10 documenation. - the PDF may be downloaded from
- + the PDF may be downloaded from + ftp://slovakia.shorewall.net/mirror/shorewall/pdf/
- http://slovakia.shorewall.net/pub/shorewall/pdf/
-
11/09/2002 - Shorewall is Back at SourceForge
- +The main Shorewall 1.3 web site is now back at SourceForge at http://shorewall.sf.net.
-
11/09/2002 - Shorewall 1.3.10
- +In this version:
- +-
-
- You may now define - the contents of a zone dynamically with the You may now define + the contents of a zone dynamically with the "shorewall add" and "shorewall - delete" commands. These commands are expected to be used - primarily within . These commands are expected to be used + primarily within FreeS/Wan updown scripts. -
- Shorewall can now doShorewall can now do MAC verification on ethernet segments. You can specify the set of allowed MAC addresses on the segment and you can optionally tie each MAC address to one or more IP addresses. -
- PPTP Servers and Clients running on the firewall - system may now be defined in the /etc/shorewall/tunnels - file. -
- A new 'ipsecnat' tunnel type is supported -for use when the remote IPSEC endpoint -is behind a NAT gateway. -
- The PATH used by Shorewall may now be specified - in /etc/shorewall/shorewall.conf. -
- The main firewall script is now /usr/lib/shorewall/firewall. - The script in /etc/init.d/shorewall is very small and uses /sbin/shorewall +
- PPTP Servers and Clients running on the +firewall system may now be defined in the +/etc/shorewall/tunnels file. +
- A new 'ipsecnat' tunnel type is supported + for use when the remote IPSEC endpoint + is behind a NAT gateway. +
- The PATH used by Shorewall may now be specified + in /etc/shorewall/shorewall.conf. +
- The main firewall script is now /usr/lib/shorewall/firewall. + The script in /etc/init.d/shorewall is very small and uses /sbin/shorewall to do the real work. This change makes custom distributions such as for Debian and for Gentoo easier to manage since it is /etc/init.d/shorewall that tends to have distribution-dependent code - +
10/24/2002 - Shorewall is now in Gentoo Linux
-
- + + Alexandru Hartmann reports that his Shorewall + package is now a part of the +Gentoo Linux distribution. Thanks Alex!
+
10/23/2002 - Shorewall 1.3.10 Beta 1
- In this version:+ In this version:
- +
-
-
- You may now define - the contents of a zone dynamically with the "shorewall add" and "shorewall - delete" commands. These commands are expected to be used -primarily within You may now define the contents of a zone dynamically +with the "shorewall add" and +"shorewall delete" commands. These commands are expected +to be used primarily within FreeS/Wan updown scripts. -
- Shorewall can now doShorewall can now do MAC verification on ethernet segments. - You can specify the set of allowed MAC addresses on the segment - and you can optionally tie each MAC address to one or more IP addresses. -
- PPTP Servers and Clients running on the firewall - system may now be defined in the /etc/shorewall/tunnels - file. -
- A new 'ipsecnat' tunnel type is supported -for use when the remote IPSEC endpoint -is behind a NAT gateway. -
- The PATH used by Shorewall may now be specified - in /etc/shorewall/shorewall.conf. -
- The main firewall script is now /usr/lib/shorewall/firewall. - The script in /etc/init.d/shorewall is very small and uses /sbin/shorewall - to do the real work. This change makes custom distributions such - as for Debian and for Gentoo easier to manage since it is /etc/init.d/shorewall - that tends to have distribution-dependent code. - + You can specify the set of allowed MAC addresses on the segment + and you can optionally tie each MAC address to one or more IP addresses. +
- PPTP Servers and Clients running on the +firewall system may now be defined in the +/etc/shorewall/tunnels file. +
- A new 'ipsecnat' tunnel type is supported + for use when the remote IPSEC endpoint + is behind a NAT gateway. +
- The PATH used by Shorewall may now be specified + in /etc/shorewall/shorewall.conf. +
- The main firewall script is now /usr/lib/shorewall/firewall. + The script in /etc/init.d/shorewall is very small and uses +/sbin/shorewall to do the real work. This change makes custom +distributions such as for Debian and for Gentoo easier to manage +since it is /etc/init.d/shorewall that tends to have distribution-dependent +code. +
- + You may download the Beta from:
+ - +
10/10/2002 - Debian 1.3.9b Packages Available
-
Apt-get sources listed at http://security.dsi.unimi.it/~lorenzo/debian.html.
- +10/9/2002 - Shorewall 1.3.9b
- This release rolls up fixes to the installer -and to the firewall script.- -
10/6/2002 - Shorewall.net now running on RH8.0
-
- The firewall and server here at shorewall.net
- are now running RedHat release 8.0.
-
- 9/30/2002 - Shorewall 1.3.9a
+ This release rolls up fixes to the installer + and to the firewall script.
+
10/6/2002 - Shorewall.net now running on RH8.0
+
+ The firewall and server here at shorewall.net
+ are now running RedHat release 8.0.
+
+ 9/30/2002 - Shorewall 1.3.9a
+
9/30/2002 - TUNNELS Broken in 1.3.9!!!
- There is an updated firewall script at ftp://www.shorewall.net/pub/shorewall/errata/1.3.9/firewall - -- copy that file to /usr/lib/shorewall/firewall.- + -- copy that file to /usr/lib/shorewall/firewall.
+
9/28/2002 - Shorewall 1.3.9
- +In this version:
-
-
-
- DNS Names are now allowed in Shorewall config files (although I recommend against using them). -
- The connection SOURCE may now be -qualified by both interface and IP address in a The connection SOURCE may now +be qualified by both interface and IP address in a Shorewall rule. -
- Shorewall startup is now disabled - after initial installation until the file /etc/shorewall/startup_disabled - is removed. This avoids nasty surprises during reboot for users - who install Shorewall but don't configure it. -
- The 'functions' and 'version' files
-and the 'firewall' symbolic link have been moved from /var/lib/shorewall
- to /usr/lib/shorewall to appease the LFS police at Debian.
-
-
-
9/23/2002 - Full Shorewall Site/Mailing List Archive Search Capability
- Restored
-
- A couple of recent configuration changes
- at www.shorewall.net broke the Search facility:- - -
- -- Hopefully these problems are now corrected. - --
-- Mailing List Archive Search was - not available.
-- The Site Search index was incomplete
-- Only one page of matches was presented.
- - -
9/23/2002 - Full Shorewall Site/Mailing List Archive Search Capability
- Restored
-
- -
-
-
- Mailing List Archive Search was -not available. -
- The Site Search index was incomplete -
- Only one page of matches was presented. - -
- -
9/18/2002 - Debian 1.3.8 Packages Available
-
+
9/23/2002 - Full Shorewall Site/Mailing List Archive Search Capability
+ Restored
+
+ A couple of recent configuration
+changes at www.shorewall.net broke the Search facility:+ + +
+ ++ Hopefully these problems are now +corrected. ++
+- Mailing List Archive Search +was not available.
+- The Site Search index was incomplete
+- Only one page of matches was +presented.
+ + + +
9/23/2002 - Full Shorewall Site/Mailing List Archive Search Capability
+ Restored
+
+ + +
-
+
- Mailing List Archive Search was + not available. +
- The Site Search index was incomplete +
- Only one page of matches was +presented. + + +
+ + +
9/18/2002 - Debian 1.3.8 Packages Available
+
Apt-get sources listed at http://security.dsi.unimi.it/~lorenzo/debian.html.
- + +9/16/2002 - Shorewall 1.3.8
- +In this version:
-
-
-
- A A NEWNOTSYN option has been added to shorewall.conf. This option determines whether Shorewall - accepts TCP packets which are not part of an established -connection and that are not 'SYN' packets (SYN flag on and ACK + accepts TCP packets which are not part of an established + connection and that are not 'SYN' packets (SYN flag on and ACK flag off). -
- The need for the 'multi' option - to communicate between zones za and zb on the same interface - is removed in the case where the chain 'za2zb' and/or 'zb2za' - exists. 'za2zb' will exist if: +
- The need for the 'multi' option + to communicate between zones za and zb on the same interface + is removed in the case where the chain 'za2zb' and/or 'zb2za' + exists. 'za2zb' will exist if: - +
- There is a policy for - za to zb; or -
- There is at least one rule - for za to zb. +
- There is a policy +for za to zb; or +
- There is at least one +rule for za to zb. - +
-
-
-
-
- The /etc/shorewall/blacklist
-file now contains three columns. In addition to the SUBNET/ADDRESS
- column, there are optional PROTOCOL and PORT columns to block
- only certain applications from the blacklisted addresses.
-
+ - The /etc/shorewall/blacklist
+ file now contains three columns. In addition to the SUBNET/ADDRESS
+ column, there are optional PROTOCOL and PORT columns to
+block only certain applications from the blacklisted addresses.
+
-
+
9/11/2002 - Debian 1.3.7c Packages Available
- +Apt-get sources listed at http://security.dsi.unimi.it/~lorenzo/debian.html.
- +9/2/2002 - Shorewall 1.3.7c
- +This is a role up of a fix for "DNAT" rules where the source zone is $FW - (fw).
+ (fw). - +8/31/2002 - I'm not available
- +I'm currently on vacation -- please respect my need for a couple of weeks free of Shorewall problem reports.
- +-Tom
- +8/26/2002 - Shorewall 1.3.7b
- +This is a role up of the "shorewall refresh" bug fix and the change which - reverses the order of "dhcp" and "norfc1918" checking.
+ reverses the order of "dhcp" and "norfc1918" checking. - +8/26/2002 - French FTP Mirror is Operational
- +ftp://france.shorewall.net/pub/mirrors/shorewall - is now available.
+ is now available. - +8/25/2002 - Shorewall Mirror in France
- +Thanks to a Shorewall user in Paris, the Shorewall web site is now mirrored - at http://france.shorewall.net.
- +8/25/2002 - Shorewall 1.3.7a Debian Packages Available
- +Lorenzo Martignoni reports that the packages for version 1.3.7a are available - at http://security.dsi.unimi.it/~lorenzo/debian.html.
- +8/22/2002 - Shorewall 1.3.7 Wins a Brown Paper Bag Award for its Author
- -- Shorewall 1.3.7a released
-
1.3.7a corrects problems occurring in rules file processing when starting - Shorewall 1.3.7.
+ Shorewall 1.3.7. - +8/22/2002 - Shorewall 1.3.7 Released 8/13/2002
- +Features in this release include:
- +-
-
- The 'icmp.def' file is now -empty! The rules in that file were required in ipchains -firewalls but are not required in Shorewall. Users who have - ALLOWRELATED=No in shorewall.conf - should see the Upgrade Issues. -
- A 'FORWARDPING' option has -been added to shorewall.conf. - The effect of setting this variable to Yes is the same -as the effect of adding an ACCEPT rule for ICMP echo-request - in /etc/shorewall/icmpdef. - Users who have such a rule in icmpdef are encouraged - to switch to FORWARDPING=Yes. -
- The loopback CLASS A Network - (127.0.0.0/8) has been added to the rfc1918 file. -
- Shorewall now works with iptables - 1.2.7 -
- The documentation and web -site no longer uses FrontPage themes. +
- The 'icmp.def' file is now + empty! The rules in that file were required in ipchains + firewalls but are not required in Shorewall. Users who have + ALLOWRELATED=No in shorewall.conf + should see the Upgrade Issues. +
- A 'FORWARDPING' option has + been added to shorewall.conf. + The effect of setting this variable to Yes is the same + as the effect of adding an ACCEPT rule for ICMP echo-request + in /etc/shorewall/icmpdef. + Users who have such a rule in icmpdef are encouraged + to switch to FORWARDPING=Yes. +
- The loopback CLASS A Network + (127.0.0.0/8) has been added to the rfc1918 file. +
- Shorewall now works with +iptables 1.2.7 +
- The documentation and web + site no longer uses FrontPage themes. - +
I would like to thank John Distler for his valuable input regarding TCP - SYN and ICMP treatment in Shorewall. That input has led - to marked improvement in Shorewall in the last two releases.
+ SYN and ICMP treatment in Shorewall. That input has +led to marked improvement in Shorewall in the last two releases. - +8/13/2002 - Documentation in the CVS Repository
- +The Shorewall-docs project now contains just the HTML and image files - the Frontpage files have been removed.
- +8/7/2002 - STABLE branch added to CVS Repository
- +This branch will only be updated after I release a new version of Shorewall - so you can always update from this branch to get the -latest stable tree.
+ so you can always update from this branch to get the + latest stable tree. - +8/7/2002 - Upgrade Issues section added to the Errata Page
- +Now there is one place to go to look for issues involved with upgrading - to recent versions of Shorewall.
+ to recent versions of Shorewall. - +8/7/2002 - Shorewall 1.3.6
- +This is primarily a bug-fix rollup with a couple of new features:
- +-
-
- The latest The latest QuickStart Guides including the Shorewall Setup Guide. -
- Shorewall will now DROP TCP - packets that are not part of or related to an existing -connection and that are not SYN packets. These "New not -SYN" packets may be optionally logged by setting the LOGNEWNOTSYN - option in /etc/shorewall/shorewall.conf. -
- The processing of "New not -SYN" packets may be extended by commands in the new - newnotsyn extension script. +
- Shorewall will now DROP +TCP packets that are not part of or related to an existing + connection and that are not SYN packets. These "New not + SYN" packets may be optionally logged by setting the LOGNEWNOTSYN + option in /etc/shorewall/shorewall.conf. +
- The processing of "New not + SYN" packets may be extended by commands in the new + newnotsyn extension script. - +
7/30/2002 - Shorewall 1.3.5b Released
- +This interim release:
- +-
-
- Causes the firewall script -to remove the lock file if it is killed. -
- Once again allows lists in -the second column of the Causes the firewall script + to remove the lock file if it is killed. +
- Once again allows lists +in the second column of the /etc/shorewall/hosts file. -
- Includes the latest Includes the latest QuickStart Guides. - +
7/29/2002 - New Shorewall Setup Guide Available
- +The first draft of this guide is available at http://www.shorewall.net/shorewall_setup_guide.htm. - The guide is intended for use by people who are setting - up Shorewall to manage multiple public IP addresses and -by people who want to learn more about Shorewall than is described - in the single-address guides. Feedback on the new guide is welcome.
+ The guide is intended for use by people who are setting + up Shorewall to manage multiple public IP addresses and + by people who want to learn more about Shorewall than is described + in the single-address guides. Feedback on the new guide is +welcome. - +7/28/2002 - Shorewall 1.3.5 Debian Package Available
- +Lorenzo Martignoni reports that the packages are version 1.3.5a and are - available at http://security.dsi.unimi.it/~lorenzo/debian.html.
- +7/27/2002 - Shorewall 1.3.5a Released
- +This interim release restores correct handling of REDIRECT rules.
- +7/26/2002 - Shorewall 1.3.5 Released
- +This will be the last Shorewall release for a while. I'm going to be focusing on rewriting a lot of the documentation.
- +In this version:
- +-
-
- Empty and invalid source and - destination qualifiers are now detected in the rules - file. It is a good idea to use the 'shorewall check' command - before you issue a 'shorewall restart' command be be sure -that you don't have any configuration problems that will prevent - a successful restart. -
- Added MERGE_HOSTS variable - in shorewall.conf to provide - saner behavior of the /etc/shorewall/hosts file. -
- The time that the counters -were last reset is now displayed in the heading of the -'status' and 'show' commands. -
- A proxyarp option has - been added for entries in Empty and invalid source +and destination qualifiers are now detected in the +rules file. It is a good idea to use the 'shorewall check' command + before you issue a 'shorewall restart' command be be sure + that you don't have any configuration problems that will prevent + a successful restart. +
- Added MERGE_HOSTS +variable in shorewall.conf +to provide saner behavior of the /etc/shorewall/hosts + file. +
- The time that the counters + were last reset is now displayed in the heading of the + 'status' and 'show' commands. +
- A proxyarp option +has been added for entries in /etc/shorewall/interfaces. This option facilitates Proxy ARP sub-netting as described in the Proxy ARP subnetting mini-HOWTO (http://www.tldp.org/HOWTO/mini/Proxy-ARP-Subnet/). - Specifying the proxyarp option for an interface causes - Shorewall to set /proc/sys/net/ipv4/conf/<interface>/proxy_arp. -
- The Samples have been updated - to reflect the new capabilities in this release. + Specifying the proxyarp option for an interface causes + Shorewall to set /proc/sys/net/ipv4/conf/<interface>/proxy_arp. +
- The Samples have been updated + to reflect the new capabilities in this release. - +
7/16/2002 - New Mirror in Argentina
- +Thanks to Arturo "Buanzo" Busleiman, there is now a Shorewall mirror in - Argentina. Thanks Buanzo!!!
+ Argentina. Thanks Buanzo!!! - +7/16/2002 - Shorewall 1.3.4 Released
- +In this version:
- +-
-
- A new A new /etc/shorewall/routestopped - file has been added. This file is intended to eventually - replace the routestopped option in the /etc/shorewall/interface - and /etc/shorewall/hosts files. This new file makes remote - firewall administration easier by allowing any IP or subnet -to be enabled while Shorewall is stopped. -
- An /etc/shorewall/stopped - extension script has been -added. This script is invoked after Shorewall has -stopped. -
- A DETECT_DNAT_ADDRS option - has been added to /etc/shoreall/shorewall.conf. - When this option is selected, DNAT rules only apply - when the destination address is the external interface's - primary IP address. -
- The routestopped option in the /etc/shorewall/interface + and /etc/shorewall/hosts files. This new file makes +remote firewall administration easier by allowing any IP or +subnet to be enabled while Shorewall is stopped. +
- An /etc/shorewall/stopped + extension script has been + added. This script is invoked after Shorewall has + stopped. +
- A DETECT_DNAT_ADDRS option + has been added to /etc/shoreall/shorewall.conf. + When this option is selected, DNAT rules only apply + when the destination address is the external interface's + primary IP address. +
- The QuickStart Guide has - been broken into three guides and has been almost entirely - rewritten. -
- The Samples have been updated - to reflect the new capabilities in this release. + been broken into three guides and has been almost entirely + rewritten. +
- The Samples have been updated + to reflect the new capabilities in this release. - +
7/8/2002 - Shorewall 1.3.3 Debian Package Available
- +Lorenzo Marignoni reports that the packages are available at http://security.dsi.unimi.it/~lorenzo/debian.html.
- +7/6/2002 - Shorewall 1.3.3 Released
- +In this version:
- +-
-
- Entries in /etc/shorewall/interface - that use the wildcard character ("+") now have the +
- Entries in /etc/shorewall/interface + that use the wildcard character ("+") now have the "multi" option assumed. -
- The 'rfc1918' chain in the -mangle table has been renamed 'man1918' to make log -messages generated from that chain distinguishable from those - generated by the 'rfc1918' chain in the filter table. -
- Interface names appearing -in the hosts file are now validated against the interfaces - file. -
- The TARGET column in the rfc1918 - file is now checked for correctness. -
- The chain structure in the -nat table has been changed to reduce the number of rules -that a packet must traverse and to correct problems with - NAT_BEFORE_RULES=No -
- The "hits" command has been - enhanced. +
- The 'rfc1918' chain in the + mangle table has been renamed 'man1918' to make log + messages generated from that chain distinguishable from those + generated by the 'rfc1918' chain in the filter table. +
- Interface names appearing + in the hosts file are now validated against the interfaces + file. +
- The TARGET column in the +rfc1918 file is now checked for correctness. +
- The chain structure in the + nat table has been changed to reduce the number of rules + that a packet must traverse and to correct problems with + NAT_BEFORE_RULES=No +
- The "hits" command has been + enhanced. - +
6/25/2002 - Samples Updated for 1.3.2
- +The comments in the sample configuration files have been updated to reflect - new features introduced in Shorewall 1.3.2.
+ new features introduced in Shorewall 1.3.2. - +6/25/2002 - Shorewall 1.3.1 Debian Package Available
- +Lorenzo Marignoni reports that the package is available at http://security.dsi.unimi.it/~lorenzo/debian.html.
- +6/19/2002 - Documentation Available in PDF Format
- +Thanks to Mike Martinez, the Shorewall Documentation is now available for download in Adobe PDF format.
- +6/16/2002 - Shorewall 1.3.2 Released
- +In this version:
- +-
-
- A A logwatch command has been added to /sbin/shorewall. -
- A A dynamic blacklist facility has been added. -
- Support for the Support for the Netfilter multiport match function - has been added. -
- The files firewall, functions - and version have been moved from -/etc/shorewall to /var/lib/shorewall. + has been added. +
- The files firewall, functions + and version have been moved from + /etc/shorewall to /var/lib/shorewall. - +
6/6/2002 - Why CVS Web access is Password Protected
- +Last weekend, I installed the CVS Web package to provide brower-based access to the Shorewall CVS repository. Since then, I have had several instances where my server was almost unusable due to the high load generated by website copying tools like HTTrack and WebStripper. These mindless tools:
- +-
-
- Ignore robot.txt files. -
- Recursively copy everything - that they find. -
- Should be classified as weapons - rather than tools. +
- Ignore robot.txt files. +
- Recursively copy everything + that they find. +
- Should be classified as +weapons rather than tools. - +
These tools/weapons are particularly damaging when combined with CVS Web - because they doggedly follow every link in the cgi-generated - HTML resulting in 1000s of executions of the cvsweb.cgi - script. Yesterday, I spend several hours implementing measures - to block these tools but unfortunately, these measures resulted - in my server OOM-ing under even moderate load.
+ because they doggedly follow every link in the cgi-generated + HTML resulting in 1000s of executions of the cvsweb.cgi + script. Yesterday, I spend several hours implementing measures + to block these tools but unfortunately, these measures resulted + in my server OOM-ing under even moderate load. - +Until I have the time to understand the cause of the OOM (or until I buy - more RAM if that is what is required), CVS Web access - will remain Password Protected.
+ more RAM if that is what is required), CVS Web access + will remain Password Protected. - +6/5/2002 - Shorewall 1.3.1 Debian Package Available
- +Lorenzo Marignoni reports that the package is available at http://security.dsi.unimi.it/~lorenzo/debian.html.
- +6/2/2002 - Samples Corrected
- +The 1.3.0 samples configurations had several serious problems that prevented - DNS and SSH from working properly. These problems have - been corrected in the 1.3.1 samples.
- +6/1/2002 - Shorewall 1.3.1 Released
- +Hot on the heels of 1.3.0, this release:
- +-
-
- Corrects a serious problem -with "all <zone> CONTINUE" policies. - This problem is present in all versions of Shorewall that +
- Corrects a serious problem + with "all <zone> CONTINUE" policies. + This problem is present in all versions of Shorewall that support the CONTINUE policy. These previous versions optimized - away the "all2<zone>" chain and replaced it with -the "all2all" chain with the usual result that a policy of REJECT -was enforced rather than the intended CONTINUE policy. -
- Adds an <zone>" chain and replaced it with + the "all2all" chain with the usual result that a policy of REJECT + was enforced rather than the intended CONTINUE policy. +
- Adds an /etc/shorewall/rfc1918 file for defining the exact behavior of the 'norfc1918' interface option. - +
5/29/2002 - Shorewall 1.3.0 Released
- +In addition to the changes in Beta 1, Beta 2 and RC1, Shorewall 1.3.0 includes:
- +-
-
- A 'filterping' interface option - that allows ICMP echo-request (ping) requests addressed - to the firewall to be handled by entries in /etc/shorewall/rules - and /etc/shorewall/policy. +
- A 'filterping' interface +option that allows ICMP echo-request (ping) requests +addressed to the firewall to be handled by entries in /etc/shorewall/rules + and /etc/shorewall/policy. - +
5/23/2002 - Shorewall 1.3 RC1 Available
- +In addition to the changes in Beta 1 and Beta 2, RC1 (Version 1.2.92) incorporates the following:
- +-
-
- Support for the /etc/shorewall/whitelist - file has been withdrawn. If you need whitelisting, see - these instructions. +
- Support for the /etc/shorewall/whitelist + file has been withdrawn. If you need whitelisting, +see these instructions. - +
5/19/2002 - Shorewall 1.3 Beta 2 Available
- +In addition to the changes in Beta 1, this release which carries the designation 1.2.91 adds:
- +-
-
- The structure of the firewall - is changed markedly. There is now an INPUT and a FORWARD - chain for each interface; this reduces the number of rules -that a packet must traverse, especially in complicated setups. -
- The structure of the firewall + is changed markedly. There is now an INPUT and a FORWARD + chain for each interface; this reduces the number of rules + that a packet must traverse, especially in complicated setups. +
- Sub-zones may now be excluded - from DNAT and REDIRECT rules. -
- The names of the columns in - a number of the configuration files have been changed - to be more consistent and self-explanatory and the documentation - has been updated accordingly. -
- The sample configurations -have been updated for 1.3. + from DNAT and REDIRECT rules. +
- The names of the columns +in a number of the configuration files have been changed + to be more consistent and self-explanatory and the documentation + has been updated accordingly. +
- The sample configurations + have been updated for 1.3. - +
5/17/2002 - Shorewall 1.3 Beta 1 Available
- +Beta 1 carries the version designation 1.2.90 and implements the following - features:
+ features: - +-
-
- Simplified rule syntax which - makes the intent of each rule clearer and hopefully makes - Shorewall easier to learn. -
- Upward compatibility with -1.2 configuration files has been maintained so that -current users can migrate to the new syntax at their convenience. -
- WARNING: - Compatibility with the old parameterized sample configurations - has NOT been maintained. Users still running those configurations - should migrate to the new sample configurations before upgrading - to 1.3 Beta 1. +
- Simplified rule syntax which + makes the intent of each rule clearer and hopefully +makes Shorewall easier to learn. +
- Upward compatibility with + 1.2 configuration files has been maintained so that + current users can migrate to the new syntax at their convenience. +
- WARNING: Compatibility with the old + parameterized sample configurations has NOT been maintained. + Users still running those configurations should migrate + to the new sample configurations before upgrading to 1.3 +Beta 1. - +
5/4/2002 - Shorewall 1.2.13 is Available
- +In this version:
- +-
-
- White-listing is supported. -
- SYN-flood protection is - added. -
- IP addresses added under ADD_IP_ALIASES and ADD_SNAT_ALIASES - now inherit the VLSM and Broadcast Address of the interface's - primary IP address. -
- The order in which port forwarding
- DNAT and Static DNAT
+
- IP addresses added under + ADD_IP_ALIASES and ADD_SNAT_ALIASES + now inherit the VLSM and Broadcast Address of the interface's + primary IP address.
+- The order in which port +forwarding DNAT and Static DNAT can now be reversed so that port forwarding rules can override the contents of /etc/shorewall/nat.
- +
4/30/2002 - Shorewall Debian News
- +Lorenzo Marignoni reports that Shorewall 1.2.12 is now in both the Debian Testing Branch and the Debian Unstable Branch.
- +4/20/2002 - Shorewall 1.2.12 is Available
- +-
-
- The 'try' command works again -
- There is now a single RPM -that also works with SuSE. +
- The 'try' command works +again +
- There is now a single RPM + that also works with SuSE. - +
4/17/2002 - Shorewall Debian News
- +Lorenzo Marignoni reports that:
- +-
-
- Shorewall 1.2.10 is in the - Debian - Testing Branch -
- Shorewall 1.2.11 is in the - Debian - Unstable Branch +
- Shorewall 1.2.10 is in the + Debian + Testing Branch +
- Shorewall 1.2.11 is in the + Debian + Unstable Branch - +
Thanks, Lorenzo!
- +4/16/2002 - Shorewall 1.2.11 RPM Available for SuSE
- +Thanks to Stefan Mohr, there - is now a Shorewall 1.2.11 - SuSE RPM available.
+ SuSE RPM available. - +4/13/2002 - Shorewall 1.2.11 Available
- +In this version:
- +-
-
- The 'try' command now accepts - an optional timeout. If the timeout is given in the +
- The 'try' command now accepts + an optional timeout. If the timeout is given in the command, the standard configuration will automatically be restarted after the new configuration has been running for that length of time. This prevents a remote admin from being locked out of the firewall in the case where the new configuration starts but prevents access. -
- Kernel route filtering may -now be enabled globally using the new ROUTE_FILTER parameter - in /etc/shorewall/shorewall.conf. -
- Individual IP source addresses - and/or subnets may now be excluded from masquerading/SNAT. -
- Simple "Yes/No" and "On/Off" - values are now case-insensitive in /etc/shorewall/shorewall.conf. +
- Kernel route filtering may + now be enabled globally using the new ROUTE_FILTER +parameter in /etc/shorewall/shorewall.conf. +
- Individual IP source addresses + and/or subnets may now be excluded from masquerading/SNAT. +
- Simple "Yes/No" and "On/Off" + values are now case-insensitive in /etc/shorewall/shorewall.conf. - +
4/13/2002 - Hamburg Mirror now has FTP
- +Stefan now has an FTP mirror at ftp://germany.shorewall.net/pub/shorewall. - Thanks Stefan!
+ Thanks Stefan! - +4/12/2002 - New Mirror in Hamburg
- +Thanks to Stefan Mohr, there - is now a mirror of the Shorewall website at http://germany.shorewall.net. -
+ - +4/10/2002 - Shorewall QuickStart Guide Version 1.1 Available
- +Version 1.1 of the QuickStart - Guide is now available. Thanks to those who have -read version 1.0 and offered their suggestions. Corrections -have also been made to the sample scripts.
+ Guide is now available. Thanks to those who have + read version 1.0 and offered their suggestions. Corrections + have also been made to the sample scripts. - +4/9/2002 - Shorewall QuickStart Guide Version 1.0 Available
- +Version 1.0 of the QuickStart - Guide is now available. This Guide and its accompanying - sample configurations are expected to provide a replacement - for the recently withdrawn parameterized samples.
+ Guide is now available. This Guide and its accompanying + sample configurations are expected to provide a replacement + for the recently withdrawn parameterized samples. - +4/8/2002 - Parameterized Samples Withdrawn
- +Although the parameterized - samples have allowed people to get a firewall up -and running quickly, they have unfortunately set the wrong -level of expectation among those who have used them. I am -therefore withdrawing support for the samples and I am recommending - that they not be used in new Shorewall installations.
+ samples have allowed people to get a firewall up + and running quickly, they have unfortunately set the wrong + level of expectation among those who have used them. I am + therefore withdrawing support for the samples and I am recommending + that they not be used in new Shorewall installations. - +4/2/2002 - Updated Log Parser
- +John Lodge has provided an updated - version of his CGI-based - log parser with corrected date handling.
+ version of his CGI-based + log parser with corrected date handling. - +3/30/2002 - Shorewall Website Search Improvements
- +The quick search on the home page now excludes the mailing list archives. - The Extended Search allows - excluding the archives or restricting the search to just - the archives. An archive search form is also available on -the mailing list -information page.
+ The Extended Search +allows excluding the archives or restricting the search +to just the archives. An archive search form is also available +on the mailing + list information page. - +3/28/2002 - Debian Shorewall News (From Lorenzo Martignoni)
- +-
-
- The 1.2.10 Debian Package -is available at The 1.2.10 Debian Package + is available at http://security.dsi.unimi.it/~lorenzo/debian.html. -
- Shorewall 1.2.9 is now in -the Shorewall 1.2.9 is now in + the Debian Unstable Distribution. - +
3/25/2002 - Log Parser Available
- +John Lodge has provided a CGI-based log parser for Shorewall. Thanks - John.
+ John. - +3/20/2002 - Shorewall 1.2.10 Released
- +In this version:
- +-
-
- A "shorewall try" command -has been added (syntax: shorewall try <configuration - directory>). This command attempts "shorewall -c - <configuration directory> start" and if that results - in the firewall being stopped due to an error, a "shorewall start" - command is executed. The 'try' command allows you to create - a new configuration and - attempt to start it; if there is an error that leaves your firewall - in the stopped state, it will automatically be restarted using - the default configuration (in /etc/shorewall). -
- A new variable ADD_SNAT_ALIASES - has been added to /etc/shorewall/shorewall.conf. - If this variable is set to "Yes", Shorewall will automatically - add IP addresses listed in the third column of the - /etc/shorewall/masq file. -
- Copyright notices have been - added to the documenation. +
- A "shorewall try" command + has been added (syntax: shorewall try <configuration + directory>). This command attempts "shorewall -c + <configuration directory> start" and if that results + in the firewall being stopped due to an error, a "shorewall +start" command is executed. The 'try' command allows you to +create a new configuration + and attempt to start it; if there is an error that leaves your + firewall in the stopped state, it will automatically be restarted + using the default configuration (in /etc/shorewall). +
- A new variable ADD_SNAT_ALIASES + has been added to /etc/shorewall/shorewall.conf. + If this variable is set to "Yes", Shorewall will +automatically add IP addresses listed in the third +column of the /etc/shorewall/masq +file. +
- Copyright notices have been + added to the documenation. - +
3/11/2002 - Shorewall 1.2.9 Released
- +In this version:
- +-
-
- Filtering by Filtering by MAC address has been added.
MAC addresses may be used as the source address in:
-
+
-
-
- Filtering rules (Filtering rules (/etc/shorewall/rules) -
- Traffic Control Classification - Rules (/etc/shorewall/tcrules) -
- TOS Rules (Traffic Control Classification + Rules (/etc/shorewall/tcrules) +
- TOS Rules (/etc/shorewall/tos) -
- Blacklist (Blacklist (/etc/shorewall/blacklist) - +
- - Several bugs have been fixed -
- The 1.2.9 Debian Package is
- also available at
+
- Several bugs have been fixed
+- The 1.2.9 Debian Package +is also available at http://security.dsi.unimi.it/~lorenzo/debian.html.
- +
3/1/2002 - 1.2.8 Debian Package is Available
- +See http://security.dsi.unimi.it/~lorenzo/debian.html
- +2/25/2002 - New Two-interface Sample
- +I've enhanced the two interface sample to allow access from the firewall - to servers in the local zone - - http://www.shorewall.net/pub/shorewall/LATEST.samples/two-interfaces.tgz
+ http://www.shorewall.net/pub/shorewall/LATEST.samples/two-interfaces.tgz - +2/23/2002 - Shorewall 1.2.8 Released
- +Do to a serious problem with 1.2.7, I am releasing 1.2.8. It corrects problems associated with the lock file used to prevent multiple state-changing - operations from occuring simultaneously. My apologies - for any inconvenience my carelessness may have caused.
+ operations from occuring simultaneously. My apologies + for any inconvenience my carelessness may have caused. - +2/22/2002 - Shorewall 1.2.7 Released
- +In this version:
- +-
-
- UPnP probes (UDP destination - port 1900) are now silently dropped in the common - chain -
- RFC 1918 checking in the mangle - table has been streamlined to no longer require packet - marking. RFC 1918 checking in the filter table has been - changed to require half as many rules as previously. -
- A 'shorewall check' command - has been added that does a cursory validation of the - zones, interfaces, hosts, rules and policy files. +
- UPnP probes (UDP destination + port 1900) are now silently dropped in the common + chain +
- RFC 1918 checking in the +mangle table has been streamlined to no longer require +packet marking. RFC 1918 checking in the filter table has +been changed to require half as many rules as previously. +
- A 'shorewall check' command + has been added that does a cursory validation of the + zones, interfaces, hosts, rules and policy files. - +
2/18/2002 - 1.2.6 Debian Package is Available
- +See http://security.dsi.unimi.it/~lorenzo/debian.html
- +2/8/2002 - Shorewall 1.2.6 Released
- +In this version:
- +-
-
- $-variables may now be used - anywhere in the configuration files except /etc/shorewall/zones. -
- The interfaces and hosts files - now have their contents validated before any changes - are made to the existing Netfilter configuration. The appearance - of a zone name that isn't defined in /etc/shorewall/zones -causes "shorewall start" and "shorewall restart" to abort without -changing the Shorewall state. Unknown options in either file cause -a warning to be issued. -
- A problem occurring when BLACKLIST_LOGLEVEL - was not set has been corrected. +
- $-variables may now be used + anywhere in the configuration files except /etc/shorewall/zones. +
- The interfaces and hosts +files now have their contents validated before any +changes are made to the existing Netfilter configuration. The +appearance of a zone name that isn't defined in /etc/shorewall/zones + causes "shorewall start" and "shorewall restart" to abort without + changing the Shorewall state. Unknown options in either file +cause a warning to be issued. +
- A problem occurring when +BLACKLIST_LOGLEVEL was not set has been corrected. - +
2/4/2002 - Shorewall 1.2.5 Debian Package Available
- +see http://security.dsi.unimi.it/~lorenzo/debian.html
- +2/1/2002 - Shorewall 1.2.5 Released
- +Due to installation problems with Shorewall 1.2.4, I have released Shorewall - 1.2.5. Sorry for the rapid-fire development.
+ 1.2.5. Sorry for the rapid-fire development. - +In version 1.2.5:
- +-
-
- The installation problems have - been corrected. -
- The installation problems +have been corrected. +
- SNAT is now supported. -
- A "shorewall version" command - has been added -
- The default value of the STATEDIR - variable in /etc/shorewall/shorewall.conf has been changed - to /var/lib/shorewall in order to conform to the GNU/Linux - File Hierarchy Standard, Version 2.2. +
- A "shorewall version" command + has been added +
- The default value of the +STATEDIR variable in /etc/shorewall/shorewall.conf has +been changed to /var/lib/shorewall in order to conform to +the GNU/Linux File Hierarchy Standard, Version 2.2. - +
1/28/2002 - Shorewall 1.2.4 Released
- +-
-
- The "fw" zone The "fw" zone may now be given a different name. -
- You may now place end-of-line - comments (preceded by '#') in any of the configuration - files -
- There is now protection against - against two state changing operations occuring concurrently. - This is implemented using the 'lockfile' utility if it -is available (lockfile is part of procmail); otherwise, a less - robust technique is used. The lockfile is created in the STATEDIR - defined in /etc/shorewall/shorewall.conf and has the name "lock". -
- "shorewall start" no longer -fails if "detect" is specified in You may now place end-of-line + comments (preceded by '#') in any of the configuration + files +
- There is now protection against + against two state changing operations occuring concurrently. + This is implemented using the 'lockfile' utility if it + is available (lockfile is part of procmail); otherwise, a less + robust technique is used. The lockfile is created in the STATEDIR + defined in /etc/shorewall/shorewall.conf and has the name +"lock". +
- "shorewall start" no longer + fails if "detect" is specified in /etc/shorewall/interfaces for an interface with subnet mask 255.255.255.255. - +
1/27/2002 - Shorewall 1.2.3 Debian Package Available -- see http://security.dsi.unimi.it/~lorenzo/debian.html
- +1/20/2002 - Corrected firewall script available
- +Corrects a problem with BLACKLIST_LOGLEVEL. See the - errata for details.
+ errata for details. - +1/19/2002 - Shorewall 1.2.3 Released
- +This is a minor feature and bugfix release. The single new feature is:
- +-
-
- Support for TCP MSS Clamp to - PMTU -- This support is usually required when the internet - connection is via PPPoE or PPTP and may be enabled using the - CLAMPMSS option in /etc/shorewall/shorewall.conf. +
- Support for TCP MSS Clamp +to PMTU -- This support is usually required when the +internet connection is via PPPoE or PPTP and may be enabled +using the CLAMPMSS option +in /etc/shorewall/shorewall.conf. - +
The following problems were corrected:
- +-
-
- The "shorewall status" command - no longer hangs. -
- The "shorewall monitor" command - now displays the icmpdef chain -
- The CLIENT PORT(S) column in - tcrules is no longer ignored +
- The "shorewall status" command + no longer hangs. +
- The "shorewall monitor" command + now displays the icmpdef chain +
- The CLIENT PORT(S) column +in tcrules is no longer ignored - +
1/18/2002 - Shorewall 1.2.2 packaged with new LEAF release
- +Jacques Nilo and Eric Wolzak have released a kernel 2.4.16 LEAF distribution - that includes Shorewall 1.2.2. See http://leaf.sourceforge.net/devel/jnilo - for details.
+ for details. - +1/11/2002 - Debian Package (.deb) Now Available - Thanks to Lorenzo Martignoni, a 1.2.2 - Shorewall Debian package is now available. There is a link - to Lorenzo's site from the Shorewall - download page.
+ Shorewall Debian package is now available. There is a +link to Lorenzo's site from the Shorewall + download page. - +1/9/2002 - Updated 1.2.2 /sbin/shorewall available - This corrected version restores - the "shorewall status" command to health.
+ the "shorewall status" command to health. - +1/8/2002 - Shorewall 1.2.2 Released
- +In version 1.2.2
- +-
-
- Support for IP blacklisting -has been added +
- Support for IP blacklisting
+ has been added
+
-
-
- You specify whether you want - packets from blacklisted hosts dropped or rejected - using the BLACKLIST_DISPOSITION - setting in /etc/shorewall/shorewall.conf -
- You specify whether you want - packets from blacklisted hosts logged and at what - syslog level using the BLACKLIST_LOGLEVEL - setting in /etc/shorewall/shorewall.conf -
- You list the IP addresses/subnets - that you wish to blacklist in You specify whether you +want packets from blacklisted hosts dropped or +rejected using the BLACKLIST_DISPOSITION + setting in /etc/shorewall/shorewall.conf +
- You specify whether you +want packets from blacklisted hosts logged and +at what syslog level using the BLACKLIST_LOGLEVEL +setting in /etc/shorewall/shorewall.conf +
- You list the IP addresses/subnets + that you wish to blacklist in /etc/shorewall/blacklist -
- You specify the interfaces - you want checked against the blacklist using the - new "blacklist" - option in /etc/shorewall/interfaces. -
- The black list is refreshed - from /etc/shorewall/blacklist by the "shorewall -refresh" command. +
- You specify the interfaces + you want checked against the blacklist using +the new "blacklist" + option in /etc/shorewall/interfaces. +
- The black list is refreshed + from /etc/shorewall/blacklist by the "shorewall + refresh" command. - +
- - Use of TCP RST replies has -been expanded + +
- Use of TCP RST replies has
+ been expanded
+
-
-
- TCP connection requests rejected - because of a REJECT policy are now replied with -a TCP RST packet. -
- TCP connection requests rejected - because of a protocol=all rule in /etc/shorewall/rules - are now replied with a TCP RST packet. +
- TCP connection requests +rejected because of a REJECT policy are now replied +with a TCP RST packet. +
- TCP connection requests +rejected because of a protocol=all rule in /etc/shorewall/rules + are now replied with a TCP RST packet. - +
- - A
+
- A LOGFILE specification has been added to /etc/shorewall/shorewall.conf. LOGFILE is used to tell the /sbin/shorewall program where to look for Shorewall - messages.
+ messages.
-
+
1/5/2002 - New Parameterized Samples (version 1.2.0) released. These are minor updates - to the previously-released samples. There are two new rules - added:
+ to the previously-released samples. There are two new +rules added: - +-
-
- Unless you have explicitly -enabled Auth connections (tcp port 113) to your firewall, -these connections will be REJECTED rather than DROPPED. -This speeds up connection establishment to some servers. -
- Orphan DNS replies are now -silently dropped. +
- Unless you have explicitly + enabled Auth connections (tcp port 113) to your firewall, + these connections will be REJECTED rather than DROPPED. + This speeds up connection establishment to some servers. +
- Orphan DNS replies are now + silently dropped. - +
See the README file for upgrade instructions.
- +1/1/2002 - Shorewall Mailing List Moving
- +The Shorewall mailing list hosted at - Sourceforge is moving to Shorewall.net. If you are - a current subscriber to the list at Sourceforge, please is moving to Shorewall.net. If you are + a current subscriber to the list at Sourceforge, please see these instructions. - If you would like to subscribe to the new list, visit http://www.shorewall.net/mailman/listinfo/shorewall-users.
+ If you would like to subscribe to the new list, visit +http://www.shorewall.net/mailman/listinfo/shorewall-users. - +12/31/2001 - Shorewall 1.2.1 Released
- +In version 1.2.1:
- +-
-
- Logging of Mangled/Invalid - Packets is added. -
- The tunnel - script has been corrected. -
- 'shorewall show tc' now correctly - handles tunnels. + Packets is added. +
- The tunnel + script has been corrected. +
- 'shorewall show tc' now correctly + handles tunnels. - +
12/21/2001 - Shorewall 1.2.0 Released! - I couldn't resist releasing 1.2 on 12/21/2001
- +Version 1.2 contains the following new features:
- +-
-
- Support for Support for Traffic Control/Shaping -
- Support for Support for Filtering of Mangled/Invalid Packets -
- Support for Support for GRE Tunnels - +
For the next month or so, I will continue to provide corrections to version - 1.1.18 as necessary so that current version 1.1.x users - will not be forced into a quick upgrade to 1.2.0 just to + 1.1.18 as necessary so that current version 1.1.x users + will not be forced into a quick upgrade to 1.2.0 just to have access to bug fixes.
- +For those of you who have installed one of the Beta RPMS, you will need - to use the "--oldpackage" option when upgrading to 1.2.0:
+ to use the "--oldpackage" option when upgrading to 1.2.0: - +- ++ - +rpm -Uvh --oldpackage shorewall-1.2-0.noarch.rpm
-
12/19/2001 - Thanks to Steve - Cowles, there is now a Shorewall mirror in Texas. -This web site is mirrored at , there is now a Shorewall mirror in Texas. + This web site is mirrored at http://www.infohiiway.com/shorewall - and the ftp site is at ftp://ftp.infohiiway.com/pub/mirrors/shorewall.
- +11/30/2001 - A new set of the parameterized Sample Configurations has been released. In this version:
- +-
-
- Ping is now allowed between -the zones. -
- In the three-interface configuration, - it is now possible to configure the internet services - that are to be available to servers in the DMZ. +
- Ping is now allowed between + the zones. +
- In the three-interface configuration, + it is now possible to configure the internet services + that are to be available to servers in the DMZ. - +
11/20/2001 - The current version of Shorewall is 1.1.18.
- +In this version:
- +-
-
- The spelling of ADD_IP_ALIASES - has been corrected in the shorewall.conf file -
- The logic for deleting user-defined - chains has been simplified so that it avoids a bug in - the LRP version of the 'cut' utility. -
- The /var/lib/lrpkg/shorwall.conf - file has been corrected to properly display the NAT -entry in that file. +
- The spelling of ADD_IP_ALIASES + has been corrected in the shorewall.conf file +
- The logic for deleting user-defined + chains has been simplified so that it avoids a bug in + the LRP version of the 'cut' utility. +
- The /var/lib/lrpkg/shorwall.conf + file has been corrected to properly display the NAT + entry in that file. - +
11/19/2001 - Thanks to Juraj - Ontkanin, there is now a Shorewall mirror in - the Slovak Republic. The website is now mirrored at http://www.nrg.sk/mirror/shorewall - and the FTP site is mirrored at , there is now a Shorewall mirror +in the Slovak Republic. The website is now mirrored +at http://www.nrg.sk/mirror/shorewall + and the FTP site is mirrored at ftp://ftp.nrg.sk/mirror/shorewall.
- +11/2/2001 - Announcing Shorewall Parameter-driven Sample Configurations. - There are three sample configurations:
+ There are three sample configurations: - +-
-
- One Interface -- for a standalone - system. -
- Two Interfaces -- A masquerading - firewall. -
- Three Interfaces -- A masquerading - firewall with DMZ. +
- One Interface -- for a standalone + system. +
- Two Interfaces -- A masquerading + firewall. +
- Three Interfaces -- A masquerading + firewall with DMZ. - +
Samples may be downloaded from ftp://ftp.shorewall.net/pub/shorewall/samples-1.1.17 - . See the README file for instructions.
+ . See the README file for instructions. - +11/1/2001 - The current version of Shorewall is 1.1.17. I intend - this to be the last of the 1.1 Shorewall releases.
+ this to be the last of the 1.1 Shorewall releases. - +In this version:
- +-
-
- The handling of The handling of ADD_IP_ALIASES has - been corrected. + been corrected. - +
10/22/2001 - The current version of Shorewall is 1.1.16. In this - version:
- - --
-
- A new "shorewall show connections" - command has been added. -
- In the "shorewall monitor" -output, the currently tracked connections are now shown -on a separate page. -
- Prior to this release, Shorewall - unconditionally added the external IP adddress(es) -specified in /etc/shorewall/nat. Beginning with version - 1.1.16, a new parameter (ADD_IP_ALIASES) - may be set to "no" (or "No") to inhibit this behavior. - This allows IP aliases created using your distribution's - network configuration tools to be used in static NAT. - - -
10/15/2001 - The current version of Shorewall is 1.1.15. In this - version:
- --
-
- Support for nested zones has - been improved. See the -documentation for details -
- Shorewall now correctly checks - the alternate configuration directory for the 'zones' - file. +
- A new "shorewall show connections" + command has been added. +
- In the "shorewall monitor" + output, the currently tracked connections are now +shown on a separate page. +
- Prior to this release, Shorewall + unconditionally added the external IP adddress(es) + specified in /etc/shorewall/nat. Beginning with version + 1.1.16, a new parameter (ADD_IP_ALIASES) + may be set to "no" (or "No") to inhibit this behavior. + This allows IP aliases created using your distribution's + network configuration tools to be used in static +NAT. - +
10/4/2001 - The current version of Shorewall is 1.1.14. In this - version
+ +10/15/2001 - The current version of Shorewall is 1.1.15. In this + version:
- +-
-
- Shorewall now supports alternate
- configuration directories. When an alternate directory
- is specified when starting or restarting Shorewall (e.g.,
- "shorewall -c /etc/testconf restart"), Shorewall will first
- look for configuration files in the alternate directory then
-in /etc/shorewall. To create an alternate configuration simply:
- 1. Create a New Directory
- 2. Copy to that directory any -of your configuration files that you want to change.
- 3. Modify the copied files as -needed.
- 4. Restart Shorewall specifying - the new directory.
- - The rules for allowing/disallowing - icmp echo-requests (pings) are now moved after rules - created when processing the rules file. This allows you to +
- Support for nested zones +has been improved. See + the documentation for details +
- Shorewall now correctly checks + the alternate configuration directory for the 'zones' + file. + + +
10/4/2001 - The current version of Shorewall is 1.1.14. In this + version
+ + +-
+
- Shorewall now supports alternate
+ configuration directories. When an alternate directory
+ is specified when starting or restarting Shorewall
+(e.g., "shorewall -c /etc/testconf restart"), Shorewall will
+first look for configuration files in the alternate directory then
+ in /etc/shorewall. To create an alternate configuration simply:
+ 1. Create a New Directory
+ 2. Copy to that directory any + of your configuration files that you want to change.
+ 3. Modify the copied files +as needed.
+ 4. Restart Shorewall specifying + the new directory.
+ - The rules for allowing/disallowing + icmp echo-requests (pings) are now moved after rules + created when processing the rules file. This allows you to add rules that selectively allow/deny ping based on source or destination address. -
- Rules that specify multiple -client ip addresses or subnets no longer cause startup -failures. -
- Zone names in the policy file - are now validated against the zones file. -
- If you have Rules that specify multiple + client ip addresses or subnets no longer cause startup + failures. +
- Zone names in the policy +file are now validated against the zones file. +
- If you have packet mangling support - enabled, the "norfc1918" - interface option now logs and drops any incoming packets - on the interface that have an RFC 1918 destination address. + enabled, the "norfc1918" + interface option now logs and drops any incoming packets + on the interface that have an RFC 1918 destination address. - +
9/12/2001 - The current version of Shorewall is 1.1.13. In this - version
+ version - +-
-
- Shell variables can now be -used to parameterize Shorewall rules. -
- The second column in the hosts
- file may now contain a comma-separated list.
-
- Example:
- sea eth0:130.252.100.0/24,206.191.149.0/24
- - Handling of multi-zone interfaces - has been improved. See the Shell variables can now be + used to parameterize Shorewall rules. +
- The second column in the
+hosts file may now contain a comma-separated list.
+
+ Example:
+ sea eth0:130.252.100.0/24,206.191.149.0/24
+ - Handling of multi-zone interfaces + has been improved. See the documentation for the /etc/shorewall/interfaces - file. + file. - +
8/28/2001 - The current version of Shorewall is 1.1.12. In this - version
+ version - +-
-
- Several columns in the rules - file may now contain comma-separated lists. -
- Shorewall is now more rigorous - in parsing the options in /etc/shorewall/interfaces. -
- Complementation using "!" is - now supported in rules. +
- Several columns in the rules + file may now contain comma-separated lists. +
- Shorewall is now more rigorous + in parsing the options in /etc/shorewall/interfaces. +
- Complementation using "!" +is now supported in rules. - +
7/28/2001 - The current version of Shorewall is 1.1.11. In this - version
+ version - +-
-
- A "shorewall refresh" command - has been added to allow for refreshing the rules associated - with the broadcast address on a dynamic interface. This - command should be used in place of "shorewall restart" when the - internet interface's IP address changes. -
- The /etc/shorewall/start file - (if any) is now processed after all temporary rules have - been deleted. This change prevents the accidental removal - of rules added during the processing of that file. -
- The "dhcp" interface option -is now applicable to firewall interfaces used by a DHCP -server running on the firewall. -
- The RPM can now be built from - the .tgz file using "rpm -tb" +
- A "shorewall refresh" command + has been added to allow for refreshing the rules associated + with the broadcast address on a dynamic interface. This + command should be used in place of "shorewall restart" when +the internet interface's IP address changes. +
- The /etc/shorewall/start +file (if any) is now processed after all temporary +rules have been deleted. This change prevents the accidental + removal of rules added during the processing of that file. +
- The "dhcp" interface option + is now applicable to firewall interfaces used by a DHCP + server running on the firewall. +
- The RPM can now be built +from the .tgz file using "rpm -tb" - +
7/6/2001 - The current version of Shorewall is 1.1.10. In this version
- +-
-
- Shorewall now enables Ipv4 -Packet Forwarding by default. Packet forwarding may +
- Shorewall now enables Ipv4 + Packet Forwarding by default. Packet forwarding may be disabled by specifying IP_FORWARD=Off in /etc/shorewall/shorewall.conf. - If you don't want Shorewall to enable or disable packet - forwarding, add IP_FORWARDING=Keep to your /etc/shorewall/shorewall.conf - file. -
- The "shorewall hits" command - no longer lists extraneous service names in its last -report. -
- Erroneous instructions in the - comments at the head of the firewall script have been - corrected. + If you don't want Shorewall to enable or disable packet + forwarding, add IP_FORWARDING=Keep to your /etc/shorewall/shorewall.conf + file. +
- The "shorewall hits" command + no longer lists extraneous service names in its last + report. +
- Erroneous instructions in +the comments at the head of the firewall script have +been corrected. - +
6/23/2001 - The current version of Shorewall is 1.1.9. In this version
- +-
-
- The "tunnels" file really - is in the RPM now. -
- SNAT can now be applied to -port-forwarded connections. -
- A bug which would cause firewall - start failures in some dhcp configurations has been -fixed. -
- The firewall script now issues - a message if you have the name of an interface in the - second column in an entry in /etc/shorewall/masq and that - interface is not up. -
- You can now configure Shorewall - so that it doesn't require the - NAT and/or mangle netfilter modules. -
- Thanks to Alex Polishchuk, -the "hits" command from seawall is now in shorewall. -
- Support for The "tunnels" file really + is in the RPM now. +
- SNAT can now be applied to + port-forwarded connections. +
- A bug which would cause firewall + start failures in some dhcp configurations has been + fixed. +
- The firewall script now issues + a message if you have the name of an interface in +the second column in an entry in /etc/shorewall/masq and +that interface is not up. +
- You can now configure Shorewall + so that it doesn't require the + NAT and/or mangle netfilter modules. +
- Thanks to Alex Polishchuk, + the "hits" command from seawall is now in shorewall. +
- Support for IPIP tunnels has been added. - +
6/18/2001 - The current version of Shorewall is 1.1.8. In this version
- +-
-
- A typo in the sample rules -file has been corrected. -
- It is now possible to restrict
- masquerading by destination
+
- A typo in the sample rules + file has been corrected.
+- It is now possible to restrict + masquerading by destination host or subnet.
-- It is now possible to have -static NAT rules applied to packets -originating on the firewall itself.
+- It is now possible to have + static NAT rules applied to packets + originating on the firewall itself.
- +
6/2/2001 - The current version of Shorewall is 1.1.7. In this version
- +-
-
- The TOS rules are now deleted - when the firewall is stopped. -
- The .rpm will now install regardless - of which version of iptables is installed. -
- The .rpm will now install without - iproute2 being installed. -
- The documentation has been -cleaned up. -
- The sample configuration files - included in Shorewall have been formatted to 80 columns - for ease of editing on a VGA console. +
- The TOS rules are now deleted + when the firewall is stopped. +
- The .rpm will now install +regardless of which version of iptables is installed. +
- The .rpm will now install +without iproute2 being installed. +
- The documentation has been + cleaned up. +
- The sample configuration +files included in Shorewall have been formatted +to 80 columns for ease of editing on a VGA console. - +
5/25/2001 - The current version of Shorewall is 1.1.6. In this version
- +-
-
- You may now rate-limit the packet log. -
- Previous versions - of Shorewall have an implementation of Static NAT which violates - the principle of least surprise. NAT only occurs for packets +
- Previous versions + of Shorewall have an implementation of Static NAT which violates + the principle of least surprise. NAT only occurs for packets arriving at (DNAT) or send from (SNAT) the interface named in the INTERFACE column of /etc/shorewall/nat. Beginning with version 1.1.6, NAT effective regardless of which interface -packets come from or are destined to. To get compatibility with -prior versions, I have added a new "ALL "ALL INTERFACES" column to /etc/shorewall/nat. - By placing "no" or "No" in the new column, the NAT behavior -of prior versions may be retained. -
- The treatment of
+
- The treatment of IPSEC Tunnels where the remote gateway is a standalone system has been improved. Previously, it was necessary to include an additional rule allowing UDP port 500 traffic @@ -2051,212 +2162,219 @@ to pass through the tunnel. Shorewall will now create this rule automatically when you place the name of the remote peer's zone in a new GATEWAY ZONE column in /etc/shorewall/tunnels.
- +
5/20/2001 - The current version of Shorewall is 1.1.5. In this version
- +-
-
- You may now pass parameters when loading netfilter modules and you can specify the modules - to load. -
- Compressed modules are now -loaded. This requires that you modutils support loading -compressed modules. -
- +
- Compressed modules are now + loaded. This requires that you modutils support loading + compressed modules. +
- You may now set the Type of Service - (TOS) field in packets. -
- Corrected rules generated for - port redirection (again). + (TOS) field in packets. +
- Corrected rules generated +for port redirection (again). - +
5/10/2001 - The current version of Shorewall is 1.1.4. In this version
- +-
-
- Accepting RELATED connections is now optional. -
- Corrected problem where if -"shorewall start" aborted early (due to kernel configuration -errors for example), superfluous 'sed' error messages -were reported. -
- Corrected rules generated for - port redirection. -
- The order in which iptables -kernel modules are loaded has been corrected (Thanks -to Mark Pavlidis). +
- Corrected problem where if + "shorewall start" aborted early (due to kernel configuration + errors for example), superfluous 'sed' error messages + were reported. +
- Corrected rules generated +for port redirection. +
- The order in which iptables + kernel modules are loaded has been corrected (Thanks + to Mark Pavlidis). - +
4/28/2001 - The current version of Shorewall is 1.1.3. In this version
- +-
-
- Correct message issued when -Proxy ARP address added (Thanks to Jason Kirtland). -
- /tmp/shorewallpolicy-$$ is -now removed if there is an error while starting the firewall. -
- /etc/shorewall/icmp.def and -/etc/shorewall/common.def are now used to define the -icmpdef and common chains unless overridden by the presence - of /etc/shorewall/icmpdef or /etc/shorewall/common. -
- In the .lrp, the file /var/lib/lrpkg/shorwall.conf - has been corrected. An extra space after "/etc/shorwall/policy" - has been removed and "/etc/shorwall/rules" has been added. -
- When a sub-shell encounters -a fatal error and has stopped the firewall, it now kills - the main shell so that the main shell will not continue. -
- A problem has been corrected - where a sub-shell stopped the firewall and main shell - continued resulting in a perplexing error message referring - to "common.so" resulted. -
- Previously, placing "-" in -the PORT(S) column in /etc/shorewall/rules resulted in -an error message during start. This has been corrected. -
- The first line of "install.sh" - has been corrected -- I had inadvertently deleted the +
- Correct message issued when + Proxy ARP address added (Thanks to Jason Kirtland). +
- /tmp/shorewallpolicy-$$ is + now removed if there is an error while starting the +firewall. +
- /etc/shorewall/icmp.def and + /etc/shorewall/common.def are now used to define the + icmpdef and common chains unless overridden by the presence + of /etc/shorewall/icmpdef or /etc/shorewall/common. +
- In the .lrp, the file /var/lib/lrpkg/shorwall.conf + has been corrected. An extra space after "/etc/shorwall/policy" + has been removed and "/etc/shorwall/rules" has been +added. +
- When a sub-shell encounters + a fatal error and has stopped the firewall, it now kills + the main shell so that the main shell will not continue. +
- A problem has been corrected + where a sub-shell stopped the firewall and main shell + continued resulting in a perplexing error message referring + to "common.so" resulted. +
- Previously, placing "-" in + the PORT(S) column in /etc/shorewall/rules resulted in + an error message during start. This has been corrected. +
- The first line of "install.sh" + has been corrected -- I had inadvertently deleted the initial "#". - +
4/12/2001 - The current version of Shorewall is 1.1.2. In this version
- +-
-
- Port redirection now works -again. -
- The icmpdef and common chains - may now be user-defined. -
- The firewall no longer fails - to start if "routefilter" is specified for an interface - that isn't started. A warning message is now issued - in this case. -
- The LRP Version is renamed -"shorwall" for 8,3 MSDOS file system compatibility. -
- A couple of LRP-specific problems - were corrected. +
- Port redirection now works + again. +
- The icmpdef and common chains + may now be user-defined. +
- The firewall no longer fails + to start if "routefilter" is specified for an interface + that isn't started. A warning message is now issued + in this case. +
- The LRP Version is renamed + "shorwall" for 8,3 MSDOS file system compatibility. +
- A couple of LRP-specific +problems were corrected. - +
4/8/2001 - Shorewall is now affiliated with the Leaf Project 
-
4/5/2001 - The current version of Shorewall is 1.1.1. In this version:
- +-
-
- The common chain is traversed - from INPUT, OUTPUT and FORWARD before logging occurs -
- The source has been cleaned -up dramatically -
- DHCP DISCOVER packets with -RFC1918 source addresses no longer generate log messages. -Linux DHCP clients generate such packets and it's -annoying to see them logged. +
- The common chain is traversed + from INPUT, OUTPUT and FORWARD before logging occurs +
- The source has been cleaned + up dramatically +
- DHCP DISCOVER packets with + RFC1918 source addresses no longer generate log messages. + Linux DHCP clients generate such packets and it's + annoying to see them logged. - +
3/25/2001 - The current version of Shorewall is 1.1.0. In this version:
- +-
-
- Log messages now indicate the - packet disposition. -
- Error messages have been improved. -
- The ability to define zones -consisting of an enumerated set of hosts and/or subnetworks -has been added. -
- The zone-to-zone chain matrix - is now sparse so that only those chains that contain - meaningful rules are defined. -
- 240.0.0.0/4 and 169.254.0.0/16 - have been added to the source subnetworks whose packets - are dropped under the norfc1918 interface - option. -
- Exits are now provided for -executing an user-defined script when a chain is +
- Log messages now indicate +the packet disposition. +
- Error messages have been +improved. +
- The ability to define zones + consisting of an enumerated set of hosts and/or subnetworks + has been added. +
- The zone-to-zone chain matrix + is now sparse so that only those chains that contain + meaningful rules are defined. +
- 240.0.0.0/4 and 169.254.0.0/16 + have been added to the source subnetworks whose packets + are dropped under the norfc1918 interface + option. +
- Exits are now provided for + executing an user-defined script when a chain is defined, when the firewall is initialized, when the firewall is started, when the firewall is stopped and when the firewall is cleared. -
- The Linux kernel's route filtering - facility can now be specified selectively on network - interfaces. +
- The Linux kernel's route +filtering facility can now be specified selectively +on network interfaces. - +
3/19/2001 - The current version of Shorewall is 1.0.4. This version:
- +-
-
- Allows user-defined zones. -Shorewall now has only one pre-defined zone (fw) +
- Allows user-defined zones. + Shorewall now has only one pre-defined zone (fw) with the remaining zones being defined in the new configuration file /etc/shorewall/zones. The /etc/shorewall/zones file released in this version provides behavior that is compatible with Shorewall 1.0.3. -
- Adds the ability to specify -logging in entries in the /etc/shorewall/rules file. -
- Correct handling of the icmp-def - chain so that only ICMP packets are sent through +
- Adds the ability to specify + logging in entries in the /etc/shorewall/rules file. +
- Correct handling of the icmp-def + chain so that only ICMP packets are sent through the chain. -
- Compresses the output of "shorewall - monitor" if awk is installed. Allows the command to work - if awk isn't installed (although it's not pretty). +
- Compresses the output of +"shorewall monitor" if awk is installed. Allows the +command to work if awk isn't installed (although it's +not pretty). - +
3/13/2001 - The current version of Shorewall is 1.0.3. This is a bug-fix - release with no new features.
+ release with no new features. - +-
-
- The PATH variable in the firewall - script now includes /usr/local/bin and /usr/local/sbin. -
- DMZ-related chains are now -correctly deleted if the DMZ is deleted. -
- The interface OPTIONS for "gw" - interfaces are no longer ignored. +
- The PATH variable in the +firewall script now includes /usr/local/bin and +/usr/local/sbin. +
- DMZ-related chains are now + correctly deleted if the DMZ is deleted. +
- The interface OPTIONS for +"gw" interfaces are no longer ignored. - +
3/8/2001 - The current version of Shorewall is 1.0.2. It supports an - additional "gw" (gateway) zone for tunnels and it supports - IPSEC tunnels with end-points on the firewall. There is -also a .lrp available now.
+ additional "gw" (gateway) zone for tunnels and it +supports IPSEC tunnels with end-points on the firewall. +There is also a .lrp available now. - -Updated 2/4/2003 - Tom Eastep -
+ +Updated 2/7/2003 - Tom Eastep +
- + Copyright © 2001, 2002 Thomas M. Eastep.
-
+
diff --git a/Shorewall-docs/blacklisting_support.htm b/Shorewall-docs/blacklisting_support.htm index 8999e2eb9..8a36ff001 100644 --- a/Shorewall-docs/blacklisting_support.htm +++ b/Shorewall-docs/blacklisting_support.htm @@ -1,95 +1,99 @@ - + - + - + - +
| + |
Blacklisting Support- |
-
Shorewall supports two different forms of blacklisting; static and dynamic.
- +Static Blacklisting
- -Shorewall static blacklisting support has the following configuration parameters:
- + +Shorewall static blacklisting support has the following configuration +parameters:
+-
-
- You specify whether you want packets from blacklisted hosts dropped -or rejected using the BLACKLIST_DISPOSITION +
- You specify whether you want packets from blacklisted hosts dropped + or rejected using the BLACKLIST_DISPOSITION setting in /etc/shorewall/shorewall.conf -
- You specify whether you want packets from blacklisted hosts logged -and at what syslog level using the BLACKLIST_LOGLEVEL setting in -/etc/shorewall/shorewall.conf -
- You list the IP addresses/subnets that you wish to blacklist in /etc/shorewall/blacklist. Beginning
-with Shorewall version 1.3.8, you may also specify PROTOCOL and Port numbers/Service
-names in the blacklist file.
-
- - You specify the interfaces whose incoming packets you want checked -against the blacklist using the "You specify whether you want packets from blacklisted hosts logged + and at what syslog level using the BLACKLIST_LOGLEVEL setting in + /etc/shorewall/shorewall.conf +
- You list the IP addresses/subnets that you wish to blacklist in
+ /etc/shorewall/blacklist. Beginning
+ with Shorewall version 1.3.8, you may also specify PROTOCOL and Port numbers/Service
+ names in the blacklist file.
+
+ - You specify the interfaces whose incoming packets you want checked + against the blacklist using the "blacklist" option in /etc/shorewall/interfaces. -
- The black list is refreshed from /etc/shorewall/blacklist by the +
- The black list is refreshed from /etc/shorewall/blacklist by the "shorewall refresh" command. - +
Dynamic Blacklisting
- -Dynamic blacklisting support was added in version 1.3.2. Dynamic blacklisting - doesn't use any configuration parameters but is rather controlled using -/sbin/shorewall commands:
- + +Dynamic blacklisting support was added in version 1.3.2. Dynamic blacklisting + doesn't use any configuration parameters but is rather controlled using + /sbin/shorewall commands:
+-
-
- drop <ip address list> - causes packets from the listed -IP addresses to be silently dropped by the firewall. -
- reject <ip address list> - causes packets from the listed -IP addresses to be rejected by the firewall. -
- allow <ip address list> - re-enables receipt of packets -from hosts previously blacklisted by a deny or reject command. -
- save - save the dynamic blacklisting configuration so that it will -be automatically restored the next time that the firewall is restarted. -
- show dynamic - displays the dynamic blacklisting configuration. - +
- drop <ip address list> - causes packets from the listed + IP addresses to be silently dropped by the firewall. +
- reject <ip address list> - causes packets from the +listed IP addresses to be rejected by the firewall. +
- allow <ip address list> - re-enables receipt of packets + from hosts previously blacklisted by a deny or reject command. +
- save - save the dynamic blacklisting configuration so that it will + be automatically restored the next time that the firewall is restarted. +
- show dynamic - displays the dynamic blacklisting configuration. +
+
Example 1:
- -shorewall drop 192.0.2.124 192.0.2.125- + +
shorewall drop 192.0.2.124 192.0.2.125+
Drops packets from hosts 192.0.2.124 and 192.0.2.125
- +Example 2:
- -shorewall allow 192.0.2.125- + +
shorewall allow 192.0.2.125+
Reenables access from 192.0.2.125.
- -Last updated 10/7/2002 - Tom Eastep
- -Copyright - © 2002 Thomas M. Eastep.
-+ +
Last updated 2/7/2003 - Tom Eastep
+ +Copyright + © 2002, 2003 Thomas M. Eastep.
++
diff --git a/Shorewall-docs/configuration_file_basics.htm b/Shorewall-docs/configuration_file_basics.htm index fd526e0e4..2e6379b18 100644 --- a/Shorewall-docs/configuration_file_basics.htm +++ b/Shorewall-docs/configuration_file_basics.htm @@ -1,339 +1,344 @@ - + - + - + - +
| - + |
+
+
Configuration Files- |
-
Warning: If you copy or edit your - configuration files on a system running Microsoft Windows, you must - run them through dos2unix - before you use them with Shorewall.
- -Files
- -Shorewall's configuration files are in the directory /etc/shorewall.
- --
-
- /etc/shorewall/shorewall.conf - used to set several - firewall parameters. -
- /etc/shorewall/params - use this file to set shell - variables that you will expand in other files. -
- /etc/shorewall/zones - partition the firewall's - view of the world into zones. -
- /etc/shorewall/policy - establishes firewall high-level - policy. -
- /etc/shorewall/interfaces - describes the interfaces - on the firewall system. -
- /etc/shorewall/hosts - allows defining zones in - terms of individual hosts and subnetworks. -
- /etc/shorewall/masq - directs the firewall where - to use many-to-one (dynamic) Network Address Translation (a.k.a. - Masquerading) and Source Network Address Translation (SNAT). -
- /etc/shorewall/modules - directs the firewall -to load kernel modules. -
- /etc/shorewall/rules - defines rules that are -exceptions to the overall policies established in /etc/shorewall/policy. -
- /etc/shorewall/nat - defines static NAT rules. -
- /etc/shorewall/proxyarp - defines use of Proxy -ARP. -
- /etc/shorewall/routestopped (Shorewall 1.3.4 and - later) - defines hosts accessible when Shorewall is stopped. -
- /etc/shorewall/tcrules - defines marking of packets - for later use by traffic control/shaping or policy routing. -
- /etc/shorewall/tos - defines rules for setting -the TOS field in packet headers. -
- /etc/shorewall/tunnels - defines IPSEC, GRE and - IPIP tunnels with end-points on the firewall system. -
- /etc/shorewall/blacklist - lists blacklisted IP/subnet/MAC - addresses. -
- /etc/shorewall/init - commands that you wish to execute at the beginning - of a "shorewall start" or "shorewall restart". -
- /etc/shorewall/start - commands that you wish to execute at the completion - of a "shorewall start" or "shorewall restart" -
- /etc/shorewall/stop - commands that you wish to execute at the beginning - of a "shorewall stop". -
- /etc/shorewall/stopped - commands that you wish to execute at the
-completion of a "shorewall stop".
-
-
-
Comments
- -You may place comments in configuration files by making the first non-whitespace - character a pound sign ("#"). You may also place comments at -the end of any line, again by delimiting the comment from the rest -of the line with a pound sign.
- -Examples:
- -# This is a comment- -
ACCEPT net fw tcp www #This is an end-of-line comment- -
Line Continuation
- -You may continue lines in the configuration files using the usual backslash - ("\") followed immediately by a new line character.
- -Example:
- -ACCEPT net fw tcp \- -
smtp,www,pop3,imap #Services running on the firewall
Using DNS Names
- -- -
WARNING: I personally recommend strongly against
- using DNS names in Shorewall configuration files. If you use DNS names
- and you are called out of bed at 2:00AM because Shorewall won't start
- as a result of DNS problems then don't say that you were not forewarned.
-
-
-Tom
-
Beginning with Shorwall 1.3.9, Host addresses in Shorewall
- configuration files may be specified as either IP addresses or DNS
- Names.
-
- DNS names in iptables rules aren't nearly as useful as they
- first appear. When a DNS name appears in a rule, the iptables utility
- resolves the name to one or more IP addresses and inserts those addresses
- into the rule. So changes in the DNS->IP address relationship that
- occur after the firewall has started have absolutely no effect on the
- firewall's ruleset.
If your firewall rules include DNS names then:
- --
-
- If your /etc/resolv.conf is wrong then your firewall -won't start. -
- If your /etc/nsswitch.conf is wrong then your firewall - won't start. -
- If your Name Server(s) is(are) down then your firewall - won't start. -
- If your startup scripts try to start your firewall before
- starting your DNS server then your firewall won't start.
-
- - Factors totally outside your control (your ISP's router - is down for example), can prevent your firewall from starting. -
- You must bring up your network interfaces prior to starting
- your firewall.
-
-
-
Each DNS name much be fully qualified and include a minumum
- of two periods (although one may be trailing). This restriction is
-imposed by Shorewall to insure backward compatibility with existing
-configuration files.
-
- Examples of valid DNS names:
-
-
-
- mail.shorewall.net -
- shorewall.net. (note the trailing period). - -
- -
-
-
- mail (not fully qualified) -
- shorewall.net (only one period) - -
- -
-
-
- The server address in a DNAT rule (/etc/shorewall/rules - file) -
- In the ADDRESS column of an entry in /etc/shorewall/masq. -
- In the /etc/shorewall/nat file. - -
- -
Complementing an Address or Subnet
- -Where specifying an IP address, a subnet or an interface, you can - precede the item with "!" to specify the complement of the item. For - example, !192.168.1.4 means "any host but 192.168.1.4". There must -be no white space following the "!".
- -Comma-separated Lists
- -Comma-separated lists are allowed in a number of contexts within the - configuration files. A comma separated list:
- --
-
- Must not have any embedded white space.
- Valid: routestopped,dhcp,norfc1918
- Invalid: routestopped, dhcp, norfc1818
- - If you use line continuation to break a comma-separated - list, the continuation line(s) must begin in column 1 (or -there would be embedded white space) -
- Entries in a comma-separated list may appear in - any order. - -
Port Numbers/Service Names
- -Unless otherwise specified, when giving a port number you can use - either an integer or a service name from /etc/services.
- -Port Ranges
- -If you need to specify a range of ports, the proper syntax is <low
- port number>:<high port number>. For example,
- if you want to forward the range of tcp ports 4000 through 4100 to
-local host 192.168.1.3, the entry in /etc/shorewall/rules is:
-
DNAT net loc:192.168.1.3 tcp 4000:4100- -
Using Shell Variables
- -You may use the /etc/shorewall/params file to set shell variables - that you can then use in some of the other configuration files.
- -It is suggested that variable names begin with an upper case letter to distinguish them from variables used internally - within the Shorewall programs
- -Example:
- -- -+ + -NET_IF=eth0-
NET_BCAST=130.252.100.255
NET_OPTIONS=noping,norfc1918
- Example (/etc/shorewall/interfaces record):
- -- - -net $NET_IF $NET_BCAST $NET_OPTIONS-
The result will be the same as if the record had been written
- - -+ + + ++ + +Warning: If you copy or edit your + configuration files on a system running Microsoft Windows, you must + run them through dos2unix + before you use them with Shorewall.
+ +Files
+ +Shorewall's configuration files are in the directory /etc/shorewall.
+ ++
+ +- /etc/shorewall/shorewall.conf - used to set several + firewall parameters.
+- /etc/shorewall/params - use this file to set +shell variables that you will expand in other files.
+- /etc/shorewall/zones - partition the firewall's + view of the world into zones.
+- /etc/shorewall/policy - establishes firewall +high-level policy.
+- /etc/shorewall/interfaces - describes the interfaces + on the firewall system.
+- /etc/shorewall/hosts - allows defining zones +in terms of individual hosts and subnetworks.
+- /etc/shorewall/masq - directs the firewall where + to use many-to-one (dynamic) Network Address Translation +(a.k.a. Masquerading) and Source Network Address Translation +(SNAT).
+- /etc/shorewall/modules - directs the firewall +to load kernel modules.
+- /etc/shorewall/rules - defines rules that are +exceptions to the overall policies established in /etc/shorewall/policy.
+- /etc/shorewall/nat - defines static NAT rules.
+- /etc/shorewall/proxyarp - defines use of Proxy + ARP.
+- /etc/shorewall/routestopped (Shorewall 1.3.4 +and later) - defines hosts accessible when Shorewall is stopped.
+- /etc/shorewall/tcrules - defines marking of packets + for later use by traffic control/shaping or policy routing.
+- /etc/shorewall/tos - defines rules for setting + the TOS field in packet headers.
+- /etc/shorewall/tunnels - defines IPSEC, GRE and + IPIP tunnels with end-points on the firewall system.
+- /etc/shorewall/blacklist - lists blacklisted +IP/subnet/MAC addresses.
+- /etc/shorewall/init - commands that you wish to execute at the beginning + of a "shorewall start" or "shorewall restart".
+- /etc/shorewall/start - commands that you wish to execute at the +completion of a "shorewall start" or "shorewall restart"
+- /etc/shorewall/stop - commands that you wish to execute at the beginning + of a "shorewall stop".
+- /etc/shorewall/stopped - commands that you wish to execute at the + completion of a "shorewall stop".
+ +
+Comments
+ +You may place comments in configuration files by making the first non-whitespace + character a pound sign ("#"). You may also place comments at + the end of any line, again by delimiting the comment from the +rest of the line with a pound sign.
+ +Examples:
+ +# This is a comment+ +ACCEPT net fw tcp www #This is an end-of-line comment+ +Line Continuation
+ +You may continue lines in the configuration files using the usual backslash + ("\") followed immediately by a new line character.
+ +Example:
+ +ACCEPT net fw tcp \+ +
smtp,www,pop3,imap #Services running on the firewallUsing DNS Names
+ ++ +
WARNING: I personally recommend strongly against + using DNS names in Shorewall configuration files. If you use DNS +names and you are called out of bed at 2:00AM because Shorewall won't +start as a result of DNS problems then don't say that you were not forewarned. +
+ +
+-Tom
+ +
+Beginning with Shorwall 1.3.9, Host addresses in Shorewall + configuration files may be specified as either IP addresses or DNS + Names.
+ +
+
+ DNS names in iptables rules aren't nearly as useful as they + first appear. When a DNS name appears in a rule, the iptables utility + resolves the name to one or more IP addresses and inserts those addresses + into the rule. So changes in the DNS->IP address relationship that + occur after the firewall has started have absolutely no effect on the + firewall's ruleset.If your firewall rules include DNS names then:
+ ++
+ +- If your /etc/resolv.conf is wrong then your firewall +won't start.
+- If your /etc/nsswitch.conf is wrong then your firewall + won't start.
+- If your Name Server(s) is(are) down then your firewall + won't start.
+- If your startup scripts try to start your firewall before + starting your DNS server then your firewall won't start.
+
+- Factors totally outside your control (your ISP's router + is down for example), can prevent your firewall from starting.
+- You must bring up your network interfaces prior to starting + your firewall.
+ +
+Each DNS name much be fully qualified and include a minumum + of two periods (although one may be trailing). This restriction is +imposed by Shorewall to insure backward compatibility with existing +configuration files.
+ +
+
+ Examples of valid DNS names:
++
+ Examples of invalid DNS names:- mail.shorewall.net
+- shorewall.net. (note the trailing period).
+ +
+ ++
+ DNS names may not be used as:- mail (not fully qualified)
+- shorewall.net (only one period)
+ +
+ ++
+ These restrictions are not imposed by Shorewall simply for + your inconvenience but are rather limitations of iptables.- The server address in a DNAT rule (/etc/shorewall/rules + file)
+- In the ADDRESS column of an entry in /etc/shorewall/masq.
+- In the /etc/shorewall/nat file.
+ +
+ +Complementing an Address or Subnet
+ +Where specifying an IP address, a subnet or an interface, you can + precede the item with "!" to specify the complement of the item. For + example, !192.168.1.4 means "any host but 192.168.1.4". There must be +no white space following the "!".
+ +Comma-separated Lists
+ +Comma-separated lists are allowed in a number of contexts within the + configuration files. A comma separated list:
+ ++
+ +- Must not have any embedded white space.
+
+ Valid: routestopped,dhcp,norfc1918
+ Invalid: routestopped, dhcp, norfc1818- If you use line continuation to break a comma-separated + list, the continuation line(s) must begin in column 1 (or +there would be embedded white space)
+- Entries in a comma-separated list may appear +in any order.
+ +Port Numbers/Service Names
+ +Unless otherwise specified, when giving a port number you can use + either an integer or a service name from /etc/services.
+ +Port Ranges
+ +If you need to specify a range of ports, the proper syntax is <low + port number>:<high port number>. For example, + if you want to forward the range of tcp ports 4000 through 4100 to local + host 192.168.1.3, the entry in /etc/shorewall/rules is:
+
+DNAT net loc:192.168.1.3 tcp 4000:4100+If you omit the low port number, a value of zero is assumed; if you omit +the high port number, a value of 65535 is assumed.
+ +Using Shell Variables
+ +You may use the /etc/shorewall/params file to set shell variables + that you can then use in some of the other configuration files.
+ +It is suggested that variable names begin with an upper case letter to distinguish them from variables used internally + within the Shorewall programs
+ +Example:
+ ++ ++ +NET_IF=eth0+
NET_BCAST=130.252.100.255
NET_OPTIONS=noping,norfc1918+ + +
+ Example (/etc/shorewall/interfaces record):+ ++ + +net $NET_IF $NET_BCAST $NET_OPTIONS+The result will be the same as if the record had been written
+ + ++- - -net eth0 130.252.100.255 noping,norfc1918-Variables may be used anywhere in the other configuration +
Variables may be used anywhere in the other configuration files.
- +Using MAC Addresses
- -Media Access Control (MAC) addresses can be used to specify packet - source in several of the configuration files. To use this feature, - your kernel must have MAC Address Match support (CONFIG_IP_NF_MATCH_MAC) + +
Media Access Control (MAC) addresses can be used to specify packet + source in several of the configuration files. To use this feature, + your kernel must have MAC Address Match support (CONFIG_IP_NF_MATCH_MAC) included.
- -MAC addresses are 48 bits wide and each Ethernet Controller has a
- unique MAC address.
-
- In GNU/Linux, MAC addresses are usually written as a
-series of 6 hex numbers separated by colons. Example:
-
- [root@gateway root]# ifconfig eth0
- eth0 Link encap:Ethernet HWaddr 02:00:08:E3:FA:55
- inet addr:206.124.146.176 Bcast:206.124.146.255
- Mask:255.255.255.0
- UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
- RX packets:2398102 errors:0 dropped:0 overruns:0
- frame:0
- TX packets:3044698 errors:0 dropped:0 overruns:0
- carrier:0
- collisions:30394 txqueuelen:100
- RX bytes:419871805 (400.4 Mb) TX bytes:1659782221
- (1582.8 Mb)
- Interrupt:11 Base address:0x1800
-
- Because Shorewall uses colons as a separator for address
- fields, Shorewall requires MAC addresses to be written in another
- way. In Shorewall, MAC addresses begin with a tilde ("~") and consist
- of 6 hex numbers separated by hyphens. In Shorewall, the MAC address
- in the example above would be written "~02-00-08-E3-FA-55".
-
Note: It is not necessary to use the special Shorewall notation + +
MAC addresses are 48 bits wide and each Ethernet Controller has a
+ unique MAC address.
+
+ In GNU/Linux, MAC addresses are usually written as
+a series of 6 hex numbers separated by colons. Example:
+
+ [root@gateway root]# ifconfig eth0
+ eth0 Link encap:Ethernet HWaddr 02:00:08:E3:FA:55
+ inet addr:206.124.146.176 Bcast:206.124.146.255
+ Mask:255.255.255.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:2398102 errors:0 dropped:0 overruns:0
+ frame:0
+ TX packets:3044698 errors:0 dropped:0 overruns:0
+ carrier:0
+ collisions:30394 txqueuelen:100
+ RX bytes:419871805 (400.4 Mb) TX bytes:1659782221
+ (1582.8 Mb)
+ Interrupt:11 Base address:0x1800
+
+ Because Shorewall uses colons as a separator for address
+ fields, Shorewall requires MAC addresses to be written in another
+ way. In Shorewall, MAC addresses begin with a tilde ("~") and
+consist of 6 hex numbers separated by hyphens. In Shorewall, the
+MAC address in the example above would be written "~02-00-08-E3-FA-55".
+
Note: It is not necessary to use the special Shorewall notation
in the /etc/shorewall/maclist file.
-
Shorewall Configurations
- -Shorewall allows you to have configuration directories other than /etc/shorewall. - The shorewall start -and restart commands allow you to specify an alternate configuration - directory and Shorewall will use the files in the alternate directory - rather than the corresponding files in /etc/shorewall. The alternate -directory need not contain a complete configuration; those files not -in the alternate directory will be read from /etc/shorewall.
- -This facility permits you to easily create a test or temporary configuration + +
Shorewall allows you to have configuration directories other than /etc/shorewall. + The shorewall start and + restart commands allow you to specify an alternate configuration + directory and Shorewall will use the files in the alternate directory + rather than the corresponding files in /etc/shorewall. The alternate directory + need not contain a complete configuration; those files not in the alternate + directory will be read from /etc/shorewall.
+ +This facility permits you to easily create a test or temporary configuration by:
- +-
-
- copying the files that need modification from +
- copying the files that need modification from /etc/shorewall to a separate directory; -
- modify those files in the separate directory; +
- modify those files in the separate directory; and -
- specifying the separate directory in a shorewall
- start or shorewall restart command (e.g., shorewall -c /etc/testconfig
+
- specifying the separate directory in a shorewall + start or shorewall restart command (e.g., shorewall -c /etc/testconfig restart ).
- +
Updated 12/29/2002 - Tom Eastep -
+ +Updated 2/7/2003 - Tom Eastep +
- -Copyright
- © 2001, 2002 Thomas M. Eastep.
-
Copyright
+ © 2001, 2002, 2003 Thomas M. Eastep.
+
diff --git a/Shorewall-docs/download.htm b/Shorewall-docs/download.htm index d203f5cfd..4b6be7b3e 100644 --- a/Shorewall-docs/download.htm +++ b/Shorewall-docs/download.htm @@ -1,392 +1,391 @@ - + - + - + - +
-
- Shorewall Download- |
-
Shorewall Download
+I strongly urge you to read and print a copy of the Shorewall QuickStart Guide
- for the configuration that most closely matches your own.
-
The entire set of Shorewall documentation is available in PDF format -at:
- + href="shorewall_quickstart_guide.htm">Shorewall QuickStart Guide + for the configuration that most closely matches your own.+ + +
The entire set of Shorewall documentation is available in PDF format at:
+ ftp://slovakia.shorewall.net/mirror/shorewall/pdf/
- http://slovakia.shorewall.net/pub/shorewall/pdf/
- rsync://slovakia.shorewall.net/shorewall/pdf/
-
The documentation in HTML format is included in the .rpm and in the -.tgz packages below.
- + http://slovakia.shorewall.net/pub/shorewall/pdf/+ rsync://slovakia.shorewall.net/shorewall/pdf/ + + +
The documentation in HTML format is included in the .rpm and in the .tgz +packages below.
+Once you've done that, download one of the modules:
- +-
-
- If you run a RedHat, SuSE, Mandrake,
- Linux PPC or TurboLinux distribution with
- a 2.4 kernel, you can use the RPM version (note: the
-RPM should also work with other distributions that store
-init scripts in /etc/init.d and that include chkconfig or
-insserv). If you find that it works in other cases, let me know so that
- I can mention them here. See the Installation
+
- If you run a RedHat, SuSE, Mandrake, + Linux PPC or TurboLinux distribution + with a 2.4 kernel, you can use the RPM version (note: the + RPM should also work with other distributions that + store init scripts in /etc/init.d and that include chkconfig +or insserv). If you find that it works in other cases, let me know so that + I can mention them here. See the Installation Instructions if you have problems installing the RPM.
-- If you are running LRP, download the .lrp file (you -might also want to download the .tgz so you will have a copy of +
- If you are running LRP, download the .lrp file (you +might also want to download the .tgz so you will have a copy of the documentation).
-- If you run Debian - and would like a .deb package, Shorewall is included in both the - Debian +
+- If you run Debian + and would like a .deb package, Shorewall is included in both +the Debian Testing Branch and the Debian - Unstable Branch.
-- Otherwise, download the shorewall - module (.tgz)
- + href="http://packages.debian.org/unstable/net/shorewall.html">Debian +Unstable Branch.- Otherwise, download the shorewall + module (.tgz)
+
The documentation in HTML format is included in the .tgz and .rpm files + +
The documentation in HTML format is included in the .tgz and .rpm files and there is an documentation .deb that also contains the documentation.
- -Please verify the version that you have downloaded -- during the - release of a new version of Shorewall, the links below may - point to a newer or an older version than is shown below.
- + +Please verify the version that you have downloaded -- during the + release of a new version of Shorewall, the links below may +point to a newer or an older version than is shown below.
+-
-
- RPM - "rpm -qip LATEST.rpm" -
- TARBALL - "tar -ztf LATEST.tgz" (the directory name - will contain the version) -
- LRP - "mkdir Shorewall.lrp; cd Shorewall.lrp; tar - -zxf <downloaded .lrp>; cat var/lib/lrpkg/shorwall.version" +
- RPM - "rpm -qip LATEST.rpm" +
- TARBALL - "tar -ztf LATEST.tgz" (the directory name + will contain the version) +
- LRP - "mkdir Shorewall.lrp; cd Shorewall.lrp; tar + -zxf <downloaded .lrp>; cat var/lib/lrpkg/shorwall.version" - +
Once you have verified the version, check the errata to see -if there are updates that apply to the version that you have - downloaded.
- -WARNING - YOU CAN NOT SIMPLY INSTALL -THE RPM AND ISSUE A "shorewall start" COMMAND. SOME CONFIGURATION - IS REQUIRED BEFORE THE FIREWALL WILL START. Once you have completed configuration + color="#ff0000"> errata to see +if there are updates that apply to the version that you have +downloaded.
+ +WARNING - YOU CAN NOT SIMPLY INSTALL +THE RPM AND ISSUE A "shorewall start" COMMAND. SOME CONFIGURATION +IS REQUIRED BEFORE THE FIREWALL WILL START. Once you have completed configuration of your firewall, you can enable startup by removing the file /etc/shorewall/startup_disabled.
- -Download Latest Version (1.3.13): Remember that updates - to the mirrors occur 1-12 hours after an update to the Washington State -site.
- -+ ++Download Latest Version (1.3.14): Remember that updates + to the mirrors occur 1-12 hours after an update to the Washington +State site.
+ +- +
Browse Download Sites:
- -+ ++- +- -
-- -SERVER LOCATION -DOMAIN -HTTP -FTP -- SourceForge -
-sf.net -+ + +SERVER LOCATION +DOMAIN +HTTP +FTP ++ -SourceForge +
+sf.net +Browse -N/A -- -Slovak Republic -Shorewall.net -Browse -Browse -- -Texas, USA -Infohiiway.com -Browse -Browse -- -Hamburg, Germany -Shorewall.net -Browse -Browse -- -Martinez (Zona Norte - GBA), Argentina -Correofuego.com.ar -Browse -Browse -- +France -Shorewall.net -Browse -Browse -N/A +- +Washington State, USA -Shorewall.net -Browse -Browse +Slovak Republic +Shorewall.net +Browse +Browse + +Texas, USA +Infohiiway.com +Browse +Browse ++ +Hamburg, Germany +Shorewall.net +Browse +Browse ++ +Martinez (Zona Norte - GBA), Argentina +Correofuego.com.ar +Browse +Browse ++ +France +Shorewall.net +Browse +Browse ++ - - + +Washington State, USA +Shorewall.net +Browse +Browse +
CVS:
- -+ ++ +- -The CVS repository at - cvs.shorewall.net contains the latest snapshots of the each Shorewall - component. There's no guarantee that what you find there will work -at all.
-
-Last Updated 1/13/2003 - CVS repository +at cvs.shorewall.net contains the latest snapshots of the each + Shorewall component. There's no guarantee that what you find there +will work at all.
+
+
Last Updated 2/7/2003 - Tom Eastep
- +Copyright © 2001, 2002, 2003 Thomas M. Eastep.
-
diff --git a/Shorewall-docs/errata.htm b/Shorewall-docs/errata.htm index 0007f0e49..5a2a445dd 100644 --- a/Shorewall-docs/errata.htm +++ b/Shorewall-docs/errata.htm @@ -2,634 +2,650 @@ - +
| + |
-
+
Shorewall Errata/Upgrade Issues- |
-
IMPORTANT
- +-
-
-
-
-
If you use a Windows system to download - a corrected script, be sure to run the script through - dos2unix after you have moved - it to your Linux system.
-
- -
-
-
If you are installing Shorewall for the first -time and plan to use the .tgz and install.sh script, you can untar -the archive, replace the 'firewall' script in the untarred directory - with the one you downloaded below, and then run install.sh.
-
- -
-
-
If you are running a Shorewall version earlier - than 1.3.11, when the instructions say to install a corrected firewall - script in /etc/shorewall/firewall, /usr/lib/shorewall/firewall - or /var/lib/shorewall/firewall, use the 'cp' (or 'scp') utility to overwrite - the existing file. DO NOT REMOVE OR RENAME THE OLD /etc/shorewall/firewall - or /var/lib/shorewall/firewall before you do that. /etc/shorewall/firewall - and /var/lib/shorewall/firewall are symbolic links that point - to the 'shorewall' file used by your system initialization scripts - to start Shorewall during boot. It is that file that must be -overwritten with the corrected script. Beginning with Shorewall -1.3.11, you may rename the existing file before copying in the new file.
-
- -
-
DO NOT INSTALL CORRECTED COMPONENTS - ON A RELEASE EARLIER THAN THE ONE THAT THEY ARE LISTED UNDER BELOW. For - example, do NOT install the 1.3.9a firewall script if you are running -1.3.7c.
-
-
-
+ -
+
+
If you use a Windows system to download + a corrected script, be sure to run the script through + dos2unix after you have moved + it to your Linux system.
+
+ -
+
+
If you are installing Shorewall for the +first time and plan to use the .tgz and install.sh script, you can +untar the archive, replace the 'firewall' script in the untarred directory + with the one you downloaded below, and then run install.sh.
+
+ -
+
+
If you are running a Shorewall version earlier + than 1.3.11, when the instructions say to install a corrected firewall + script in /etc/shorewall/firewall, /usr/lib/shorewall/firewall + or /var/lib/shorewall/firewall, use the 'cp' (or 'scp') utility to +overwrite the existing file. DO NOT REMOVE OR RENAME THE OLD +/etc/shorewall/firewall or /var/lib/shorewall/firewall before +you do that. /etc/shorewall/firewall and /var/lib/shorewall/firewall + are symbolic links that point to the 'shorewall' file used by +your system initialization scripts to start Shorewall during +boot. It is that file that must be overwritten with the corrected +script. Beginning with Shorewall 1.3.11, you may rename the existing file +before copying in the new file.
+
+ -
+
+
DO NOT INSTALL CORRECTED COMPONENTS + ON A RELEASE EARLIER THAN THE ONE THAT THEY ARE LISTED UNDER BELOW. +For example, do NOT install the 1.3.9a firewall script if you are running + 1.3.7c.
+
+
+
-
-
- Upgrade Issues -
- Problems
+
- Upgrade Issues
+- Problems in Version 1.3
-- Problems in Version 1.2
-- Problems in Version 1.1
-- Problem with iptables version 1.2.3 +
- Problem with iptables version 1.2.3 on RH7.2
-- Problems - with kernels >= 2.4.18 and RedHat iptables
-- Problems installing/upgrading -RPM on SuSE
-- Problems with iptables version - 1.2.7 and MULTIPORT=Yes
-- Problems with RH Kernel 2.4.18-10 and +
+- Problems with kernels >= 2.4.18 and +RedHat iptables
+- Problems installing/upgrading + RPM on SuSE
+- Problems with iptables +version 1.2.7 and MULTIPORT=Yes
+- Problems with RH Kernel 2.4.18-10 and NAT
- +
-
+ +
Problems in Version 1.3
- +Version 1.3.13
- +-
-
- The 'shorewall add' command produces an error message referring to - 'find_interfaces_by_maclist'. -
- The 'shorewall delete' command can leave behind undeleted rules.
-
-
-
-
-
-
- VLAN interface names of the form "ethn.m" (e.g., eth0.1)
-are not supported in this version or in 1.3.12. If you need such support,
-post on the users list and I can provide you with a patched version.
+ - The 'shorewall add' command produces an error message referring +to 'find_interfaces_by_maclist'. +
- The 'shorewall delete' command can leave behind undeleted rules. +
- The 'shorewall add' command can fail with "iptables: Index of insertion
+too big".
-
Version 1.3.12
+ + All three problems are corrected by this + firewall script which may be installed in /usr/lib/shorewall as described + above.+
-
-
- If RFC_1918_LOG_LEVEL is set to anything but ULOG, the effect is -the same as if RFC_1918_LOG_LEVEL=info had been specified. The problem is -corrected by this - firewall script which may be installed in /usr/lib/shorewall as described - above. -
- VLAN interface names of the form "ethn.m" (e.g., eth0.1) -are not supported in this version or in 1.3.13. If you need such support, +
- VLAN interface names of the form "ethn.m" (e.g., eth0.1)
+are not supported in this version or in 1.3.12. If you need such support,
post on the users list and I can provide you with a patched version.
-
+
Version 1.3.12 LRP
+ +Version 1.3.12
-
-
- The .lrp was missing the /etc/shorewall/routestopped file -- a
-new lrp (shorwall-1.3.12a.lrp) has been released which corrects this problem.
-
+ - If RFC_1918_LOG_LEVEL is set to anything but ULOG, the effect is + the same as if RFC_1918_LOG_LEVEL=info had been specified. The problem +is corrected by this + firewall script which may be installed in /usr/lib/shorewall as described + above. +
- VLAN interface names of the form "ethn.m" (e.g., eth0.1)
+ are not supported in this version or in 1.3.13. If you need such support,
+ post on the users list and I can provide you with a patched version.
+
Version 1.3.11a
+Version 1.3.12 LRP
-
-
- This
- copy of /etc/shorewall/rfc1918 reflects the recent allocation of 82.0.0.0/8.
+ - The .lrp was missing the /etc/shorewall/routestopped file -- a
+new lrp (shorwall-1.3.12a.lrp) has been released which corrects this problem.
Version 1.3.11a
+ +-
+
- This
+ copy of /etc/shorewall/rfc1918 reflects the recent allocation of 82.0.0.0/8.
+
+
+
Version 1.3.11
- +-
-
- When installing/upgrading using the .rpm, you may receive the
- following warnings:
+ - When installing/upgrading using the .rpm, you may receive
+the following warnings:
+
+ user teastep does not exist - using root
+ group teastep does not exist - using root
+
+ These warnings are harmless and may be ignored. Users downloading + the .rpm from shorewall.net or mirrors should no longer see these warnings + as the .rpm you will get from there has been corrected.
+ - DNAT rules that exclude a source subzone (SOURCE column contains
+ ! followed by a sub-zone list) result in an error message and Shorewall
+ fails to start.
- user teastep does not exist - using root
- group teastep does not exist - using root
-
- These warnings are harmless and may be ignored. Users downloading -the .rpm from shorewall.net or mirrors should no longer see these warnings -as the .rpm you will get from there has been corrected.
- - DNAT rules that exclude a source subzone (SOURCE column contains
- ! followed by a sub-zone list) result in an error message and Shorewall
- fails to start.
-
- Install this - corrected script in /usr/lib/shorewall/firewall to correct this problem. + Install this + corrected script in /usr/lib/shorewall/firewall to correct this problem. Thanks go to Roger Aich who analyzed this problem and provided a fix.
-
- This problem is corrected in version 1.3.11a.
-
-
+
+ This problem is corrected in version 1.3.11a.
+ +
Version 1.3.10
- +-
-
- If you experience problems connecting to a PPTP server running
- on your firewall and you have a 'pptpserver' entry in /etc/shorewall/tunnels,
- this
- version of the firewall script may help. Please report any cases where
- installing this script in /usr/lib/shorewall/firewall solved your connection
- problems. Beginning with version 1.3.10, it is safe to save the old version
- of /usr/lib/shorewall/firewall before copying in the new one since /usr/lib/shorewall/firewall
- is the real script now and not just a symbolic link to the real script.
-
-
+ - If you experience problems connecting to a PPTP server running
+ on your firewall and you have a 'pptpserver' entry in /etc/shorewall/tunnels,
+ this
+ version of the firewall script may help. Please report any cases
+where installing this script in /usr/lib/shorewall/firewall solved your
+connection problems. Beginning with version 1.3.10, it is safe to save
+the old version of /usr/lib/shorewall/firewall before copying in the
+new one since /usr/lib/shorewall/firewall is the real script now and
+not just a symbolic link to the real script.
+
+
Version 1.3.9a
- --
-
- If entries are used in /etc/shorewall/hosts and MERGE_HOSTS=No - then the following message appears during "shorewall [re]start": - -
-
+
- If entries are used in /etc/shorewall/hosts and MERGE_HOSTS=No + then the following message appears during "shorewall [re]start": + +
recalculate_interfacess: command not found- +
The updated firewall script at ftp://www.shorewall.net/pub/shorewall/errata/1.3.9/firewall - corrects this problem.Copy the script to /usr/lib/shorewall/firewall + target="_top">ftp://www.shorewall.net/pub/shorewall/errata/1.3.9/firewall + corrects this problem.Copy the script to /usr/lib/shorewall/firewall as described above.- -
-
Alternatively, edit /usr/lob/shorewall/firewall and change the - single occurence (line 483 in version 1.3.9a) of 'recalculate_interefacess' - to 'recalculate_interface'.- -
-
-
-
- The installer (install.sh) issues a misleading message "Common
- functions installed in /var/lib/shorewall/functions" whereas the file
- is installed in /usr/lib/shorewall/functions. The installer also performs
- incorrectly when updating old configurations that had the file /etc/shorewall/functions.
- Here
- is an updated version that corrects these problems.
-
-
-
Alternatively, edit /usr/lob/shorewall/firewall and change the + single occurence (line 483 in version 1.3.9a) of 'recalculate_interefacess' + to 'recalculate_interface'.+ +
+
-
+
- The installer (install.sh) issues a misleading message
+"Common functions installed in /var/lib/shorewall/functions" whereas
+the file is installed in /usr/lib/shorewall/functions. The installer
+also performs incorrectly when updating old configurations that had the
+file /etc/shorewall/functions. Here
+ is an updated version that corrects these problems.
+
+
+
Version 1.3.9
- TUNNELS Broken in 1.3.9!!! There is an updated firewall + TUNNELS Broken in 1.3.9!!! There is an updated firewall script at ftp://www.shorewall.net/pub/shorewall/errata/1.3.9/firewall + target="_top">ftp://www.shorewall.net/pub/shorewall/errata/1.3.9/firewall -- copy that file to /usr/lib/shorewall/firewall as described above.-
- Version 1.3.8 +
+ Version 1.3.8
-
-
- Use of shell variables in the LOG LEVEL or SYNPARMS +
- Use of shell variables in the LOG LEVEL or SYNPARMS columns of the policy file doesn't work. -
- A DNAT rule with the same original and new IP addresses
- but with different port numbers doesn't work (e.g., "DNAT loc dmz:10.1.1.1:24
- tcp 25 - 10.1.1.1")
-
-
-
Version 1.3.7b
- -DNAT rules where the source zone is 'fw' ($FW) - result in an error message. Installing - - this corrected firewall script in /var/lib/shorewall/firewall - as described above corrects this problem.
- -Version 1.3.7a
- -"shorewall refresh" is not creating the proper - rule for FORWARDPING=Yes. Consequently, after - "shorewall refresh", the firewall will not forward - icmp echo-request (ping) packets. Installing - - this corrected firewall script in /var/lib/shorewall/firewall - as described above corrects this problem.
- -Version <= 1.3.7a
- -If "norfc1918" and "dhcp" are both specified as - options on a given interface then RFC 1918 - checking is occurring before DHCP checking. This - means that if a DHCP client broadcasts using an - RFC 1918 source address, then the firewall will - reject the broadcast (usually logging it). This - has two problems:
- --
-
- If the firewall is -running a DHCP server, the client -won't be able to obtain an IP address - lease from that server. -
- With this order of -checking, the "dhcp" option cannot -be used as a noise-reduction measure -where there are both dynamic and static - clients on a LAN segment. - -
- This version of the 1.3.7a firewall script - corrects the problem. It must be installed - in /var/lib/shorewall as described -above.
- -Version 1.3.7
- -Version 1.3.7 dead on arrival -- please use - version 1.3.7a and check your version against - these md5sums -- if there's a difference, please - download again.
- -d2fffb7fb99bcc6cb047ea34db1df10 shorewall-1.3.7a.tgz- -
6a7fd284c8685b2b471a2f47b469fb94 shorewall-1.3.7a-1.noarch.rpm
3decd14296effcff16853106771f7035 shorwall-1.3.7a.lrp
In other words, type "md5sum <whatever package you downloaded> - and compare the result with what you see above.
- -I'm embarrassed to report that 1.2.7 was also DOA -- maybe I'll skip the - .7 version in each sequence from now on.
- -Version 1.3.6
- --
-
-
-
-
-
If ADD_SNAT_ALIASES=Yes is specified in /etc/shorewall/shorewall.conf, - an error occurs when the firewall script attempts to add - an SNAT alias.
-
- -
-
-
The logunclean and dropunclean options - cause errors during startup when Shorewall is run with iptables - 1.2.7.
+ - A DNAT rule with the same original and new IP addresses
+ but with different port numbers doesn't work (e.g., "DNAT loc dmz:10.1.1.1:24
+ tcp 25 - 10.1.1.1")
These problems are fixed in - this correct firewall script which must be installed in - /var/lib/shorewall/ as described above. These problems are also - corrected in version 1.3.7.
- -Two-interface Samples 1.3.6 (file two-interfaces.tgz)
- -A line was inadvertently deleted from the "interfaces - file" -- this line should be added back in if the version that you - downloaded is missing it:
- -net eth0 detect routefilter,dhcp,norfc1918
- -If you downloaded two-interfaces-a.tgz then the above - line should already be in the file.
- -Version 1.3.5-1.3.5b
- -The new 'proxyarp' interface option doesn't work :-( - This is fixed in - this corrected firewall script which must be installed in - /var/lib/shorewall/ as described above.
- -Versions 1.3.4-1.3.5a
- -Prior to version 1.3.4, host file entries such as the - following were allowed:
- -adm eth0:1.2.4.5,eth0:5.6.7.8-
That capability was lost in version 1.3.4 so that it is only - possible to include a single host specification on each line. - This problem is corrected by this - modified 1.3.5a firewall script. Install the script in /var/lib/pub/shorewall/firewall - as instructed above.
-This problem is corrected in version 1.3.5b.
-Version 1.3.5
- -REDIRECT rules are broken in this version. Install - - this corrected firewall script in /var/lib/pub/shorewall/firewall - as instructed above. This problem is corrected in version - 1.3.5a.
- -Version 1.3.n, n < 4
- -The "shorewall start" and "shorewall restart" commands - to not verify that the zones named in the /etc/shorewall/policy file - have been previously defined in the /etc/shorewall/zones file. -The "shorewall check" command does perform this verification so -it's a good idea to run that command after you have made configuration - changes.
- -Version 1.3.n, n < 3
- -If you have upgraded from Shorewall 1.2 and after - "Activating rules..." you see the message: "iptables: No chains/target/match - by that name" then you probably have an entry in /etc/shorewall/hosts - that specifies an interface that you didn't include in -/etc/shorewall/interfaces. To correct this problem, you -must add an entry to /etc/shorewall/interfaces. Shorewall 1.3.3 and - later versions produce a clearer error message in this case.
- -Version 1.3.2
- -Until approximately 2130 GMT on 17 June 2002, the - download sites contained an incorrect version of the .lrp file. That - file can be identified by its size (56284 bytes). The correct version - has a size of 38126 bytes.
- --
-
- The code to detect a duplicate interface - entry in /etc/shorewall/interfaces contained a typo that -prevented it from working correctly. -
- "NAT_BEFORE_RULES=No" was broken; it behaved - just like "NAT_BEFORE_RULES=Yes". - -
Both problems are corrected in - this script which should be installed in /var/lib/shorewall - as described above.
- --
-
-
+ Installing
+ this corrected firewall script in /var/lib/shorewall/firewall
+ as described above corrects these
+problems.
+
Version 1.3.7b
+ +DNAT rules where the source zone is 'fw' ($FW) + result in an error message. Installing + + this corrected firewall script in /var/lib/shorewall/firewall + as described above corrects this +problem.
+ +Version 1.3.7a
+ +"shorewall refresh" is not creating the proper + rule for FORWARDPING=Yes. Consequently, after + "shorewall refresh", the firewall will not forward + icmp echo-request (ping) packets. Installing + + this corrected firewall script in /var/lib/shorewall/firewall + as described above corrects this +problem.
+ +Version <= 1.3.7a
+ +If "norfc1918" and "dhcp" are both specified as + options on a given interface then RFC 1918 + checking is occurring before DHCP checking. This + means that if a DHCP client broadcasts using an + RFC 1918 source address, then the firewall will + reject the broadcast (usually logging it). This + has two problems:
+ +-
+
- If the firewall is +running a DHCP server, the client +won't be able to obtain an IP address + lease from that server. +
- With this order of +checking, the "dhcp" option cannot +be used as a noise-reduction measure +where there are both dynamic and static + clients on a LAN segment. + +
The IANA have just announced the allocation of subnet - 221.0.0.0/8. This - updated rfc1918 file reflects that allocation.
-
-
+
+
+ This version of the 1.3.7a firewall script + corrects the problem. It must be installed + in /var/lib/shorewall as described + above.
+ +Version 1.3.7
+ +Version 1.3.7 dead on arrival -- please use + version 1.3.7a and check your version against + these md5sums -- if there's a difference, please + download again.
+ +d2fffb7fb99bcc6cb047ea34db1df10 shorewall-1.3.7a.tgz+ +
6a7fd284c8685b2b471a2f47b469fb94 shorewall-1.3.7a-1.noarch.rpm
3decd14296effcff16853106771f7035 shorwall-1.3.7a.lrp
In other words, type "md5sum <whatever package you downloaded> + and compare the result with what you see above.
+ +I'm embarrassed to report that 1.2.7 was also DOA -- maybe I'll skip the + .7 version in each sequence from now on.
+ +Version 1.3.6
+ +-
+
-
+
+
+
If ADD_SNAT_ALIASES=Yes is specified in /etc/shorewall/shorewall.conf, + an error occurs when the firewall script attempts to +add an SNAT alias.
+
+ -
+
+
The logunclean and dropunclean options + cause errors during startup when Shorewall is run with iptables + 1.2.7.
+
+
These problems are fixed in + this correct firewall script which must be installed in + /var/lib/shorewall/ as described above. These problems are also + corrected in version 1.3.7.
+ +Two-interface Samples 1.3.6 (file two-interfaces.tgz)
+ +A line was inadvertently deleted from the "interfaces + file" -- this line should be added back in if the version that you + downloaded is missing it:
+ +net eth0 detect routefilter,dhcp,norfc1918
+ +If you downloaded two-interfaces-a.tgz then the above + line should already be in the file.
+ +Version 1.3.5-1.3.5b
+ +The new 'proxyarp' interface option doesn't work :-( + This is fixed in + this corrected firewall script which must be installed in + /var/lib/shorewall/ as described above.
+ +Versions 1.3.4-1.3.5a
+ +Prior to version 1.3.4, host file entries such as the + following were allowed:
+ +adm eth0:1.2.4.5,eth0:5.6.7.8+
That capability was lost in version 1.3.4 so that it is only + possible to include a single host specification on each line. + This problem is corrected by this + modified 1.3.5a firewall script. Install the script in /var/lib/pub/shorewall/firewall + as instructed above.
+This problem is corrected in version 1.3.5b.
+Version 1.3.5
+ +REDIRECT rules are broken in this version. Install + + this corrected firewall script in /var/lib/pub/shorewall/firewall + as instructed above. This problem is corrected in version + 1.3.5a.
+ +Version 1.3.n, n < 4
+ +The "shorewall start" and "shorewall restart" commands + to not verify that the zones named in the /etc/shorewall/policy +file have been previously defined in the /etc/shorewall/zones +file. The "shorewall check" command does perform this verification +so it's a good idea to run that command after you have made configuration + changes.
+ +Version 1.3.n, n < 3
+ +If you have upgraded from Shorewall 1.2 and after + "Activating rules..." you see the message: "iptables: No chains/target/match + by that name" then you probably have an entry in /etc/shorewall/hosts + that specifies an interface that you didn't include in + /etc/shorewall/interfaces. To correct this problem, you + must add an entry to /etc/shorewall/interfaces. Shorewall 1.3.3 +and later versions produce a clearer error message in this +case.
+ +Version 1.3.2
+ +Until approximately 2130 GMT on 17 June 2002, the + download sites contained an incorrect version of the .lrp file. That + file can be identified by its size (56284 bytes). The correct +version has a size of 38126 bytes.
+ +-
+
- The code to detect a duplicate interface + entry in /etc/shorewall/interfaces contained a typo that prevented + it from working correctly. +
- "NAT_BEFORE_RULES=No" was broken; it behaved + just like "NAT_BEFORE_RULES=Yes". + +
Both problems are corrected in + this script which should be installed in /var/lib/shorewall + as described above.
+ +-
+
-
+
+
+
The IANA have just announced the allocation of subnet + 221.0.0.0/8. This + updated rfc1918 file reflects that allocation.
+
+
+
Version 1.3.1
- +-
-
- TCP SYN packets may be double counted when - LIMIT:BURST is included in a CONTINUE or ACCEPT policy (i.e., - each packet is sent through the limit chain twice). -
- An unnecessary jump to the policy chain -is sometimes generated for a CONTINUE policy. -
- When an option is given for more than one
- interface in /etc/shorewall/interfaces then depending
-on the option, Shorewall may ignore all but the first appearence
-of the option. For example:
-
- net eth0 dhcp
- loc eth1 dhcp
-
- Shorewall will ignore the 'dhcp' on eth1.
- - Update 17 June 2002 - The bug described -in the prior bullet affects the following options: dhcp, - dropunclean, logunclean, norfc1918, routefilter, multi, - filterping and noping. An additional bug has been found +
- TCP SYN packets may be double counted +when LIMIT:BURST is included in a CONTINUE or ACCEPT policy +(i.e., each packet is sent through the limit chain twice). +
- An unnecessary jump to the policy chain + is sometimes generated for a CONTINUE policy. +
- When an option is given for more than
+one interface in /etc/shorewall/interfaces then depending
+ on the option, Shorewall may ignore all but the first
+appearence of the option. For example:
+
+ net eth0 dhcp
+ loc eth1 dhcp
+
+ Shorewall will ignore the 'dhcp' on eth1.
+ - Update 17 June 2002 - The bug described
+ in the prior bullet affects the following options: dhcp,
+ dropunclean, logunclean, norfc1918, routefilter, multi,
+ filterping and noping. An additional bug has been found
that affects only the 'routestopped' option.
-
- Users who downloaded the corrected script prior - to 1850 GMT today should download and install the corrected - script again to ensure that this second problem is corrected.
-
+
+ Users who downloaded the corrected script +prior to 1850 GMT today should download and install +the corrected script again to ensure that this second +problem is corrected. +
These problems are corrected in - this firewall script which should be installed in /etc/shorewall/firewall - as described above.
- + href="http://www.shorewall.net/pub/shorewall/errata/1.3.1/firewall"> + this firewall script which should be installed in /etc/shorewall/firewall + as described above. +Version 1.3.0
- +-
-
- Folks who downloaded 1.3.0 from the links - on the download page before 23:40 GMT, 29 May 2002 may - have downloaded 1.2.13 rather than 1.3.0. The "shorewall - version" command will tell you which version that you -have installed. -
- The documentation NAT.htm file uses non-existent +
- Folks who downloaded 1.3.0 from the links + on the download page before 23:40 GMT, 29 May 2002 may + have downloaded 1.2.13 rather than 1.3.0. The "shorewall + version" command will tell you which version that you + have installed. +
- The documentation NAT.htm file uses non-existent wallpaper and bullet graphic files. The - corrected version is here. - + href="http://www.shorewall.net/pub/shorewall/errata/1.3.0/NAT.htm"> + corrected version is here. +
+ +
Upgrade Issues
- +The upgrade issues have moved to a separate page.
- --
Problem with - iptables version 1.2.3
- -- -- -There are a couple of serious bugs in iptables 1.2.3 that - prevent it from working with Shorewall. Regrettably, RedHat + +
+Problem with + iptables version 1.2.3
+ ++ ++ + +There are a couple of serious bugs in iptables 1.2.3 that + prevent it from working with Shorewall. Regrettably, RedHat released this buggy iptables in RedHat 7.2.
- +I have built a - corrected 1.2.3 rpm which you can download here and I have + href="ftp://ftp.shorewall.net/pub/shorewall/errata/iptables-1.2.3-3.i386.rpm"> + corrected 1.2.3 rpm which you can download here and I have also built an - iptables-1.2.4 rpm which you can download here. If you are currently - running RedHat 7.1, you can install either of these RPMs - before you upgrade to RedHat 7.2.
+ href="ftp://ftp.shorewall.net/pub/shorewall/iptables-1.2.4-1.i386.rpm"> +iptables-1.2.4 rpm which you can download here. If you are currently + running RedHat 7.1, you can install either of these RPMs + before you upgrade to RedHat 7.2. - -Update 11/9/2001: RedHat - has released an iptables-1.2.4 RPM of their own which you can download - from http://www.redhat.com/support/errata/RHSA-2001-144.html. - I have installed this RPM on my firewall and it works + +
Update 11/9/2001: RedHat + has released an iptables-1.2.4 RPM of their own which you can +download from http://www.redhat.com/support/errata/RHSA-2001-144.html. + I have installed this RPM on my firewall and it works fine.
- -If you would like to patch iptables 1.2.3 yourself, - the patches are available for download. This patch - which corrects a problem with parsing of the --log-level specification - while this patch + +
If you would like to patch iptables 1.2.3 yourself, + the patches are available for download. This patch + which corrects a problem with parsing of the --log-level specification + while this patch corrects a problem in handling the TOS target.
- +To install one of the above patches:
- +-
+- cd iptables-1.2.3/extensions
-- patch -p0 < the-patch-file
+- cd iptables-1.2.3/extensions
+- patch -p0 < the-patch-file
+ + +Problems with kernels >= 2.4.18 + and RedHat iptables
+ ++- - -Users who use RedHat iptables RPMs and who upgrade to kernel 2.4.18/19 + may experience the following:
- -Problems with kernels >= 2.4.18 - and RedHat iptables
+-+--Users who use RedHat iptables RPMs and who upgrade to kernel 2.4.18/19 - may experience the following:
- --+# shorewall start-
Processing /etc/shorewall/shorewall.conf ...
Processing /etc/shorewall/params ...
Starting Shorewall...
Loading Modules...
Initializing...
Determining Zones...
Zones: net
Validating interfaces file...
Validating hosts file...
Determining Hosts in Zones...
Net Zone: eth0:0.0.0.0/0
iptables: libiptc/libip4tc.c:380: do_check: Assertion
`h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
Aborted (core dumped)
iptables: libiptc/libip4tc.c:380: do_check: Assertion
`h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
Aborted (core dumped)The RedHat iptables RPM is compiled with debugging enabled but the - user-space debugging code was not updated to reflect recent changes in - the Netfilter 'mangle' table. You can correct the problem by installing - - this iptables RPM. If you are already running a 1.2.5 version - of iptables, you will need to specify the --oldpackage option to + +
The RedHat iptables RPM is compiled with debugging enabled but the + user-space debugging code was not updated to reflect recent changes in + the Netfilter 'mangle' table. You can correct the problem by +installing + this iptables RPM. If you are already running a 1.2.5 version + of iptables, you will need to specify the --oldpackage option to rpm (e.g., "iptables -Uvh --oldpackage iptables-1.2.5-1.i386.rpm").
-
Problems installing/upgrading - RPM on SuSE
- -If you find that rpm complains about a conflict - with kernel <= 2.2 yet you have a 2.4 kernel - installed, simply use the "--nodeps" option to - rpm.
- + +Problems installing/upgrading + RPM on SuSE
+ +If you find that rpm complains about a conflict + with kernel <= 2.2 yet you have a 2.4 kernel + installed, simply use the "--nodeps" option to + rpm.
+Installing: rpm -ivh --nodeps <shorewall rpm>
- +Upgrading: rpm -Uvh --nodeps <shorewall rpm>
- -Problems with - iptables version 1.2.7 and MULTIPORT=Yes
- -The iptables 1.2.7 release of iptables has made - an incompatible change to the syntax used to - specify multiport match rules; as a consequence, - if you install iptables 1.2.7 you must be running - Shorewall 1.3.7a or later or:
- + +Problems with + iptables version 1.2.7 and MULTIPORT=Yes
+ +The iptables 1.2.7 release of iptables has made + an incompatible change to the syntax used to + specify multiport match rules; as a consequence, + if you install iptables 1.2.7 you must be running + Shorewall 1.3.7a or later or:
+-
-
- set MULTIPORT=No in - /etc/shorewall/shorewall.conf; or -
- if you are running -Shorewall 1.3.6 you may install - - this firewall script in /var/lib/shorewall/firewall - as described above. - +
- set MULTIPORT=No in + /etc/shorewall/shorewall.conf; or +
- if you are running +Shorewall 1.3.6 you may install + + this firewall script in /var/lib/shorewall/firewall + as described above. +
Problems with RH Kernel 2.4.18-10 and NAT
-
- /etc/shorewall/nat entries of the following form will result
-in Shorewall being unable to start:-
- + + /etc/shorewall/nat entries of the following form will result + in Shorewall being unable to start:
+
+
#EXTERNAL INTERFACE INTERNAL ALL INTERFACES LOCAL- Error message is:
192.0.2.22 eth0 192.168.9.22 yes yes
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE
- + Error message is:
+
Setting up NAT...- The solution is to put "no" in the LOCAL column. Kernel support - for LOCAL=yes has never worked properly and 2.4.18-10 has disabled -it. The 2.4.19 kernel contains corrected support under a new kernel -configuraiton option; see http://www.shorewall.net/Documentation.htm#NAT
iptables: Invalid argument
Terminated
- -
Last updated 1/25/2003 - - Tom Eastep
- + The solution is to put "no" in the LOCAL column. Kernel support + for LOCAL=yes has never worked properly and 2.4.18-10 has disabled it. + The 2.4.19 kernel contains corrected support under a new kernel configuraiton + option; see http://www.shorewall.net/Documentation.htm#NAT+ +
Last updated 2/8/2003 - + Tom Eastep
+Copyright © 2001, 2002, 2003 Thomas M. Eastep.
-
diff --git a/Shorewall-docs/mailing_list.htm b/Shorewall-docs/mailing_list.htm index 67e3fafd6..8fd3276af 100644 --- a/Shorewall-docs/mailing_list.htm +++ b/Shorewall-docs/mailing_list.htm @@ -2,151 +2,152 @@ - + - + - + - +
| + | ||||
-
+
+
- |
- - + | +
+
Shorewall Mailing Lists- |
- + | 
- - + + - - + + + - - Powered by Postfix - |
-
- 
- 
- Not getting List Mail? -- Check Here
- -If you experience problems with any of these lists, please + +
If you experience problems with any of these lists, please let me know
- +Not able to Post Mail to shorewall.net?
- -You can report such problems by sending mail to tom dot eastep - at hp dot com.
- + +You can report such problems by sending mail to tom dot eastep + at hp dot com.
+A Word about SPAM Filters
- -Before subscribing please read my policy
- about list traffic that bounces. Also please note that the mail server
- at shorewall.net checks incoming mail:
-
Before subscribing please read my policy
+ about list traffic that bounces. Also please note that the mail server
+ at shorewall.net checks incoming mail:
+
-
-
- against Spamassassin
- (including Vipul's Razor).
-
- - to ensure that the sender address is fully qualified. -
- to verify that the sender's domain has an A or MX record - in DNS. -
- to ensure that the host name in the HELO/EHLO command +
- against Spamassassin
+ (including Vipul's Razor).
+
+ - to ensure that the sender address is fully qualified. +
- to verify that the sender's domain has an A or MX record + in DNS. +
- to ensure that the host name in the HELO/EHLO command is a valid fully-qualified DNS name that resolves. - +
Please post in plain text
- A growing number of MTAs serving list subscribers are rejecting -all HTML traffic. At least one MTA has gone so far as to blacklist shorewall.net - "for continuous abuse" because it has been my policy to allow HTML in -list posts!!-
- I think that blocking all HTML is a Draconian way to control spam - and that the ultimate losers here are not the spammers but the list subscribers - whose MTAs are bouncing all shorewall.net mail. As one list subscriber - wrote to me privately "These e-mail admin's need to get a (explitive -deleted) life instead of trying to rid the planet of HTML based e-mail". -Nevertheless, to allow subscribers to receive list posts as must as possible, -I have now configured the list server at shorewall.net to strip all HTML -from outgoing posts. This means that HTML-only posts will be bounced by the -list server.
- -
Note: The list server limits posts to 120kb.
-
+
+ I think that blocking all HTML is a Draconian way to control spam + and that the ultimate losers here are not the spammers but the list subscribers + whose MTAs are bouncing all shorewall.net mail. As one list subscriber + wrote to me privately "These e-mail admin's need to get a (explitive + deleted) life instead of trying to rid the planet of HTML based e-mail". + Nevertheless, to allow subscribers to receive list posts as must as possible, + I have now configured the list server at shorewall.net to strip all HTML + from outgoing posts. This means that HTML-only posts will be bounced by +the list server.
+
Note: The list server limits posts to 120kb.
+
Other Mail Delivery Problems
- If you find that you are missing an occasional list post, your e-mail - admin may be blocking mail whose Received: headers contain the -names of certain ISPs. Again, I believe that such policies hurt more than -they help but I'm not prepared to go so far as to start stripping Received: - headers to circumvent those policies.- + If you find that you are missing an occasional list post, your e-mail + admin may be blocking mail whose Received: headers contain the names + of certain ISPs. Again, I believe that such policies hurt more than they + help but I'm not prepared to go so far as to start stripping Received: + headers to circumvent those policies.
+
Mailing Lists Archive Search
- - + +Please do not try to download the entire
+Archive -- it is 75MB (and growing daily) and my slow DSL line simply won't
+stand the traffic. If I catch you, you will be blacklisted.
+
+
Shorewall CA Certificate
- If you want to trust X.509 certificates issued by Shoreline + If you want to trust X.509 certificates issued by Shoreline Firewall (such as the one used on my web site), you may download and install my CA certificate - in your browser. If you don't wish to trust my certificates then you - can either use unencrypted access when subscribing to Shorewall mailing - lists or you can use secure access (SSL) and accept the server's certificate - when prompted by your browser.- + href="Shorewall_CA_html.html">download and install my CA certificate + in your browser. If you don't wish to trust my certificates then +you can either use unencrypted access when subscribing to Shorewall +mailing lists or you can use secure access (SSL) and accept the server's +certificate when prompted by your browser.
+
Shorewall Users Mailing List
- -The Shorewall Users Mailing list provides a way for users - to get answers to questions and to report problems. Information of - general interest to the Shorewall user community is also posted to - this list.
- -Before posting a problem report to this list, please see - the problem reporting -guidelines.
- -To subscribe to the mailing list:
-
-
-
- Insecure: http://lists.shorewall.net/mailman/listinfo/shorewall-users -
- SSL: https//lists.shorewall.net/mailman/listinfo/shorewall-users - -
To post to the list, post to shorewall-users@lists.shorewall.net.
- -The list archives are at http://lists.shorewall.net/pipermail/shorewall-users.
- -Note that prior to 1/1/2002, the mailing list was hosted at -Sourceforge. The archives from that list -may be found at www.geocrawler.com/lists/3/Sourceforge/9327/0/.
- -Shorewall Announce Mailing List
- -This list is for announcements of general interest to the
- Shorewall community. To subscribe:
-
-
-
- Insecure: http://lists.shorewall.net/mailman/listinfo/shorewall-announce -
- SSL: https//lists.shorewall.net/mailman/listinfo/shorewall-announce. - -
- The list archives are at http://lists.shorewall.net/pipermail/shorewall-announce.
Shorewall Development Mailing List
- -The Shorewall Development Mailing list provides a forum for - the exchange of ideas about the future of Shorewall and for coordinating - ongoing Shorewall Development.
- + +The Shorewall Users Mailing list provides a way for users + to get answers to questions and to report problems. Information +of general interest to the Shorewall user community is also posted +to this list.
+ +Before posting a problem report to this list, please see + the problem reporting + guidelines.
+To subscribe to the mailing list:
-
-
- Insecure: Insecure: http://lists.shorewall.net/mailman/listinfo/shorewall-users +
- SSL: https//lists.shorewall.net/mailman/listinfo/shorewall-users + +
To post to the list, post to shorewall-users@lists.shorewall.net.
+ +The list archives are at http://lists.shorewall.net/pipermail/shorewall-users.
+ +Note that prior to 1/1/2002, the mailing list was hosted +at Sourceforge. The archives from that +list may be found at www.geocrawler.com/lists/3/Sourceforge/9327/0/.
+ +Shorewall Announce Mailing List
+ +This list is for announcements of general interest to the
+ Shorewall community. To subscribe:
+
-
+
- Insecure: http://lists.shorewall.net/mailman/listinfo/shorewall-announce +
- SSL: https//lists.shorewall.net/mailman/listinfo/shorewall-announce. + +
+ The list archives are at http://lists.shorewall.net/pipermail/shorewall-announce.
Shorewall Development Mailing List
+ +The Shorewall Development Mailing list provides a forum for + the exchange of ideas about the future of Shorewall and for coordinating + ongoing Shorewall Development.
+ +To subscribe to the mailing list:
+
-
+
- Insecure: http://lists.shorewall.net/mailman/listinfo/shorewall-devel -
- SSL: SSL: https//lists.shorewall.net/mailman/listinfo/shorewall-devel. - +
To post to the list, post to shorewall-devel@lists.shorewall.net.
- +The list archives are at http://lists.shorewall.net/pipermail/shorewall-devel.
- -How to Unsubscribe from one of - the Mailing Lists
- -There seems to be near-universal confusion about unsubscribing - from Mailman-managed lists although Mailman 2.1 has attempted to - make this less confusing. To unsubscribe:
- + +How to Unsubscribe from one of + the Mailing Lists
+ +There seems to be near-universal confusion about unsubscribing + from Mailman-managed lists although Mailman 2.1 has attempted +to make this less confusing. To unsubscribe:
+-
-
-
-
-
Follow the same link above that you used to subscribe - to the list.
-
- -
-
-
Down at the bottom of that page is the following text: - " To unsubscribe from <list name>, get a password - reminder, or change your subscription options enter your subscription - email address:". Enter your email address in the box and click - on the "Unsubscribe or edit options" button.
-
- -
-
-
There will now be a box where you can enter your password - and click on "Unsubscribe"; if you have forgotten your password, - there is another button that will cause your password to be emailed - to you.
-
-
+ -
+
+
Follow the same link above that you used to subscribe + to the list.
+
+ -
+
+
Down at the bottom of that page is the following text: + " To unsubscribe from <list name>, get a password + reminder, or change your subscription options enter your subscription + email address:". Enter your email address in the box and click + on the "Unsubscribe or edit options" button.
+
+ -
+
+
There will now be a box where you can enter your password + and click on "Unsubscribe"; if you have forgotten your password, + there is another button that will cause your password to be emailed + to you.
+
+
+ +
Frustrated by having to Rebuild Mailman to use it with Postfix?
- + - +Last updated 2/3/2003 - Tom Eastep
- - Copyright
-© 2001, 2002, 2003 Thomas M. Eastep.
-
Copyright ©
+2001, 2002, 2003 Thomas M. Eastep.
+
diff --git a/Shorewall-docs/ports.htm b/Shorewall-docs/ports.htm index 4e9c2b71a..4912c722f 100644 --- a/Shorewall-docs/ports.htm +++ b/Shorewall-docs/ports.htm @@ -1,194 +1,203 @@ - +
- Ports required for Various
+
+
+ |
- Ports required for Various Services/Applications- |
+
In addition to those applications described in the /etc/shorewall/rules documentation, here - are some other services/applications that you may need to configure your + href="Documentation.htm">the /etc/shorewall/rules documentation, here + are some other services/applications that you may need to configure your firewall to accommodate.
- +NTP (Network Time Protocol)
- -+ ++- +UDP Port 123
-
rdate
- --+TCP Port 37
-
++TCP Port 37
+
UseNet (NNTP)
- -+ ++- +TCP Port 119
-
DNS
- --- + +UDP Port 53. If you are configuring a DNS client, you will probably -want to open TCP Port 53 as well.
-
- If you are configuring a server, only open TCP Port 53 if you will return - long replies to queries or if you need to enable ZONE transfers. In the - latter case, be sure that your server is properly configured.
++UDP Port 53. If you are configuring a DNS client, you will probably want +to open TCP Port 53 as well.
+
+ If you are configuring a server, only open TCP Port 53 if you will +return long replies to queries or if you need to enable ZONE transfers. In +the latter case, be sure that your server is properly configured.
ICQ
- --+UDP Port 4000. You will also need to open a range of TCP ports which + +
+- +UDP Port 4000. You will also need to open a range of TCP ports which you can specify to your ICQ client. By default, clients use 4000-4100.
-
PPTP
- -+ ++- -Protocol 47 (NOT port 47) and TCP Port 1723 (Lots more information here).
-IPSEC
- --- -Protocols 50 and 51 (NOT ports 50 and 51) and UDP Port - 500. These should be opened in both directions (Lots more information - here and here).
-SMTP
- --- -TCP Port 25.
-POP3
- --- -TCP Port 110.
-TELNET
- --- -TCP Port 23.
-SSH
- --- -TCP Port 22.
-Auth (identd)
- --- -TCP Port 113
-Web Access
- --+TCP Ports 80 and 443.
-
IPSEC
+ +++ +Protocols 50 and 51 (NOT ports 50 and 51) and UDP Port + 500. These should be opened in both directions (Lots more information + here and here).
+
SMTP
+ +++ +TCP Port 25.
+
POP3
+ +++ +TCP Port 110.
+
TELNET
+ +++ +TCP Port 23.
+
SSH
+ +++ +TCP Port 22.
+
Auth (identd)
+ +++ +TCP Port 113
+
Web Access
+ +++TCP Ports 80 and 443.
+
FTP
- -+ +++Server configuration is covered on in the /etc/shorewall/rules documentation,
+ +For a client, you must open outbound TCP port 21 and be sure that your + kernel is compiled to support FTP connection tracking. If you build this + support as a module, Shorewall will automatically load the module from + /var/lib/<kernel version>/kernel/net/ipv4/netfilter.
-
+For a client, you must open outbound TCP port 21 and be sure that your - kernel is compiled to support FTP connection tracking. If you build this - support as a module, Shorewall will automatically load the module from - /var/lib/<kernel version>/kernel/net/ipv4/netfilter.
- -
-If you run an FTP server on a nonstandard port or you need to access -such a server, then you must specify that port in /etc/shorewall/modules. -For example, if you run an FTP server that listens on port 49 then you would -have:
- -
-++ +If you run an FTP server on a nonstandard port or you need to access + such a server, then you must specify that port in /etc/shorewall/modules. + For example, if you run an FTP server that listens on port 49 then you would + have:
+ +
++ loadmodule ip_nat_ftp ports=21,49loadmodule ip_conntrack_ftp ports=21,49
-
- loadmodule ip_nat_ftp ports=21,49
-
+ +Note that you MUST include port 21 in the ports list or you may + have problems accessing regular FTP servers.
-Note that you MUST include port 21 in the ports list or you may -have problems accessing regular FTP servers.
- -If there is a possibility that these modules might be loaded before -Shorewall starts, then you should include the port list in /etc/modules.conf:
- -
-+- + options ip_nat_ftp ports=21,49If there is a possibility that these modules might be loaded before Shorewall +starts, then you should include the port list in /etc/modules.conf:
+ +
+-options ip_conntrack_ftp ports=21,49
-
- options ip_nat_ftp ports=21,49
-
+ +
SMB/NMB (Samba/Windows Browsing/File Sharing)
- +- -
+ ++- + UDP Ports 137-139.TCP Ports 137, 139 and 445.
-
- UDP Ports 137-139.
-
- Also, see this page.
+
+ Also, see this page. +
Traceroute
- -+ ++ ++UDP ports 33434 through 33434+<max number of hops>-1
-
NFS
+
+-I personally use the following rules for opening access from zone z1 +to a server with IP address a.b.c.d in zone z2:
+
+ACCEPT z1 z2:a.b.c.d udp 111+
ACCEPT z1 z2:a.b.c.d udp 2049
ACCEPT z1 z2:a.b.c.d udp 32700:
NFS
- --- -There's some good information at +
Note that my rules only cover NFS using UDP (the normal case). There +is lots of additional information at http://nfs.sourceforge.net/nfs-howto/security.html
-
Didn't find what you are looking for -- have you looked in your own -/etc/services file?
- + + +Didn't find what you are looking for -- have you looked in your own /etc/services +file?
+Still looking? Try http://www.networkice.com/advice/Exploits/Ports
- -Last updated 11/10/2002 - Last updated 2/7/2003 - Tom Eastep
- Copyright - © 2001, 2002 Thomas M. Eastep.+ Copyright © 2001, 2002, 2003 Thomas M. Eastep.
+
diff --git a/Shorewall-docs/seattlefirewall_index.htm b/Shorewall-docs/seattlefirewall_index.htm index b205364d3..5e0a09cab 100644 --- a/Shorewall-docs/seattlefirewall_index.htm +++ b/Shorewall-docs/seattlefirewall_index.htm @@ -5,7 +5,8 @@ - + +
| + |
@@ -37,15 +39,15 @@
-
+
+ Shorewall
+ 1.3 - "iptables
+ made easy"
@@ -54,50 +56,51 @@ made easy"
-
+
+
+
+ |
+
+
|
+
- - |
-
-
-
-
-
-
-
-
-
-
What is it?@@ -108,11 +111,12 @@ made 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 - gateway/router/server or on a standalone GNU/Linux system. + + +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 + gateway/router/server or on a standalone GNU/Linux system. @@ -122,27 +126,29 @@ made 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 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. + + 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 @@ -152,7 +158,8 @@ the GNU General Public License along with - + + Copyright 2001, 2002, 2003 Thomas M. Eastep @@ -164,30 +171,30 @@ the GNU General Public License along with - + Congratulations to Jacques and Eric on the recent release of Bering
-1.0 Final!!! 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)+ +This is a mirror of the main Shorewall web site at SourceForge +(http://shorewall.sf.net)@@ -200,7 +207,7 @@ the GNU General Public License along with - +News@@ -211,7 +218,8 @@ the GNU General Public License along with - + + @@ -219,456 +227,117 @@ the GNU General Public License along with - -2/4/2003 - Shorewall 1.3.14-RC1 Includes the Beta 2 content plus support for OpenVPN tunnels. - - The release candidate may be downloaded from: http://www.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) - - The beta may be downloaded from: http://www.shorewall.net/pub/shorewall/Beta- - 1/25/2003 - Shorewall 1.3.14-Beta1 The Beta includes the following changes: New features include +
- - http://www.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:
1/6/2003 - BURNOUT - - - -Until further notice, I will not be involved in either Shorewall - 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 - - - - ftp://slovakia.shorewall.net/mirror/shorewall/pdf/ 12/27/2002 - Shorewall 1.3.12 Released - - - - Features include:
12/20/2002 - Shorewall 1.3.12 Beta 3 - - - You may download the Beta from: http://www.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: - - - - -
- - - - http://www.shorewall.net/pub/shorewall/Beta- - - - 12/12/2002 - Mandrake Multi Network Firewall - - - - 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. - - - -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 - - - - ++ + 2/5/2003 - Shorewall Support included in Webmin 1.060
+ 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. - - - - -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 - - - - - ftp://slovakia.shorewall.net/mirror/shorewall/pdf/ 11/24/2002 - Shorewall 1.3.11 - - - - - -In this version: - - - - ++ + +
|
+
- M | -
| + |
@@ -722,12 +391,12 @@ command is now compatible with bash clones such as ash and dash. 
-
+
@@ -737,34 +406,30 @@ command is now compatible with bash clones such as ash and dash.Shorewall is free but
-if you try it and find it useful, please consider making a donation
- to Starlight Children's
-Foundation. Thanks!
+
+ Shorewall is free +but if you try it and find it useful, please consider making a donation + to Starlight +Children's Foundation. Thanks! - |
+
-
Updated 2/4/2003 - Tom Eastep - + +
Updated 2/7/2003 - Tom Eastep
+
-
-
-
-
+ diff --git a/Shorewall-docs/shorewall_features.htm b/Shorewall-docs/shorewall_features.htm index f60d7486c..ec305966e 100644 --- a/Shorewall-docs/shorewall_features.htm +++ b/Shorewall-docs/shorewall_features.htm @@ -1,114 +1,118 @@ - + - + - + - +
| + |
Shorewall Features- |
-
-
-
- Uses Netfilter's connection tracking facilities for stateful packet - filtering. -
- Can be used in a wide range of router/firewall/gateway applications.
-
-
-
-
- Completely customizable using configuration files. -
- No limit on the number of network interfaces. -
- Allows you to partitions the network into zones and gives you complete - control over the connections permitted between each pair of zones. -
- Multiple interfaces per zone and multiple zones per interface - permitted. -
- Supports nested and overlapping zones. - -
- - QuickStart Guides (HOWTOs) -to help get your first firewall up and running quickly -
- Extensive documentation - included in the .tgz and .rpm downloads. -
- Flexible address management/routing support (and you can
-use all types in the same firewall):
-
-
-
- Masquerading/SNAT -
- Port Forwarding (DNAT). -
- Static NAT. -
- Proxy ARP. -
- Simple host/subnet Routing - -
- - Blacklisting of individual - IP addresses and subnetworks is supported. -
- Operational support:
-
-
-
-
- Commands to start, stop and clear the firewall -
- Supports status monitoring with an audible alarm - when an "interesting" packet is detected. -
- Wide variety of informational commands. - -
- - VPN Support
-
-
-
- IPSEC, GRE, IPIP and -OpenVPN Tunnels. -
- PPTP clients and Servers. - -
- - Support for Traffic Control/Shaping - integration. -
- Wide support for different GNU/Linux Distributions.
+
-
+
- Uses Netfilter's connection tracking facilities for stateful packet + filtering. +
- Can be used in a wide range of router/firewall/gateway applications.
+
-
-
- RPM and Debian - packages available. -
- Includes automated install, upgrade, -fallback and uninstall facilities for users who can't use -or choose not to use the RPM or Debian packages. -
- Included as a standard part of LEAF/Bering (router/firewall -on a floppy, CD or compact flash). - +
- Completely customizable using configuration files. +
- No limit on the number of network interfaces. +
- Allows you to partitions the network into zones and gives you complete + control over the connections permitted between each pair of zones. +
- Multiple interfaces per zone and multiple zones per interface + permitted. +
- Supports nested and overlapping zones. + +
+ - QuickStart Guides (HOWTOs) +to help get your first firewall up and running quickly +
- A GUI is available via Webmin 1.060 and later (http://www.webmin.com)
+
+ - Extensive documentation + included in the .tgz and .rpm downloads. +
- Flexible address management/routing support (and you can
+use all types in the same firewall):
+
-
+
- Masquerading/SNAT +
- Port Forwarding (DNAT). +
- Static NAT. +
- Proxy ARP. +
- Simple host/subnet Routing + +
+ - Blacklisting of individual + IP addresses and subnetworks is supported. +
- Operational support:
+
+
-
+
- Commands to start, stop and clear the firewall +
- Supports status monitoring with an audible alarm + when an "interesting" packet is detected. +
- Wide variety of informational commands. + +
+ - VPN Support
+
-
+
- IPSEC, GRE, IPIP and +OpenVPN Tunnels. +
- PPTP clients and Servers. + +
+ - Support for Traffic Control/Shaping + integration. +
- Wide support for different GNU/Linux Distributions.
+
+
-
+
- RPM and Debian + packages available. +
- Includes automated install, upgrade, +fallback and uninstall facilities for users who can't use +or choose not to use the RPM or Debian packages. +
- Included as a standard part of LEAF/Bering (router/firewall + on a floppy, CD or compact flash). +
- - Media Access Control (MAC) Address
- Verification
-
-
+ - Media Access Control (MAC)
+Address Verification
+
+
+
Last updated 1/31/2003 - Tom Eastep
- + +Last updated 2/5/2003 - Tom Eastep
+Copyright © 2001-2003 Thomas M. Eastep.
+ +
-
diff --git a/Shorewall-docs/sourceforge_index.htm b/Shorewall-docs/sourceforge_index.htm index 1bf7bb132..f1733f3f1 100644 --- a/Shorewall-docs/sourceforge_index.htm +++ b/Shorewall-docs/sourceforge_index.htm @@ -6,7 +6,7 @@ - +Shoreline Firewall (Shorewall) 1.3 @@ -15,22 +15,22 @@ -+ - + - + -
- -+ - + + + - - - - - - - - - + ++ @@ -39,16 +39,17 @@ - + + +
+ Shorewall + 1.3 - "iptables + made easy" + @@ -58,34 +59,34 @@ + + +
- Shorewall
- 1.3 - "iptables
- made easy"
- - -+ + + + +- + + + ++ +- - - - -+ - -- + -
- -+ - - - - - - - - - -+ @@ -95,7 +96,7 @@ - + - -What is it?
@@ -107,11 +108,12 @@ - -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 - gateway/router/server or on a standalone GNU/Linux system.
+ + +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 + gateway/router/server or on a standalone GNU/Linux system.
@@ -122,29 +124,30 @@ - -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 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, USA
+ + 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 @@ -155,7 +158,8 @@ MA 02139, USA - + +Copyright 2001, 2002, 2003 Thomas M. Eastep
@@ -167,22 +171,24 @@ MA 02139, USA - + +
- Congratulations to Jacques and -Eric on the recent release of Bering 1.0 Final!!!
- 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
- + 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!!!
+ - + +News
@@ -196,46 +202,17 @@ Eric on the recent release of Bering 1.0 Final!!!
- -2/4/2003 - Shorewall 1.3.14-RC1
- -2/8/2003 - Shoreawll 1.3.14
- Includes the Beta 2 content plus support for OpenVPN tunnels.
-
-The release candidate may be downloaded from:
- -
-http://www.shorewall.net/pub/shorewall/Beta
- - -
-ftp://ftp.shorewall.net/pub/shorewall/Beta1/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)
- -The beta may be downloaded from:
- -
-http://www.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:
- + + +
-New features include
+-
-
- 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 +
- 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 @@ -244,18 +221,25 @@ in shorewall.conf and the 'noping' and 'filterping' options in /etc/shorewall/ 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:
+ - 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:
+ - Support for OpenVPN Tunnels.
+
+
+ - Support for VLAN devices with names of the form $DEV.$VID (e.g.,
+eth0.0)
+
+
+ - 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.
@@ -266,11 +250,11 @@ traffic from:
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 @@ -283,393 +267,44 @@ on subnetworks that you don't wish to masquerade.
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]#[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?
- +[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
- In this case, you would want to change the entry in /etc/shorewall/masq + +
192.168.1.0/24 scope link
192.168.10.0/24 proto kernel scope link src 192.168.10.254
[root@gateway test]#[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:
- +#INTERFACE SUBNET ADDRESS
-
eth0 192.168.1.0/24 206.124.146.176
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE
-
+
- -http://www.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. - -
1/6/2003 - BURNOUT -
- - -Until further notice, I will not be involved in either Shorewall - 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
- - -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 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. -
- 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.
-
- - -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 only 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. - - - -
- - - -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 MandrakeSofts'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.
- - - -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.
- - - - -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
- - - - -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 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 - - - - -
11/14/2002 - Shorewall Documentation in PDF Format -
- - - - -Juraj Ontkanin has produced a PDF containing the Shorewall 1.3.10 - documenation. the PDF may be downloaded from
- - - - -ftp://slovakia.shorewall.net/mirror/shorewall/pdf/
- - - - + +
- http://slovakia.shorewall.net/pub/shorewall/pdf/
-2/5/2003 - Shorewall Support included in Webmin 1.060 +
+ Webmin version 1.060 now has Shorewall support included as standard. +See http://www.webmin.com +
+ - + + + + + +
-
@@ -677,93 +312,8 @@ command is now compatible with bash clones such as ash and dash.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - - - - -
- - - - - --
- - - - - -This site is hosted by the generous folks at SourceForge.net
- - - - -Donations
- - -
-- - - -
+ +- - + + + + + + + + +- - + @@ -771,11 +321,99 @@ command is now compatible with bash clones such as ash and dash.More News + + + + + + + + + + + + + + +
+ + + + + +
+ + + + + +
+ + + + + +This site is hosted by the generous folks at SourceForge.net
+ + + + + + +Donations
+ + +
++ + + +
- -+ + + - - - + + ++ + + + + + + + + + @@ -786,34 +424,32 @@ command is now compatible with bash clones such as ash and dash.Shorewall is free -but if you try it and find it useful, please consider making a donation - to Starlight -Children's Foundation. Thanks! + + + -Shorewall is free but +if you try it and find it useful, please consider making a donation + to Starlight Children's +Foundation. Thanks!
-Updated 2/4/2003 - Tom Eastep - -
-
-
-
-
+ + +Updated 2/7/2003 - Tom Eastep + +
diff --git a/Shorewall-docs/support.htm b/Shorewall-docs/support.htm index eeb5f6dc0..8e6c88b57 100644 --- a/Shorewall-docs/support.htm +++ b/Shorewall-docs/support.htm @@ -2,121 +2,128 @@ - + - + - + - +
+Support - + - +- -
- +- ++ + + + + - - + +- + + -Shorewall Support
-
- While I don't answer Shorewall questions -emailed directly to me, I try to spend some time each day answering questions -on the Shorewall Users Mailing List.
- +-Tom Eastep
- +Before Reporting a Problem
- There are a number of sources for problem - solution information. Please try these before you post. - +"Well at least you tried to read the documentation, which is a lot more +than some people on this list appear to do."
+
+- Wietse Venema - On the Postfix mailing list+
+
+ There are a number of sources for +problem solution information. Please try these before you post. +
- +
- +-
-
- More than half of the questions posted on the support
-list have answers directly accessible from the More than half of the questions posted on the support
+ list have answers directly accessible from the Documentation Index
-
-
- - The FAQ - has solutions to more than 20 common problems. - +
+
+ - The FAQ + has solutions to more than 20 common problems. +
- +
-
-
- The The Troubleshooting Information contains - a number of tips to help you solve common problems. - + a number of tips to help you solve common problems. +
- + - +
- +
-
-
- The Mailing List Archives - search facility can locate posts about similar problems: - - +
- The Mailing List +Archives search facility can locate posts about similar problems: + +
- +
Mailing List Archive Search
- + - + +Problem Reporting Guidelines
- "Let me see if I can translate your message into a real-world - example. It would be like saying that you have three rooms at home, - and when you walk into one of the rooms, you detect this strange smell. - Can anyone tell you what that strange smell is?-
- Now, all of us could do some wonderful guessing as to the smell - and even what's causing it. You would be absolutely amazed at the -range and variety of smells we could come up with. Even more amazing -is that all of the explanations for the smells would be completely + "Let me see if I can translate your message into a real-world + example. It would be like saying that you have three rooms at home, + and when you walk into one of the rooms, you detect this strange smell. + Can anyone tell you what that strange smell is?
+
+ Now, all of us could do some wonderful guessing as to the +smell and even what's causing it. You would be absolutely amazed +at the range and variety of smells we could come up with. Even more +amazing is that all of the explanations for the smells would be completely plausible."
-
- -
-
- -
- -
-
-
- Please remember we only know what is posted in your message.
- Do not leave out any information that appears to be correct, or was mentioned
- in a previous post. There have been countless posts by people who were
- sure that some part of their configuration was correct when it actually
- contained a small error. We tend to be skeptics where detail is lacking.
-
-
- - Please keep in mind that you're asking for free
- technical support. Any help we offer is an act of generosity, not an obligation.
- Try to make it easy for us to help you. Follow good, courteous practices
- in writing and formatting your e-mail. Provide details that we need if
-you expect good answers. Exact quoting of error messages, log
-entries, command output, and other output is better than a paraphrase or
-summary.
-
-
- - Please don't describe your
- environment and then ask us to send you custom configuration
- files. We're here to answer your questions but we can't
- do your job for you.
-
-
- - When reporting a problem, ALWAYS include this - information: - -
-
-
-
- the exact version of Shorewall you are running.
-
- shorewall version
-
-
-
- - the exact kernel version you are running
-
- uname -a
-
-
-
- - the complete, exact output of
-
- ip addr show
-
-
-
- - the complete, exact output of
-
- ip route show
-
-
-
- - If your kernel is modularized, the exact output from
-
- lsmod
-
-
- - the exact wording of any
pingfailure responses.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NEVER include the output of "iptables -L". Instead, if you are having connection
-problems please post the exact output of
-
- /sbin/shorewall status
-
- Since that command generates a lot of output, we suggest - that you redirect the output to a file and attach the file to your post
-
- /sbin/shorewall status > /tmp/status.txt
-
-
- - As a general matter, please do not edit the diagnostic - information in an attempt to conceal your IP address, netmask, - nameserver addresses, domain name, etc. These aren't secrets, and concealing - them often misleads us (and 80% of the time, a hacker could derive them -anyway from information contained in the SMTP headers of your post). - -
-
-
-
- -
-
-
-
- -
-
-
- Do you see any "Shorewall"
- messages ("/sbin/shorewall show log")
- when you exercise the function that is giving you problems? If
-so, include the message(s) in your post along with a copy of your /etc/shorewall/interfaces
- file.
-
-
- - Please include any of the Shorewall configuration files -(especially the /etc/shorewall/hosts file if you have modified - that file) that you think are relevant. If you include /etc/shorewall/rules, - please include /etc/shorewall/policy as well (rules are meaningless unless - one also knows the policies). - -
- -
-
-
-
- -
-
-
- If an error occurs when - you try to "shorewall start", - include a trace (See the Troubleshooting - section for instructions). - -
- -
-
-
-
-
-
The list server limits posts to 120kb so don't post GIFs of - your network layout, etc. to the Mailing List -- your - post will be rejected.
-
-
-
- -
Please post in plain text
- -- A growing number of MTAs serving list subscribers are rejecting -all HTML traffic. At least one MTA has gone so far as to blacklist shorewall.net - "for continuous abuse" because it has been my policy to allow HTML in list - posts!!
-
- I think that blocking all HTML is a Draconian way to control -spam and that the ultimate losers here are not the spammers but the list -subscribers whose MTAs are bouncing all shorewall.net mail. As one list -subscriber wrote to me privately "These e-mail admin's need to get a (expletive - deleted) life instead of trying to rid the planet of HTML based e-mail". - Nevertheless, to allow subscribers to receive list posts as must as possible, - I have now configured the list server at shorewall.net to strip all HTML - from outgoing posts.
+
+
+
+ +
+ +
-
+
- Please remember we only know what is posted in your message.
+ Do not leave out any information that appears to be correct, or was mentioned
+ in a previous post. There have been countless posts by people who were
+ sure that some part of their configuration was correct when it actually
+ contained a small error. We tend to be skeptics where detail is lacking.
+
+
+ - Please keep in mind that you're asking for free
+ technical support. Any help we offer is an act of generosity, not an obligation.
+ Try to make it easy for us to help you. Follow good, courteous practices
+ in writing and formatting your e-mail. Provide details that we need if
+ you expect good answers. Exact quoting of error messages, log
+ entries, command output, and other output is better than a paraphrase or
+ summary.
+
+
+ - Please don't describe your
+ environment and then ask us to send you custom configuration
+ files. We're here to answer your questions but we can't
+ do your job for you.
+
+
+ - When reporting a problem, ALWAYS include +this information: + +
-
+
+
- the exact version of Shorewall you are running.
+
+ shorewall version
+
+
+
+ - the exact kernel version you are running
+
+ uname -a
+
+
+
+ - the complete, exact output of
+
+ ip addr show
+
+
+
+ - the complete, exact output of
+
+ ip route show
+
+
+
+ - If your kernel is modularized, the exact output from
+
+ lsmod
+
+
+ - the exact wording of any
pingfailure responses
+
+
+ - If you installed Shorewall using one of the QuickStart Guides, please
+indicate which one.
+
+
+ - If you are running Shorewall under Mandrake using the Mandrake
+installation of Shorewall, please say so.
+
+
+
+
-
+
-
+
-
+
-
+
-
+
-
+
- NEVER include the output of "iptables -L". Instead, if you are having connection
+ problems of any kind, post the exact output of
+
+ /sbin/shorewall status
+
+ Since that command generates a lot of output, we +suggest that you redirect the output to a file and attach the file to +your post
+
+ /sbin/shorewall status > /tmp/status.txt
+
+
+ - As a general matter, please do not edit the diagnostic + information in an attempt to conceal your IP address, netmask, + nameserver addresses, domain name, etc. These aren't secrets, and concealing + them often misleads us (and 80% of the time, a hacker could derive them + anyway from information contained in the SMTP headers of your post). + +
-
+
+
+ +
-
+
+
+ +
-
+
- Do you see any "Shorewall"
+ messages ("/sbin/shorewall show log")
+ when you exercise the function that is giving you problems? If
+ so, include the message(s) in your post along with a copy of your /etc/shorewall/interfaces
+ file.
+
+
+ - Please include any of the Shorewall configuration files + (especially the /etc/shorewall/hosts file if you have modified + that file) that you think are relevant. If you include /etc/shorewall/rules, + please include /etc/shorewall/policy as well (rules are meaningless unless + one also knows the policies). + +
+ +
-
+
+
+ +
-
+
- If an error occurs +when you try to "shorewall start", + include a trace (See the Troubleshooting + section for instructions). + +
+ +
-
+
-
+
+
The list server limits posts to 120kb so don't post GIFs of + your network layout, etc. to the Mailing List -- your + post will be rejected.
+
+
+
+ +
Please post in plain text
+ ++ A growing number of MTAs serving list subscribers are rejecting + all HTML traffic. At least one MTA has gone so far as to blacklist shorewall.net + "for continuous abuse" because it has been my policy to allow HTML in +list posts!!
+
+ I think that blocking all HTML is a Draconian way to control + spam and that the ultimate losers here are not the spammers but the +list subscribers whose MTAs are bouncing all shorewall.net mail. As +one list subscriber wrote to me privately "These e-mail admin's need +to get a (expletive deleted) life instead of trying to rid the +planet of HTML based e-mail". Nevertheless, to allow subscribers to receive +list posts as must as possible, I have now configured the list server +at shorewall.net to strip all HTML from outgoing posts.
+
Where to Send your Problem Report or to Ask for Help
- -+ +- ++ list. +If you run Shorewall under Bering -- please post your question or problem - to the LEAF Users -mailing list.
- If you run Shorewall under MandrakeSoft Multi Network Firewall - (MNF) and you have not purchased an MNF license from MandrakeSoft then - you can post non MNF-specific Shorewall questions to the LEAF Users + mailing list. + If you run Shorewall under MandrakeSoft Multi Network Firewall + (MNF) and you have not purchased an MNF license from MandrakeSoft then + you can post non MNF-specific Shorewall questions to the Shorewall users mailing -list. Do not expect to get free MNF support on the list.
- + list. Do not expect to get free MNF support on the list.
+Otherwise, please post your question or problem to the Shorewall users mailing -list.
-
To Subscribe to the mailing list go to http://lists.shorewall.net/mailman/listinfo/shorewall-users - .
+ . - -Last Updated 2/3/2003 - Tom Eastep
- + +Last Updated 2/4/2003 - Tom Eastep
+ Copyright © 2001, 2002, 2003 Thomas M. Eastep.
-
+
-
-
+
+