diff --git a/Shorewall-docs/Documentation.htm b/Shorewall-docs/Documentation.htm
index b44a0319f..8964733a5 100644
--- a/Shorewall-docs/Documentation.htm
+++ b/Shorewall-docs/Documentation.htm
@@ -9,11 +9,17 @@
+ Shorewall 1.3 Reference+ |
+
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 +
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 files.
This file is used to set the following firewall parameters:
--Why do you call it "Shorewall"?
-What distributions does it work with?
- - -
- - - --I just ran an nmap UDP scan of my firewall and -it showed 100s of ports as open!!!!
-
- - - - --
- --
--I've installed Shorewall and now I can't ping through the -firewall
- -
--Where are the log messages written and -how do I change the destination?
-Shorewall is writing log messages all over my -console making it unusable!
- -
- --When I try to start Shorewall on RedHat 7.x, I +
+
+ + ++ ++ +Shorewall FAQs
+1a. Ok -- I followed those instructions +but it doesn't work.
+ + + +3. I want to use Netmeeting with +Shorewall. What do I do?
+ +4a. I just ran an nmap UDP scan +of my firewall and it showed 100s of ports as open!!!!
+5. I've installed Shorewall and now I +can't ping through the firewall
+ +6. Where are the log messages +written and how do I change the destination?
+ +6a. Are there any log parsers +that work with Shorewall?
+ + + +8. When I try to start Shorewall on RedHat 7.x, I get messages about insmod failing -- what's wrong?
- -
-+Why does Shorewall only accept IP addresses as + +
9. Why does Shorewall only accept IP addresses as opposed to FQDNs?
+ +10. What distributions does it +work with?
+ +11. What features does it +support?
+ + + +13. Why do you call it "Shorewall"?
+ + + +15. My local systems can't see out to +the net
+ +16. Shorewall is writing log messages +all over my console making it unusable!
+ +17. Why can't Shorewall detect my +interfaces properly?
++
1. I want to forward UDP port 7777 to my my personal PC with IP @@ -556,11 +563,10 @@ over my console making it unusable!
+ zone is defined as all hosts connected through eth1.Answer: The above output is perfectly normal. The Net zone is defined as all hosts that are connected through eth0 and the local - zone is defined as all hosts connected through eth1. -
Last updated -7/31/2002 - Tom +8/15/2002 - Tom Eastep
Copyright diff --git a/Shorewall-docs/GnuCopyright.htm b/Shorewall-docs/GnuCopyright.htm index 7b70f73ff..9edd1c7ae 100644 --- a/Shorewall-docs/GnuCopyright.htm +++ b/Shorewall-docs/GnuCopyright.htm @@ -6,12 +6,17 @@
Copyright - -GNU Free Documentation License
++
+ ++ +GNU Free Documentation License
+Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA diff --git a/Shorewall-docs/IPIP.htm b/Shorewall-docs/IPIP.htm index f0c80a4f7..c8c0e7a75 100644 --- a/Shorewall-docs/IPIP.htm +++ b/Shorewall-docs/IPIP.htm @@ -5,11 +5,16 @@GRE/IPIP Tunnels - -GRE and IPIP Tunnels
++
+ ++ +GRE and IPIP Tunnels
+Warning: GRE and IPIP Tunnels are insecure when used over the internet; use them at your own risk
GRE and IPIP tunneling with Shorewall requires iproute2 and can be used to bridge two masqueraded networks. GRE diff --git a/Shorewall-docs/IPSEC.htm b/Shorewall-docs/IPSEC.htm index 2c827b29c..fee400531 100644 --- a/Shorewall-docs/IPSEC.htm +++ b/Shorewall-docs/IPSEC.htm @@ -10,10 +10,15 @@ - - +
-IPSEC Tunnels
++
+ ++ +IPSEC Tunnels
+Configuring FreeS/Wan
There is an excellent guide to configuring IPSEC tunnels at http://jixen.tripod.com @@ -113,8 +118,28 @@ on system B, we would have:
You need to define a zone for the remote subnet or include + it in your local zone. In this example, we'll assume that you have created a + zone called "vpn" to represent the remote subnet.
+ ++++
++ +ZONE +DISPLAY +COMMENTS ++ + +vpn +VPN +Remote Subnet +
At both -systems, ipsec0 would be included in /etc/shorewall/interfaces as a "gw" +systems, ipsec0 would be included in /etc/shorewall/interfaces as a "vpn" interface:
@@ -131,7 +156,7 @@ interface: OPTIONS- gw +vpn ipsec0 @@ -140,7 +165,7 @@ interface: - You will need to allow traffic between the "gw" zone and +
You will need to allow traffic between the "vpn" zone and the "loc" zone -- if you simply want to admit all traffic in both directions, you can use the policy file:
@@ -155,13 +180,13 @@ interface:loc -gw +vpn ACCEPT - gw +vpn loc ACCEPT @@ -188,6 +213,26 @@ be able to establish a secure connection back to your local network. +
You need to define a zone for the laptop or include it in + your local zone. In this example, we'll assume that you have created a zone + called "vpn" to represent the remote host.
+ ++++
++ +ZONE +DISPLAY +COMMENTS ++ + +vpn +VPN +Remote Subnet +In this instance, the mobile system (B) has IP address 134.28.54.2 but that cannot be determined in advance. In the /etc/shorewall/tunnels file on system A, @@ -210,15 +255,14 @@ the following entry should be made:
ipsec net 0.0.0.0/0 -gw +vpn
Note that the GATEWAY -ZONE column contains the name of the zone corresponding to peer subnetworks -(gw in the default /etc/shorewall/zones). This indicates that the +ZONE column contains the name of the zone corresponding to peer subnetworks. This indicates that the gateway system itself comprises the peer subnetwork; in other words, the remote gateway is a standalone system.
@@ -228,7 +272,7 @@ remote gateway is a standalone system.Last -updated 5/18/2002 - +updated 8/20/2002 - Tom Eastep
diff --git a/Shorewall-docs/Install.htm b/Shorewall-docs/Install.htm index 321ae6156..468f4b2e7 100644 --- a/Shorewall-docs/Install.htm +++ b/Shorewall-docs/Install.htm @@ -5,10 +5,16 @@
+ Shorewall Installation+ |
+
Install using RPM IMPORTANT: If all you want to do is forward
ports to servers behind your firewall, you do NOT want to use static NAT.
Port forwarding can be accomplished with simple entries in the
diff --git a/Shorewall-docs/News.htm b/Shorewall-docs/News.htm
index bd6842fa3..78ec4d63d 100644
--- a/Shorewall-docs/News.htm
+++ b/Shorewall-docs/News.htm
@@ -5,13 +5,42 @@
8/22/2002 - Shorewall 1.3.7 Released 8/13/2002 Features in this release include: 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. 8/13/2002 - Documentation in the CVS Repository The Shorewall-docs project now contains just the HTML and image files - the
@@ -995,7 +1024,7 @@ version:
Install
diff --git a/Shorewall-docs/NAT.htm b/Shorewall-docs/NAT.htm
index 6c7d6dadc..c72bf1388 100644
--- a/Shorewall-docs/NAT.htm
+++ b/Shorewall-docs/NAT.htm
@@ -5,13 +5,18 @@
-
Static NAT
+
+
+
+
+
+ Static NAT
+ Shorewall News Archive
+
+
+
+
+
+
+ Shorewall News Archive
+
+
+
+
Updated 8/13/2002 - Tom
+ Updated 8/22/2002 - Tom
Eastep Proxy ARP can be used to make the systems with addresses
130.252.100.18 and 130.252.100.19 appear to be on the upper (130.252.100.*)
subnet. Assuming that the upper firewall interface is eth0 and the
lower interface is eth1, this is accomplished using the following entries in
/etc/shorewall/proxyarp: Be sure that the internal systems (130.242.100.18 and 130.252.100.19
in the above example) are not included in any specification in
/etc/shorewall/masq or /etc/shorewall/nat.
+
+
+
+
ADDRESS
@@ -46,6 +56,8 @@
no
A word of warning is in order here. ISPs typically configure - there routers with a long ARP cache timeout. If you move a system from + their routers with a long ARP cache timeout. If you move a system from parallel to your firewall to behind your firewall with Proxy ARP, it will probably be HOURS before that system can communicate with the internet. You can call your ISP and ask them to purge the stale ARP cache entry but many @@ -86,9 +98,8 @@ was the MAC address of the system on the lower left. In other words, the gateway's ARP cache still associates 130.252.100.19 with the NIC in that system rather than with the firewall's eth0.
Last updated 8/11/2002 -
+ Last updated 8/17/2002 -
Tom
Eastep Shorewall supports two different forms of blacklisting; static and dynamic. Shorewall
diff --git a/Shorewall-docs/configuration_file_basics.htm b/Shorewall-docs/configuration_file_basics.htm
index c08ba2dca..7071256c0 100644
--- a/Shorewall-docs/configuration_file_basics.htm
+++ b/Shorewall-docs/configuration_file_basics.htm
@@ -6,12 +6,17 @@
Warning: If you copy or edit your
configuration files on a system running Microsoft Windows, you must
run them through
diff --git a/Shorewall-docs/copyright.htm b/Shorewall-docs/copyright.htm
index 2330511e6..b4af82bdd 100644
--- a/Shorewall-docs/copyright.htm
+++ b/Shorewall-docs/copyright.htm
@@ -6,12 +6,17 @@
Copyright © 2000, 2001
Thomas M Eastep I strongly urge you to read and print a copy of the
Shorewall QuickStart Guide
@@ -61,7 +66,7 @@ AND ISSUE A "shorewall start" COMMAND. SOME CONFIGURATION IS REQUIRED
FIREWALL WILL START. IF YOU ISSUE A "start" COMMAND AND THE FIREWALL FAILS TO
START, YOUR SYSTEM WILL NO LONGER ACCEPT ANY NETWORK TRAFFIC. IF THIS HAPPENS,
ISSUE A "shorewall clear" COMMAND TO RESTORE NETWORK CONNECTIVITY.
-
-
-
+
Shorewall
diff --git a/Shorewall-docs/blacklisting_support.htm b/Shorewall-docs/blacklisting_support.htm
index c27da0af8..d6f57f189 100644
--- a/Shorewall-docs/blacklisting_support.htm
+++ b/Shorewall-docs/blacklisting_support.htm
@@ -6,12 +6,17 @@
-
-
-Home
-Shorewall 1.2 Home
-Features
-Requirements
-Download
-QuickStart Guides
-Installation/Upgrade
- /Configuration
-Documentation
-Reference Manual
-FAQs
-Troubleshooting
-Errata
-Support
-Mailing Lists
+
+
+
+
+Configuration
-
- News Archive
-CVS Repository
-Quotes from Users
-About the Author
-Donations
+
+
Blacklisting Support
+
+
+
+
+
+ Blacklisting Support
+ Static Blacklisting
Configuration Files
+
+
+
+
+
+ Configuration Files
+ Copyright
+
+
+
+
+
+ Copyright
+
DHCP
+
+
+
+
+
+ DHCP
+ DHCP Server on your firewall
Shorewall Download
+
+
+
+
+
+ Shorewall Download
+
Download Latest Version (1.3.6): Remember that updates to the mirrors +
Download Latest Version (1.3.7): Remember that updates to the mirrors occur 1-12 hours after an update to the primary site.
@@ -211,7 +216,7 @@ Shorewall component. There's no guarantee that what you find there will work at all. -
Last Updated 8/05/2002 - Tom +
-Last Updated 8/22/2002 - Tom Eastep
Copyright diff --git a/Shorewall-docs/errata.htm b/Shorewall-docs/errata.htm index a3905ae22..6adf735d5 100644 --- a/Shorewall-docs/errata.htm +++ b/Shorewall-docs/errata.htm @@ -10,15 +10,19 @@ - + -
Shorewall Errata/Upgrade Issues
++
+ ++ +Shorewall Errata/Upgrade Issues
+- - - IMPORTANT
+ IMPORTANT
- @@ -86,6 +90,53 @@ dos2unix
Upgrade Issues
+Version >= 1.3.7
+ +Users specifying ALLOWRELATED=No in + /etc/shorewall.conf will need to include the + following rules in their /etc/shorewall/icmpdef + file (creating this file if necessary):
+ +run_iptables -A icmpdef -p ICMP --icmp-type echo-reply -j ACCEPT + run_iptables -A icmpdef -p ICMP --icmp-type source-quench -j ACCEPT + run_iptables -A icmpdef -p ICMP --icmp-type destination-unreachable -j ACCEPT + run_iptables -A icmpdef -p ICMP --icmp-type time-exceeded -j ACCEPT + run_iptables -A icmpdef -p ICMP --icmp-type parameter-problem -j ACCEPT+Users having an /etc/shorewall/icmpdef file may remove the ". + /etc/shorewall/icmp.def" command from that file since the icmp.def file is now + empty.
+Upgrading Bering to + Shorewall >= 1.3.3
+ +To properly upgrade with Shorewall version + 1.3.3 and later:
+ ++
+- Be sure you have a backup -- you will need + to transcribe any Shorewall configuration + changes that you have made to the new + configuration.
+- Replace the shorwall.lrp package provided on + the Bering floppy with the later one. If you did + not obtain the later version from Jacques's + site, see additional instructions below.
+- Edit the /var/lib/lrpkg/root.exclude.list + file and remove the /var/lib/shorewall entry if + present. Then do not forget to backup root.lrp !
+The .lrp that I release isn't set up for a two-interface firewall like + Jacques's. You need to follow the instructions for + setting up a two-interface firewall plus you also need to add the following + two Bering-specific rules to /etc/shorewall/rules:
+++# Bering specific rules: +# allow loc to fw udp/53 for dnscache to work +# allow loc to fw tcp/80 for weblet to work +# +ACCEPT loc fw udp 53 +ACCEPT loc fw tcp 80+Version >= 1.3.6
If you have a pair of firewall systems configured for @@ -144,6 +195,38 @@ dos2unix
Problems in Version 1.3
+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 :-( @@ -289,8 +372,7 @@ you are currently running RedHat 7.1, you can install either of these RPMs
Update 11/9/2001: RedHat has - released an iptables-1.2.4 RPM of their own which you can download from - + 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.
@@ -357,21 +439,25 @@ Aborted (core dumped)Upgrading: rpm -Uvh <shorewall rpm>
-Problems with - iptables version 1.2.7 and MULTIPORT=Yes
+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, - users who install iptables 1.2.7 must set - MULTIPORT=No in /etc/shorewall/shorewall.conf or - install - - this firewall script in /var/lib/shorewall/firewall - as described above.
+ if you install iptables 1.2.7 you must- Last updated 8/14/2002 - +
+
+- 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.
++ Last updated 8/22/2002 - Tom Eastep
Copyright diff --git a/Shorewall-docs/errata_1.htm b/Shorewall-docs/errata_1.htm index c6b5123a1..b64dc819a 100644 --- a/Shorewall-docs/errata_1.htm +++ b/Shorewall-docs/errata_1.htm @@ -6,12 +6,17 @@
-Shorewall Errata for Version 1 - -Shorewall Errata for Version 1.1
++
+ ++ +Shorewall Errata for Version 1.1
+To those of you who downloaded the 1.1.13 updated firewall script prior to Sept 20, 2001:
diff --git a/Shorewall-docs/errata_2.htm b/Shorewall-docs/errata_2.htm index 11355f3a7..29250ef7d 100644 --- a/Shorewall-docs/errata_2.htm +++ b/Shorewall-docs/errata_2.htm @@ -10,10 +10,15 @@ - - + -Shorewall 1.2 Errata
++
+ ++ +Shorewall 1.2 Errata
+diff --git a/Shorewall-docs/fallback.htm b/Shorewall-docs/fallback.htm index 843fa0682..b3219c5e1 100644 --- a/Shorewall-docs/fallback.htm +++ b/Shorewall-docs/fallback.htm @@ -5,12 +5,19 @@
Shorewall Fallback and Uninstall - -Fallback and Uninstall
++
+ ++ + +Fallback and Uninstall
+ +Shorewall includes a fallback script diff --git a/Shorewall-docs/gnu_mailman.htm b/Shorewall-docs/gnu_mailman.htm index 94a1aa0bd..702ff74be 100644 --- a/Shorewall-docs/gnu_mailman.htm +++ b/Shorewall-docs/gnu_mailman.htm @@ -6,13 +6,20 @@
GNU Mailman - -GNU Mailman/Postfix
+
-the Easy Way+
+ ++ ++ +GNU Mailman/Postfix +the Easy Way
+
The following was posted on the Postfix mailing list on 5/4/2002 by Michael Tokarev as a suggested addition to the Postfix FAQ.
Q: Mailman does not work with Postfix, complaining about GID mismatch
diff --git a/Shorewall-docs/index.htm b/Shorewall-docs/index.htm index b140d6f58..6bf808fdb 100644 --- a/Shorewall-docs/index.htm +++ b/Shorewall-docs/index.htm @@ -5,10 +5,9 @@Shoreline Firewall - -Routestopped File:
-#INTERFACE HOST(S) +#INTERFACE HOST(S) eth1 206.124.146.177 eth2 - - eth3 206.124.146.180+ eth3 206.124.146.180Common File:
. /etc/shorewall/common.def run_iptables -A common -p udp --sport 53 -mstate --state NEW -j DROP diff --git a/Shorewall-docs/ports.htm b/Shorewall-docs/ports.htm index 5a4d43b72..f205236fe 100644 --- a/Shorewall-docs/ports.htm +++ b/Shorewall-docs/ports.htm @@ -5,10 +5,16 @@Shorewall Port Information - -Ports required for Various Services/Applications
+ ++
+ ++ +Ports required for Various Services/Applications
+In addition to those applications described in the /etc/shorewall/rules documentation, here are some other @@ -95,6 +101,12 @@ services/applications that you may need to configure your firewall to accommodat
Traceroute
+UDP ports 33434 through 33434+<max number of hops>-1
+NFS
++There's some good 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?
@@ -103,7 +115,7 @@ services/applications that you may need to configure your firewall to accommodat http://www.networkice.com/advice/Exploits/PortsLast updated 7/30/2002 - +
-Last updated 8/21/2002 - Tom Eastep
Copyright diff --git a/Shorewall-docs/quotes.htm b/Shorewall-docs/quotes.htm index bff768d67..9f3778db2 100644 --- a/Shorewall-docs/quotes.htm +++ b/Shorewall-docs/quotes.htm @@ -6,12 +6,17 @@Quotes from Shorewall Users - -Quotes from Shorewall Users
++
+ ++ +Quotes from Shorewall Users
+"I just installed Shorewall after weeks of messing with diff --git a/Shorewall-docs/samba.htm b/Shorewall-docs/samba.htm index 98d52d9a6..6656b21bf 100644 --- a/Shorewall-docs/samba.htm +++ b/Shorewall-docs/samba.htm @@ -6,12 +6,17 @@
Samba - -Samba
++
+ ++ +Samba
+If you wish to run Samba on your firewall and access shares between the firewall and local hosts, you need the following rules:
/etc/shorewall/rules:
diff --git a/Shorewall-docs/seattlefirewall_index.htm b/Shorewall-docs/seattlefirewall_index.htm index 6db9b5750..81e76436c 100644 --- a/Shorewall-docs/seattlefirewall_index.htm +++ b/Shorewall-docs/seattlefirewall_index.htm @@ -11,7 +11,7 @@- + @@ -63,29 +63,53 @@
News
+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 use 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.
+8/13/2002 - Documentation in the - CVS Repository -
+ CVS RepositoryThe 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 -
+ CVS RepositoryThis 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.
8/7/2002 - Upgrade Issues section added - to the Errata Page -
+ to the Errata PageNow there is one place to go to look for issues involved with upgrading to recent versions of Shorewall.
-8/7/2002 - Shorewall 1.3.6 -
+8/7/2002 - Shorewall 1.3.6
This is primarily a bug-fix rollup with a couple of new features:
@@ -126,7 +150,7 @@Updated - 8/13/2002 - Tom Eastep + 8/22/2002 - Tom Eastep diff --git a/Shorewall-docs/shoreline.htm b/Shorewall-docs/shoreline.htm index 039c60ba3..3e6239b7f 100644 --- a/Shorewall-docs/shoreline.htm +++ b/Shorewall-docs/shoreline.htm @@ -10,13 +10,19 @@ - +
-Tom Eastep
++
@@ -65,16 +71,15 @@ Washington+ ++ +Tom Eastep
+Our current home network consists of:
-
- 1.2Gz Athlon, Windows XP Pro, 320MB RAM, 40GB & 8GB IDE HDs - and LNE100TX (Tulip) NIC - My personal Windows system. This system also has - RH7.3 installed.
-- PII/266, RH7.3, 320MB RAM, 20GB HD, LNE100TX(Tulip) NIC - My personal - GNU/Linux System which runs Samba configured as a WINS server.
-- K6-2/350, RH7.3, 256MB RAM, 8GB IDE HD, EEPRO100 NIC +
- 1.2Gz Athlon, Windows XP Pro, 320MB RAM, 40GB & 8GB IDE HDs and LNE100TX + (Tulip) NIC - My personal Windows system.
+- Celeron 1.4Gz, RH7.3, 256MB RAM, 60GB HD, LNE100TX(Tulip) NIC - My + personal Linux System which runs Samba configured as a WINS server.
+- K6-2/350, RH7.3, 384MB RAM, 8GB IDE HD, EEPRO100 NIC - Mail (Postfix & Courier-IMAP), HTTP (Apache), FTP (Pure_ftpd), DNS server (Bind).
-- PII/233, RH7.3 with 2.4.19 kernel, 128MB MB RAM, 2GB SCSI HD - 3 - LNE100TX (Tulip) and 1 TLAN NICs - Firewall running Shorewall 1.3.4 and a DHCP +
- PII/233, RH7.3 with 2.4.19 kernel, 256MB MB RAM, 2GB SCSI HD - 3 + LNE100TX (Tulip) and 1 TLAN NICs - Firewall running Shorewall 1.3.6 and a DHCP server. Also runs PoPToP for road warrior access.
- Duron 750, Win ME, 192MB RAM, 20GB HD, RTL8139 NIC - My wife's personal system.
- PII/400 Laptop, Win2k SP2, 224MB RAM, 12GB HD, onboard EEPRO100 and EEPRO100 @@ -83,7 +88,7 @@ in expansion base - My main work system.
For more about our network see my Shorewall Configuration.
-The PII/266 is made by Dell. All of our +
All of our other systems are made by Compaq (part of the new HP).. All of our Tulip NICs are Netgear FA310TXs.
@@ -93,7 +98,7 @@ in expansion base - My main work system.Last updated 8/10/2002 - +
@@ -68,9 +63,8 @@ processing of the command.Last updated 8/16/2002 - Tom Eastep
Copyright diff --git a/Shorewall-docs/shorewall_ca_certificate.htm b/Shorewall-docs/shorewall_ca_certificate.htm index 1241ebdc7..3768f568c 100644 --- a/Shorewall-docs/shorewall_ca_certificate.htm +++ b/Shorewall-docs/shorewall_ca_certificate.htm @@ -6,7 +6,6 @@Shorewall CA Certificate - diff --git a/Shorewall-docs/shorewall_extension_scripts.htm b/Shorewall-docs/shorewall_extension_scripts.htm index bb81ef009..c8689cdbe 100644 --- a/Shorewall-docs/shorewall_extension_scripts.htm +++ b/Shorewall-docs/shorewall_extension_scripts.htm @@ -6,12 +6,17 @@Shorewall Extension Scripts - -Extension Scripts
++
+ ++ +Extension Scripts
+Extension scripts are user-provided @@ -41,20 +46,10 @@ been processed.
-The following two files receive -special treatment:
- --
+ may be used as a starting point for making your own customized file.- /etc/shorewall/common -- If this file is present, the rules that it +
-The /etc/shorewall/common file receives special treatment. If this file is present, the rules that it defines will totally replace the default rules in the common chain. These default rules are contained in the file /etc/shorewall/common.def which - may be used as a starting point for making your own customized file.
- /etc/shorewall/icmpdef -- If this file is present, the rules that it - defines will totally replace the default rules in the icmpdef chain. -These default rules are contained in the file /etc/shorewall/icmp.def -which may be used as a starting point for making your own customized -file.
-- If you decide to create /etc/shorewall/common or /etc/shorewall/icmp.def, it - is a good idea to use the following technique (common file shown but the same - technique applies to icmpdef).
+ If you decide to create /etc/shorewall/common it is a good idea to use the + following technique @@ -80,25 +74,36 @@ processing of the command.-source /etc/shorewall/common.def +. /etc/shorewall/common.def <add your rules here>If you need to supercede a rule in the released common.def file, you can add - the superceding rule before the 'source' command. Using this technique allows + the superceding rule before the '.' command. Using this technique allows you to add new rules while still getting the benefit of the latest common.def file.
-Remember that /etc/shorewall/common and /etc/shorewall/icmpdef define rules +
Remember that /etc/shorewall/common defines rules that are only applied if the applicable policy is DROP or REJECT. These rules - are NOT applied if the policy is ACCEPT or CONTINUE.
+ are NOT applied if the policy is ACCEPT or CONTINUE. -
-Last updated -8/5/2002 - Tom +
If you set ALLOWRELATED=No in shorewall.conf, then most ICMP packets will be + rejected by the firewall. It is recommended with this setting that you create + the file /etc/shorewall/icmpdef and in it place the following commands:
+ + + +run_iptables -A icmpdef -p ICMP --icmp-type echo-reply -j ACCEPT + run_iptables -A icmpdef -p ICMP --icmp-type source-quench -j ACCEPT + run_iptables -A icmpdef -p ICMP --icmp-type destination-unreachable -j ACCEPT + run_iptables -A icmpdef -p ICMP --icmp-type time-exceeded -j ACCEPT + run_iptables -A icmpdef -p ICMP --icmp-type parameter-problem -j ACCEPT ++Last updated +8/22/2002 - Tom Eastep
Copyright 2002 Thomas M. Eastep
diff --git a/Shorewall-docs/shorewall_features.htm b/Shorewall-docs/shorewall_features.htm index afd814396..e2dff314f 100644 --- a/Shorewall-docs/shorewall_features.htm +++ b/Shorewall-docs/shorewall_features.htm @@ -6,12 +6,17 @@Shorewall Features - -Shorewall Features
++
+ ++ +Shorewall Features
+
- Uses Netfilter's connection tracking facilities for stateful packet filtering.
diff --git a/Shorewall-docs/shorewall_firewall_structure.htm b/Shorewall-docs/shorewall_firewall_structure.htm index 89dcfd7b1..ffdfd6b46 100644 --- a/Shorewall-docs/shorewall_firewall_structure.htm +++ b/Shorewall-docs/shorewall_firewall_structure.htm @@ -6,14 +6,19 @@Shorewall Firewall Structure - -Firewall Structure
++
+ ++ +Firewall Structure
+- Shorewall views the network in which it is running as a set of disjoint + Shorewall views the network in which it is running as a set of zones. Shorewall itself defines exactly one zone called "fw" which refers to the firewall system itself . The /etc/shorewall/zones file is used to define additional zones and the example file provided with Shorewall @@ -36,6 +41,21 @@ from the internet and from the DMZ and in some cases, from each other. +
While zones are normally disjoint (no two zones have a host in common), + there are cases where nested or overlapping zone definitions are appropriate.
+Packets entering the firewall first pass through the mangle table's + PREROUTING chain (you can see the mangle table by typing "shorewall show + mangle"). If the packet entered through an interface that has the norfc1918 + option, then the packet is sent down the man1918 which will drop + the packet if its destination IP address is reserved (as specified in the + /etc/shorewall/rfc1918 file). Next the packet passes through the pretos + chain to set its TOS field as specified in the /etc/shorewall/tos file. + Finally, if traffic control/shaping is being used, the packet is sent through + the tcpre chain to be marked for later use in policy routing or traffic + control.
+Next, if the packet isn't part of an established connection, it passes + through the nat table's PREROUTING chain (you can see the nat table by + typing "shorewall show nat").
Traffic entering the firewall is sent to an input chain. If the traffic is destined for the diff --git a/Shorewall-docs/shorewall_index.htm b/Shorewall-docs/shorewall_index.htm index 0624df8b4..bede1c576 100644 --- a/Shorewall-docs/shorewall_index.htm +++ b/Shorewall-docs/shorewall_index.htm @@ -5,7 +5,6 @@
Shoreline Firewall - diff --git a/Shorewall-docs/shorewall_mailing_list_migration.htm b/Shorewall-docs/shorewall_mailing_list_migration.htm index 054eb4a46..d39573fe8 100644 --- a/Shorewall-docs/shorewall_mailing_list_migration.htm +++ b/Shorewall-docs/shorewall_mailing_list_migration.htm @@ -6,12 +6,17 @@Shorewall Mailing List Migration - -Shorewall Mailing List Migration
++
+ ++ +Shorewall Mailing List Migration
+If you are a current subscriber to the Shorewall mailing list at Sourceforge, please do the following:
diff --git a/Shorewall-docs/shorewall_mirrors.htm b/Shorewall-docs/shorewall_mirrors.htm index 01bf4e6ff..a99d161ed 100644 --- a/Shorewall-docs/shorewall_mirrors.htm +++ b/Shorewall-docs/shorewall_mirrors.htm @@ -6,12 +6,17 @@
Shorewall Mirrors - -Shorewall Mirrors
++
+ ++ +Shorewall Mirrors
+Remember that updates to the mirrors are often delayed for 6-12 hours after an update to the primary site.
diff --git a/Shorewall-docs/shorewall_prerequisites.htm b/Shorewall-docs/shorewall_prerequisites.htm index 2a3eb83d4..56067978f 100644 --- a/Shorewall-docs/shorewall_prerequisites.htm +++ b/Shorewall-docs/shorewall_prerequisites.htm @@ -6,13 +6,17 @@Shorewall Prerequisites - -Shorewall Requirements
-+
+
+ ++ +Shorewall Requirements
+
- A kernel that supports netfilter. I've tested with 2.4.2 - 2.4.19. Check here for kernel configuration information. diff --git a/Shorewall-docs/shorewall_quickstart_guide.htm b/Shorewall-docs/shorewall_quickstart_guide.htm index 5c3d47df5..bcd097d68 100644 --- a/Shorewall-docs/shorewall_quickstart_guide.htm +++ b/Shorewall-docs/shorewall_quickstart_guide.htm @@ -6,13 +6,19 @@
Shorewall QuickStart Guide - + -Shorewall QuickStart Guides
+
-Version 3.0+
+ ++ +Shorewall QuickStart Guides
+
+Version 3.0With thanks to Richard who reminded me once again that we must all first walk before we can run.
@@ -69,7 +75,7 @@ explained in the single-address guides above.Additional Documentation
The following documentation covers a variety of topics and supplements the -QuickStart Guides described above.
+QuickStart Guides described above.
- Blacklisting
- Static Blacklisting using /etc/shorewall/blacklist
@@ -126,6 +132,7 @@ QuickStart Guides described above.- Samba
- Starting/stopping the Firewall
- Static NAT
+- Traffic Shaping/Control
- Tunnels
- IPSEC
- GRE and IPIP
diff --git a/Shorewall-docs/shorewall_setup_guide.htm b/Shorewall-docs/shorewall_setup_guide.htm index e99e5abfe..fefe0e2ab 100644 --- a/Shorewall-docs/shorewall_setup_guide.htm +++ b/Shorewall-docs/shorewall_setup_guide.htm @@ -6,7 +6,7 @@Shorewall Setup Guide - + @@ -46,6 +46,10 @@ know more about Shorewall than is contained in the guides. Because the range of possible applications is so broad, the Guide will give you general guidelines and will point you to other resources as necessary. +
+If you run LEAF Bering, your Shorewall configuration is NOT what I release -- I +suggest that you consider installing a stock Shorewall lrp from the +shorewall.net site before you proceed.
This guide assumes that you have the iproute/iproute2 package installed (on RedHat, the package is called iproute). You can tell if this package is installed by the presence of an ip program on your firewall @@ -730,6 +734,13 @@ table but if we logically and that address with 255.255.255.0, the result is
192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth2So to route a packet to 192.168.1.5, the packet is sent directly over eth2. +
One more thing needs to be emphasized -- all outgoing packet are +sent using the routing table and reply packets are not a special case. There +seems to be a common mis-conception whereby people think that request packets +are like salmon and contain a genetic code that is magically transferred to +reply packets so that the replies follow the reverse route taken by the request. +That isn't the case; the replies may take a totally different route back to the +client than was taken by the requests -- they are totally independent.
4.4 Address Resolution Protocol
When sending packets over Ethernet, IP addresses aren't used. Rather Ethernet addressing is based on Media Access Control (MAC) @@ -1123,7 +1134,7 @@ Destination Gateway Genmask Flags MSS Window irtt Iface host routes thru eth2 to 192.0.2.177 and 192.0.2.178.
A word of warning is in order here. ISPs typically configure - there routers with a long ARP cache timeout. If you move a system from + their routers with a long ARP cache timeout. If you move a system from parallel to your firewall to behind your firewall with Proxy ARP, it will probably be HOURS before that system can communicate with the internet. You can call your ISP and ask them to purge the stale ARP cache entry but many @@ -2347,11 +2358,11 @@ foobar.net. 86400 IN A 192.0.2.177 test it using the "shorewall try" command.
Last updated -8/10/2002 - Tom +8/18/2002 - Tom Eastep
- +