From 10b51d19910be800ed5e0229a0bbae13b3a2d39c Mon Sep 17 00:00:00 2001 From: teastep Date: Sat, 8 Feb 2003 20:46:02 +0000 Subject: [PATCH] Shorewall 1.3.14 Release git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@438 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs/FAQ.htm | 1765 ++++++----- Shorewall-docs/News.htm | 2846 +++++++++--------- Shorewall-docs/blacklisting_support.htm | 128 +- Shorewall-docs/configuration_file_basics.htm | 609 ++-- Shorewall-docs/download.htm | 679 +++-- Shorewall-docs/errata.htm | 1044 +++---- Shorewall-docs/mailing_list.htm | 412 +-- Shorewall-docs/ports.htm | 297 +- Shorewall-docs/seattlefirewall_index.htm | 765 ++--- Shorewall-docs/shorewall_features.htm | 180 +- Shorewall-docs/sourceforge_index.htm | 826 ++--- Shorewall-docs/support.htm | 568 ++-- 12 files changed, 4860 insertions(+), 5259 deletions(-) diff --git a/Shorewall-docs/FAQ.htm b/Shorewall-docs/FAQ.htm index 9c261b54a..401f1db4d 100644 --- a/Shorewall-docs/FAQ.htm +++ b/Shorewall-docs/FAQ.htm @@ -2,1131 +2,1256 @@ - + + - + + - + + - + + Shorewall FAQ - + + - - - + + - + + - - + + +
+
- +

Shorewall FAQs

-
+

1. I want to forward UDP - port 7777 to my my personal PC with IP address 192.168.1.5. - I've looked everywhere and can't find how to do it.

- + port 7777 to my my personal PC with IP address 192.168.1.5. + I've looked everywhere and can't find how to do it.

+ +

1a. Ok -- I followed those instructions - but it doesn't work.
-

- + but it doesn't work.
+

+ +

1b. I'm still having problems with - port forwarding

- + port forwarding

+

2. I port forward www requests - to www.mydomain.com (IP 130.151.100.69) to system 192.168.1.5 - in my local network. External clients can browse http://www.mydomain.com - but internal clients can't.

- + to www.mydomain.com (IP 130.151.100.69) to system 192.168.1.5 + in my local network. External clients can browse http://www.mydomain.com + but internal clients can't.

+ +

2a. I have a zone "Z" with an RFC1918 - subnet and I use static NAT to assign non-RFC1918 - addresses to hosts in Z. Hosts in Z cannot communicate with - each other using their external (non-RFC1918 addresses) so they - can't access each other using their DNS names.

+ subnet and I use static NAT to assign non-RFC1918 + addresses to hosts in Z. Hosts in Z cannot communicate with + each other using their external (non-RFC1918 addresses) so they + can't access each other using their DNS names.

+

3. I want to use Netmeeting - or MSN Instant Messenger with Shorewall. What do -I do?

- + or MSN Instant Messenger with Shorewall. What do + I do?

+ +

4. I just used an online port scanner - to check my firewall and it shows some ports as 'closed' - rather than 'blocked'. Why?

- + to check my firewall and it shows some ports as 'closed' + rather than 'blocked'. Why?

+ +

4a. I just ran an nmap UDP scan - of my firewall and it showed 100s of ports as open!!!!

- + 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

+ I can't ping through the firewall

+

6. Where are the log messages - written and how do I change the destination?

+ written and how do I change the destination?

- +

6a. Are there any log parsers - that work with Shorewall?

- + that work with Shorewall?

+

6b. DROP messages on port 10619 are flooding the logs with their connect - requests. Can i exclude these error messages for this port temporarily + requests. Can i exclude these error messages for this port temporarily from logging in Shorewall?
-

- +

+

6c. All day long I get a steady flow - of these DROP messages from port 53 to some high numbered port.  - They get dropped, but what the heck are they?
-

- + of these DROP messages from port 53 to some high numbered port.  + They get dropped, but what the heck are they?
+

+ +

6d. Why is the MAC address +in Shorewall log messages so long? I thought MAC addresses were only +6 bytes in length.
+

7. When I stop Shorewall using 'shorewall stop', I can't connect to anything. Why doesn't that command - work?

+ work?

+

8. When I try to start Shorewall - on RedHat I get messages about insmod failing -- what's - wrong?

+ on RedHat I get messages about insmod failing -- what's + wrong?

+

9. Why can't Shorewall detect - my interfaces properly?

+ my interfaces properly?

- +

10. What distributions does - it work with?

+ it work with?

+

11. What features does it support?

-

12. Why isn't there a GUI

+ +

12. Is there a GUI?

+

13. Why do you call it "Shorewall"?

- + +

14. I'm connected via a cable modem - and it has an internel web server that allows me to configure/monitor - it but as expected if I enable rfc1918 blocking for - my eth0 interface, it also blocks the cable modems web server.

- + and it has an internel web server that allows me to configure/monitor + it but as expected if I enable rfc1918 blocking for + my eth0 interface, it also blocks the cable modems web +server.

+ +

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.

+ 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.

+

15. My local systems can't see - out to the net

+ out to the net

+

16. Shorewall is writing log messages - all over my console making it unusable!
-

- 17. How - do I find out why this traffic is getting logged?
-
- 18. Is there any way to - use aliased ip addresses with Shorewall, and maintain -separate rulesets for different IPs?
-
- 19. I have added entries - to /etc/shorewall/tcrules but they don't seem to do - anything. Why?
-
- 20. I have just set up a - server. Do I have to change Shorewall to allow access to my server - from the internet?
+ all over my console making it unusable!
+

+ 17. How do I find out why this traffic is +getting logged?
+
+ 18. Is there any way +to use aliased ip addresses with Shorewall, and maintain + separate rulesets for different IPs?
+
+ 19. I have added entries + to /etc/shorewall/tcrules but they don't seem to do + anything. Why?
+
+ 20. I have just set up +a server. Do I have to change Shorewall to allow access to my +server from the internet?
+
+ 21. I see these strange +log entries occasionally; what are they?
+
+ 22. I have some iptables commands + that I want to run when Shorewall starts. Which file do +I put them in?

- 21. I see these strange log - entries occasionally; what are they?
-
- 22. I have some iptables commands -that I want to run when Shorewall starts. Which file do I -put them in?
-
- 23. Why do you use such ugly fonts - on your web site?
-
- 24: How can I allow conections to let's - say the ssh port only from specific IP Addresses on the internet?
- -
+ 23. Why do you use such ugly fonts + on your web site?
+
+ 24. How can I allow conections to +let's say the ssh port only from specific IP Addresses on the internet?
+
+ +

1. I want to forward UDP port 7777 to - my my personal PC with IP address 192.168.1.5. I've looked - everywhere and can't find how to do it.

- + my my personal PC with IP address 192.168.1.5. I've looked + everywhere and can't find how to do it. + +

Answer: The first example in the rules file documentation shows how to - do port forwarding under Shorewall. The format of a port-forwarding - rule to a local system is as follows:

- + do port forwarding under Shorewall. The format of a port-forwarding + rule to a local system is as follows:

+ +
- + - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + - + + - +
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATnetloc:<local IP address>[:<local - port>]<protocol><port #>
-
-
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATnetloc:<local IP address>[:<local + port>]<protocol><port #>
+
+
-
- + + +

So to forward UDP port 7777 to internal system 192.168.1.5, - the rule is:

- + the rule is:

+ +
- + - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + - + + - +
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATnetloc:192.168.1.5udp7777
-
-
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATnetloc:192.168.1.5udp7777
+
+
-
- + + +
If - you want to forward requests directed to a particular address ( <external - IP> ) on your firewall to an internal system:
- + you want to forward requests directed to a particular address ( <external + IP> ) on your firewall to an internal system: + +
- + - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + - + + - +
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATnetloc:<local IP address>[:<local - port>]<protocol><port #>-<external IP>
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATnetloc:<local IP address>[:<local + port>]<protocol><port #>-<external IP>
-
- Finally, -if you need to forward a range of ports, in the PORT column specify the range -as low-port:high-port.
+ + +Finally, if you need to forward a range of ports, in the PORT column specify +the range as low-port:high-port.
+

1a. Ok -- I followed those instructions - but it doesn't work

- + but it doesn't work + +

Answer: That is usually the result of one of two things:

- + + - + +

1b. I'm still having problems with port - forwarding

- Answer: To further diagnose this problem:
- + forwarding + Answer: To further diagnose this problem:
+ - +

2. I port forward www requests to www.mydomain.com - (IP 130.151.100.69) to system 192.168.1.5 in my local network. - External clients can browse http://www.mydomain.com but internal - clients can't.

- + (IP 130.151.100.69) to system 192.168.1.5 in my local network. + External clients can browse http://www.mydomain.com but internal + clients can't. + +

Answer: I have two objections to this setup.

- + + - + +

If you insist on an IP solution to the accessibility problem - rather than a DNS solution, then assuming that your external - interface is eth0 and your internal interface is eth1 and - that eth1 has IP address 192.168.1.254 with subnet 192.168.1.0/24, - do the following:

- + rather than a DNS solution, then assuming that your external + interface is eth0 and your internal interface is eth1 and + that eth1 has IP address 192.168.1.254 with subnet 192.168.1.0/24, + do the following:

+ +

a) In /etc/shorewall/interfaces, specify "multi" as an option - for eth1 (No longer required as of Shorewall version 1.3.9).

- -
+ for eth1 (No longer required as of Shorewall version 1.3.9).

+ + +

b) In /etc/shorewall/rules, add:

-
- -
+
+ + +
- + - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + - + + - +
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATloc:192.168.1.0/24loc:192.168.1.5tcpwww-130.151.100.69:192.168.1.254
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATloc:192.168.1.0/24loc:192.168.1.5tcpwww-130.151.100.69:192.168.1.254
-
-
+ +
- -
+ +

That rule only works of course if you have a static external - IP address. If you have a dynamic IP address and are running - Shorewall 1.3.4 or later then include this in /etc/shorewall/params:

-
- -
+ IP address. If you have a dynamic IP address and are running + Shorewall 1.3.4 or later then include this in /etc/shorewall/params:

+
+ + +
     ETH0_IP=`find_interface_address eth0`
-
- -
+
+ + +

and make your DNAT rule:

-
- -
+
+ + +
- + - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + - + + - +
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATloc:192.168.1.0/24loc:192.168.1.5tcpwww-$ETH0_IP:192.168.1.254
ACTIONSOURCEDESTINATIONPROTOCOLPORTSOURCE PORTORIG. DEST.
DNATloc:192.168.1.0/24loc:192.168.1.5tcpwww-$ETH0_IP:192.168.1.254
-
-
- -
+ +
+ + +

Using this technique, you will want to configure your DHCP/PPPoE - client to automatically restart Shorewall each time that - you get a new IP address.

-
- + client to automatically restart Shorewall each time that + you get a new IP address.

+
+ +

2a. I have a zone "Z" with an RFC1918 - subnet and I use static NAT to assign non-RFC1918 addresses - to hosts in Z. Hosts in Z cannot communicate with each other -using their external (non-RFC1918 addresses) so they can't access -each other using their DNS names.

- + subnet and I use static NAT to assign non-RFC1918 addresses + to hosts in Z. Hosts in Z cannot communicate with each other + using their external (non-RFC1918 addresses) so they can't access + each other using their DNS names. + +

Answer: This is another problem that is best solved - using Bind Version 9 "views". It allows both external and - internal clients to access a NATed host using the host's DNS - name.

- + using Bind Version 9 "views". It allows both external and + internal clients to access a NATed host using the host's DNS + name.

+ +

Another good way to approach this problem is to switch from - static NAT to Proxy ARP. That way, the hosts in Z have + static NAT to Proxy ARP. That way, the hosts in Z have non-RFC1918 addresses and can be accessed externally and internally using the same address.

- + +

If you don't like those solutions and prefer routing all Z->Z traffic through your firewall then:

- + +

a) Specify "multi" on the entry for Z's interface in /etc/shorewall/interfaces - (If you are running a Shorewall version earlier than 1.3.9).
- b) Set the Z->Z policy to ACCEPT.
- c) Masquerade Z to itself.
-
- Example:

- + (If you are running a Shorewall version earlier than 1.3.9).
+ b) Set the Z->Z policy to ACCEPT.
+ c) Masquerade Z to itself.
+
+ Example:

+ +

Zone: dmz
- Interface: eth2
- Subnet: 192.168.2.0/24

- + Interface: eth2
+ Subnet: 192.168.2.0/24

+ +

In /etc/shorewall/interfaces:

- + +
- + - - - - - - - - - - - - - + + + + + + + + + + + + + - + + - +
ZONEINTERFACEBROADCASTOPTIONS
dmzeth2192.168.2.255multi
ZONEINTERFACEBROADCASTOPTIONS
dmzeth2192.168.2.255multi
-
- + + +

In /etc/shorewall/policy:

- + +
- + - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + +
SOURCE DESTINATIONPOLICYLIMIT:BURST
dmzdmzACCEPT
-
SOURCE DESTINATIONPOLICYLIMIT:BURST
dmzdmzACCEPT
+
+
+ - - - - - -

In /etc/shorewall/masq:

- + +
- + - - - - - - - - - - - + + + + + + + + + + + - + + - +
INTERFACE - SUBNETADDRESS
eth2192.168.2.0/24
-
INTERFACE + SUBNETADDRESS
eth2192.168.2.0/24
+
-
- + + +

3. I want to use Netmeeting or MSN Instant - Messenger with Shorewall. What do I do?

- + Messenger with Shorewall. What do I do? + +

Answer: There is an H.323 connection - tracking/NAT module that may help with Netmeeting. Look - here for a solution for MSN - IM but be aware that there are significant security risks involved with + tracking/NAT module that may help with Netmeeting. Look + here for a solution for +MSN IM but be aware that there are significant security risks involved with this solution. Also check the Netfilter mailing list archives -at http://www.netfilter.org. -

+ at http://www.netfilter.org. +

- +

4. I just used an online port scanner - to check my firewall and it shows some ports as 'closed' - rather than 'blocked'. Why?

+ to check my firewall and it shows some ports as 'closed' + rather than 'blocked'. Why? - +

Answer: The common.def included with version 1.3.x - always rejects connection requests on TCP port 113 rather - than dropping them. This is necessary to prevent outgoing - connection problems to services that use the 'Auth' mechanism - for identifying requesting users. Shorewall also rejects TCP - ports 135, 137 and 139 as well as UDP ports 137-139. These are -ports that are used by Windows (Windows can be configured - to use the DCE cell locator on port 135). Rejecting these connection -requests rather than dropping them cuts down slightly on the amount -of Windows chatter on LAN segments connected to the Firewall.

+ always rejects connection requests on TCP port 113 rather + than dropping them. This is necessary to prevent outgoing + connection problems to services that use the 'Auth' mechanism + for identifying requesting users. Shorewall also rejects TCP + ports 135, 137 and 139 as well as UDP ports 137-139. These are + ports that are used by Windows (Windows can be configured + to use the DCE cell locator on port 135). Rejecting these connection + requests rather than dropping them cuts down slightly on the amount + of Windows chatter on LAN segments connected to the Firewall.

- +

If you are seeing port 80 being 'closed', that's probably - your ISP preventing you from running a web server in violation - of your Service Agreement.

+ your ISP preventing you from running a web server in +violation of your Service Agreement.

- +

4a. I just ran an nmap UDP scan of my - firewall and it showed 100s of ports as open!!!!

+ firewall and it showed 100s of ports as open!!!! - +

Answer: Take a deep breath and read the nmap man page - section about UDP scans. If nmap gets nothing back - from your firewall then it reports the port as open. If -you want to see which UDP ports are really open, temporarily -change your net->all policy to REJECT, restart Shorewall and -do the nmap UDP scan again.

+ section about UDP scans. If nmap gets nothing +back from your firewall then it reports the port as open. +If you want to see which UDP ports are really open, temporarily + change your net->all policy to REJECT, restart Shorewall and + do the nmap UDP scan again.

+

5. I've installed Shorewall and now I - can't ping through the firewall

- + can't ping through the firewall + +

Answer: If you want your firewall to be totally open - for "ping":

- + for "ping":

+ +

a) Do NOT specify 'noping' on any interface in /etc/shorewall/interfaces.
- b) Copy /etc/shorewall/icmp.def to /etc/shorewall/icmpdef
- c) Add the following to /etc/shorewall/icmpdef: -

- + b) Copy /etc/shorewall/icmp.def to +/etc/shorewall/icmpdef
+ c) Add the following to /etc/shorewall/icmpdef: +

+ +
- +

run_iptables -A icmpdef -p ICMP --icmp-type echo-request - -j ACCEPT
-

-
- For a complete description of Shorewall 'ping' management, see - this page. - + -j ACCEPT
+

+ + For a complete description of Shorewall 'ping' management, +see this page. +

6. Where are the log messages written - and how do I change the destination?

- + and how do I change the destination? + +

Answer: NetFilter uses the kernel's equivalent of syslog (see "man syslog") to log messages. It always uses the LOG_KERN (kern) facility (see "man openlog") and you get to choose the log level (again, see "man syslog") in your policies and rules. The destination for messaged logged by syslog is controlled by /etc/syslog.conf (see "man syslog.conf"). - When you have changed /etc/syslog.conf, be sure to restart - syslogd (on a RedHat system, "service syslog restart").

- + When you have changed /etc/syslog.conf, be sure to restart + syslogd (on a RedHat system, "service syslog restart").

+ +

By default, older versions of Shorewall ratelimited log messages - through settings in -/etc/shorewall/shorewall.conf -- If you want to log all messages, -set:

- -
+ through settings in + /etc/shorewall/shorewall.conf -- If you want to log all messages, + set:

+ + +
     LOGLIMIT=""
     LOGBURST=""

Beginning with Shorewall version 1.3.12, you can set up Shorewall to log all of its messages to a separate file.
-
- +
+ +

6a. Are there any log parsers that work - with Shorewall?

- + with Shorewall? + +

Answer: Here are several links that may be helpful: -

- +

+ +
- +

http://www.shorewall.net/pub/shorewall/parsefw/
- http://www.fireparse.com
- http://www.fireparse.com
+ http://cert.uni-stuttgart.de/projects/fwlogwatch
- http://www.logwatch.org
- http://gege.org/iptables
-

-
- I personnaly use Logwatch. It emails me a report each day - from my various systems with each report summarizing the logged activity - on the corresponding system. - + http://www.logwatch.org
+ http://gege.org/iptables
+

+ + I personnaly use Logwatch. It emails me a report each +day from my various systems with each report summarizing the logged +activity on the corresponding system. +

6b. DROP messages on port 10619 - are flooding the logs with their connect requests. Can i exclude -these error messages for this port temporarily from logging in Shorewall?

- Temporarily add the following rule:
- + are flooding the logs with their connect requests. Can i exclude + these error messages for this port temporarily from logging in Shorewall? + Temporarily add the following rule:
+ 
	DROP    net    fw    udp    10619
- +

6c. All day long I get a steady flow - of these DROP messages from port 53 to some high numbered port.  They get - dropped, but what the heck are they?

- + of these DROP messages from port 53 to some high numbered port.  They +get dropped, but what the heck are they? + 
Jan  8 15:50:48 norcomix kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC=00:40:c7:2e:09:c0:00:01:64:4a:70:00:08:00
                                                        SRC=208.138.130.16 DST=24.237.22.45 LEN=53 TOS=0x00 PREC=0x00
                                                        TTL=251 ID=8288 DF PROTO=UDP SPT=53 DPT=40275 LEN=33
- Answer: There are two possibilities:
- + Answer: There are two possibilities:
+
    -
  1. They are late-arriving replies to DNS queries.
    2. -
  2. They are corrupted reply packets.
    3. - +
  3. They are late-arriving replies to DNS queries.
    4. +
  4. They are corrupted reply packets.
    5. +
- You can distinguish the difference by setting the logunclean option - (/etc/shorewall/interfaces) -on your external interface (eth0 in the above example). If they get logged -twice, they are corrupted. I solve this problem by using an /etc/shorewall/common - file like this:
- -
+ You can distinguish the difference by setting the logunclean +option (/etc/shorewall/interfaces) + on your external interface (eth0 in the above example). If they get logged + twice, they are corrupted. I solve this problem by using an /etc/shorewall/common + file like this:
+ +
#
# Include the standard common.def file
#
. /etc/shorewall/common.def
#
# The following rule is non-standard and compensates for tardy
# DNS replies
#
run_iptables -A common -p udp --sport 53 -mstate --state NEW -j DROP
-
- The above file is also include in all of my sample configurations available - in the Quick Start Guides.
- -

7. When I stop Shorewall using 'shorewall - stop', I can't connect to anything. Why doesn't that command - work?

- -

The 'stop' command is intended to place your firewall into - a safe state whereby only those hosts listed in /etc/shorewall/routestopped' - are activated. If you want to totally open up your firewall, - you must use the 'shorewall clear' command.

- -

8. When I try to start Shorewall on RedHat, - I get messages about insmod failing -- what's wrong?

- -

Answer: The output you will see looks something like - this:

- -
     /lib/modules/2.4.17/kernel/net/ipv4/netfilter/ip_tables.o: init_module: Device or resource busy
     Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
     /lib/modules/2.4.17/kernel/net/ipv4/netfilter/ip_tables.o: insmod
     /lib/modules/2.4.17/kernel/net/ipv4/netfilter/ip_tables.o failed
     /lib/modules/2.4.17/kernel/net/ipv4/netfilter/ip_tables.o: insmod ip_tables failed
     iptables v1.2.3: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
     Perhaps iptables or your kernel needs to be upgraded.
- -

This is usually cured by the following sequence of commands: -

- -
-
     service ipchains stop
     chkconfig --delete ipchains
     rmmod ipchains
-
- -
-

Also, be sure to check the errata - for problems concerning the version of iptables (v1.2.3) - shipped with RH7.2.

-
- -

- -

9. Why can't Shorewall detect my interfaces - properly?

- +
+ The above file is also include in all of my sample configurations available + in the Quick Start Guides.
+ +

6d. Why is the MAC address in +Shorewall log messages so long? I thought MAC addresses were only 6 bytes +in length. What is labeled as the MAC address in a Shorewall log message +is actually the Ethernet frame header. In contains:
+

+ + Example:
+
+ MAC=00:04:4c:dc:e2:28:00:b0:8e:cf:3c:4c:08:00
-

I just installed Shorewall and when I issue the start command, - I see the following:

+ +

7. When I stop Shorewall using 'shorewall + stop', I can't connect to anything. Why doesn't that command + work?

+ +

The 'stop' command is intended to place your firewall into + a safe state whereby only those hosts listed in /etc/shorewall/routestopped' + are activated. If you want to totally open up your firewall, + you must use the 'shorewall clear' command.

+ + +

8. When I try to start Shorewall on RedHat, + I get messages about insmod failing -- what's wrong?

+ + +

Answer: The output you will see looks something like + this:

+ + +
     /lib/modules/2.4.17/kernel/net/ipv4/netfilter/ip_tables.o: init_module: Device or resource busy
     Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
     /lib/modules/2.4.17/kernel/net/ipv4/netfilter/ip_tables.o: insmod
     /lib/modules/2.4.17/kernel/net/ipv4/netfilter/ip_tables.o failed
     /lib/modules/2.4.17/kernel/net/ipv4/netfilter/ip_tables.o: insmod ip_tables failed
     iptables v1.2.3: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
     Perhaps iptables or your kernel needs to be upgraded.
+ + +

This is usually cured by the following sequence of commands: +

+ +
+
     service ipchains stop
     chkconfig --delete ipchains
     rmmod ipchains
+
+ + +
+

Also, be sure to check the errata + for problems concerning the version of iptables (v1.2.3) + shipped with RH7.2.

+
+ + +

+ +

9. Why can't Shorewall detect my interfaces + properly?

+ + +

I just installed Shorewall and when I issue the start command, + I see the following:

+ + +
     Processing /etc/shorewall/shorewall.conf ...
     Processing /etc/shorewall/params ...
     Starting Shorewall...
     Loading Modules...
     Initializing...
     Determining Zones...
     Zones: net loc
     Validating interfaces file...
     Validating hosts file...
     Determining Hosts in Zones...
     Net Zone: eth0:0.0.0.0/0
     Local Zone: eth1:0.0.0.0/0
     Deleting user chains...
     Creating input Chains...
     ...
-
- -
+
+ + +

Why can't Shorewall detect my interfaces properly?

-
- -
+
+ + +

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

-
+ - +

10. What Distributions does it work with?

- +

Shorewall works with any GNU/Linux distribution that includes - the proper prerequisites.

- + the proper prerequisites.

+

11. What Features does it have?

- +

Answer: See the Shorewall - Feature List.

- -

12. Why isn't there a GUI?

+ Feature List.

+ +

12. Is there a GUI?

- -

Answer: Every time I've started to work on one, I find -myself doing other things. I guess I just don't care enough if Shorewall -has a GUI to invest the effort to create one myself. There are several -Shorewall GUI projects underway however and I will publish links to -them when the authors feel that they are ready.

- + +

Answer: Yes. Shorewall support is included in Webmin +1.060 and later versions. See http://www.webmin.com +

+

13. Why do you call it "Shorewall"?

- +

Answer: Shorewall is a concatenation of "Shoreline" - (the city where - I live) and "Firewall". The full name of the product - is actually "Shoreline Firewall" but "Shorewall" is must more commonly - used.

- + (the city +where I live) and "Firewall". The full name of the +product is actually "Shoreline Firewall" but "Shorewall" is must more +commonly used.

+

14. I'm connected via a cable modem - and it has an internal web server that allows me to configure/monitor - it but as expected if I enable rfc1918 blocking for my eth0 - interface (the internet one), it also blocks the cable modems - web server.

+ and it has an internal web server that allows me to configure/monitor + it but as expected if I enable rfc1918 blocking for my eth0 + interface (the internet one), it also blocks the cable modems + web server. - +

Is there any way it can add a rule before the rfc1918 blocking - that will let all traffic to and from the 192.168.100.1 address - of the modem in/out but still block all other rfc1918 addresses?

+ that will let all traffic to and from the 192.168.100.1 +address of the modem in/out but still block all other rfc1918 +addresses?

- +

Answer: If you are running a version of Shorewall earlier than 1.3.1, create /etc/shorewall/start and in it, place the following:

- -
+ +
     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:

-
- -
+ following to /etc/shorewall/rfc1918:

+
+ + +
- + - - - - - - - - - + + + + + + + + + + + + + +
SUBNET TARGET
192.168.100.1RETURN
SUBNET TARGET
192.168.100.1RETURN
+
+
+ + +
+

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.

-
- + 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:

+
    -
  1. +
  2. - + +

    The default gateway on each local system isn't set to - the IP address of the local firewall interface.

    -
    3. -
  3. + the IP address of the local firewall interface.

    +
    4. +
  4. - + +

    The entry for the local network in the /etc/shorewall/masq - file is wrong or missing.

    -
    5. -
  5. + file is wrong or missing.

    +
    6. +
  6. - + +

    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.

    -
    7. - -
- -

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.
-

- + 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:
+
    -
  1. man1918 - The destination address - is listed in /etc/shorewall/rfc1918 with a logdrop target - -- see /etc/shorewall/rfc1918.
    2. -
  2. rfc1918 - The source address -is listed in /etc/shorewall/rfc1918 with a logdrop target - -- see /etc/shorewall/rfc1918.
    3. -
  3. 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.
    4. +
  4. rfc1918 - The source address + is listed in /etc/shorewall/rfc1918 with a logdrop target + -- see /etc/shorewall/rfc1918.
    5. +
  5. 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.
    -
    6. -
  6. <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.
    7. -
  7. <interface>_mac - The packet is - being logged under the maclist +
  8. <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.
    9. +
  9. <interface>_mac - The packet +is being logged under the maclist interface option.
    -
    10. -
  10. logpkt - The packet is being -logged under the logunclean +
  11. logpkt - The packet is being + logged under the logunclean interface option.
    12. -
  12. 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.
    13. -
  13. 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.
    14. -
  14. 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.
    15. -
  15. 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.
    16. -
  16. 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.
    17. +
  17. 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.
    18. +
  18. logflags - The packet is being logged +because it failed the checks implemented by the tcpflags interface option.
    -
    19. - + +
- +

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

     ACCEPT	net	fw:192.0.2.125	tcp	auth
- Example - 2 (NAT):
-
- /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)

     ACCEPT	net	loc:10.1.1.126	tcp	www
- Example 3 (DNAT):
- + 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?
+ +
+ 
Nov 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 ]
-
- 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.
- + + 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
+

- +
- Last updated 2/3/2003 - Last updated 2/6/2003 - Tom Eastep - +

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 - + - + - + - - - + + - + + - - + +
+
- +

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

    -
  1. An OLD_PING_HANDLING option has been added to shorewall.conf. When +
  2. 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.
    -
    -
    3. -
  3. 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
    -  
    4. -
  4. 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.
    +
    +
    5. +
  5. 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
    +  
    6. +
  6. Support for OpenVPN Tunnels.
    +
    +
    7. +
  7. Support for VLAN devices with names of the form $DEV.$VID (e.g., eth0.0)
    +
    +
    8. +
  8. 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
    -
    9. - +
- +


+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:
+

+ +
    +
  1. 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.
    +
    +
    2. +
  2. 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
    +  
    3. +
  3. 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
    +
    4. + +
+

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. 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,....
    -
    -
    2. -
  2. The 'shorewall check' command now prints out the applicable -policy between each pair of zones.
    -
    -
    3. -
  3. 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.
    -
    -
    4. -
  4. 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.
    -
    5. - -
- -

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:
+

+ +
    +
  1. 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,....
    +
    +
    2. +
  2. The 'shorewall check' command now prints out the applicable + policy between each pair of zones.
    +
    +
    3. +
  3. 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.
    +
    +
    4. +
  4. 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.
    +
    5. + +
+ +

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:
-

- +

+
    -
  1. "shorewall refresh" now reloads the traffic shaping rules -(tcrules and tcstart).
    2. -
  2. "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.
    3. -
  3. "shorewall [re]start" has been speeded up by more than 40% - with my configuration. Your milage may vary.
    4. -
  4. 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"
    5. -
  5. 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.
    6. -
  6. 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).
    7. +
  7. "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.
    8. +
  8. "shorewall [re]start" has been speeded up by more than +40% with my configuration. Your milage may vary.
    9. +
  9. 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"
    10. +
  10. 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.
    11. +
  11. 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.
    12. -
  12. 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.
    13. -
  13. I have added a new RFC1918_LOG_LEVEL variable to +
  14. 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.
    15. +
  15. 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.
    -
    16. - + 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 +

+ 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.
- +

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:
- + 1 was made available only to a limited audience).
+

+ Features include:
+
    -
  1. "shorewall refresh" now reloads the traffic shaping -rules (tcrules and tcstart).
    2. -
  2. "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.
    3. -
  3. "shorewall [re]start" has been speeded up by more than - 40% with my configuration. Your milage may vary.
    4. -
  4. A "shorewall show classifiers" command has been added - which shows the current packet classification filters. The output +
  5. "shorewall refresh" now reloads the traffic shaping + rules (tcrules and tcstart).
    6. +
  6. "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.
    7. +
  7. "shorewall [re]start" has been speeded up by more +than 40% with my configuration. Your milage may vary.
    8. +
  8. 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"
    9. -
  9. 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.
    10. -
  10. 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.
    11. -
  11. I have cluttered up the /etc/shorewall directory with - empty 'init', 'start', 'stop' and 'stopped' files. If you already +
  12. 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.
    13. +
  13. 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.
    14. +
  14. 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.
    15. - +
- You may download the Beta from:
- + 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 Powered by Mandrake Linux -

- Shorewall is at the center of MandrakeSoft's recently-announced -

+ Shorewall is at the center of MandrakeSoft's recently-announced + Multi - Network Firewall (MNF) product. Here is the product. Here is the press - release.
- + 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:

- + - +

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:

- + - +

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!
- +

+ 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 download the Beta from:
- + 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

- Roles up the fix for broken tunnels.
+ 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

+ Roles up the fix for broken tunnels.
+

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:
-

- +

+ - -

9/23/2002 - Full Shorewall Site/Mailing List Archive Search Capability - Restored
-

- Brown Paper Bag - A couple of recent configuration changes - at www.shorewall.net broke the Search facility:
- - -
- -
    -
  1. Mailing List Archive Search was - not available.
    2. -
  2. The Site Search index was incomplete
    3. -
  3. Only one page of matches was presented.
    4. - - -
-
- Hopefully these problems are now corrected. - -

9/23/2002 - Full Shorewall Site/Mailing List Archive Search Capability - Restored
-

- A couple of recent configuration changes - at www.shorewall.net had the negative effect of breaking -the Search facility:
- -
    -
  1. Mailing List Archive Search was -not available.
    2. -
  2. The Site Search index was incomplete
    3. -
  3. Only one page of matches was presented.
    4. - -
- Hopefully these problems are now corrected.
- -

9/18/2002 -  Debian 1.3.8 Packages Available
-

+
  • 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
    +

    + Brown Paper Bag + A couple of recent configuration +changes at www.shorewall.net broke the Search facility:
    + + +
    + +
      +
    1. Mailing List Archive Search +was not available.
      2. +
    2. The Site Search index was incomplete
      3. +
    3. Only one page of matches was +presented.
      4. + + + +
    +
    + Hopefully these problems are now +corrected. +

    9/23/2002 - Full Shorewall Site/Mailing List Archive Search Capability + Restored
    +

    + A couple of recent configuration changes + at www.shorewall.net had the negative effect of breaking + the Search facility:
    + + +
      +
    1. Mailing List Archive Search was + not available.
      2. +
    2. The Site Search index was incomplete
      3. +
    3. Only one page of matches was +presented.
      4. + + +
    + Hopefully these problems are now corrected.
    + + +

    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:
    -

    +

    - + - + - +

    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:

    - + - +

    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:

    - + - +

    7/30/2002 - Shorewall 1.3.5b Released

    - +

    This interim release:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    5/17/2002 - Shorewall 1.3 Beta 1 Available

    - +

    Beta 1 carries the version designation 1.2.90 and implements the following - features:

    + features:

    - + - +

    5/4/2002 - Shorewall 1.2.13 is Available

    - +

    In this version:

    - + - +

    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

    - + - +

    4/17/2002 - Shorewall Debian News

    - +

    Lorenzo Marignoni reports that:

    - + - +

    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:

    - + - +

    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)

    - + - +

    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:

    - + - +

    3/11/2002 - Shorewall 1.2.9 Released

    - +

    In this version:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    1/28/2002 - Shorewall 1.2.4 Released

    - + - +

    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:

    - + - +

    The following problems were corrected:

    - + - +

    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

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    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:

    - + - +

    11/20/2001 - The current version of Shorewall is 1.1.18. 

    - +

    In this version:

    - + - +

    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:

    - + - +

    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:

    - + - +

    10/22/2001 - The current version of Shorewall is 1.1.16. In this - version:

    - - - + version:

    -

    10/15/2001 - The current version of Shorewall is 1.1.15. In this - version:

    - - - -

    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:

    - + + + +

    10/4/2001 - The current version of Shorewall is 1.1.14. In this + version

    + + + - +

    9/12/2001 - The current version of Shorewall is 1.1.13. In this - version

    + version

    - + - +

    8/28/2001 - The current version of Shorewall is 1.1.12. In this - version

    + version

    - + - +

    7/28/2001 - The current version of Shorewall is 1.1.11. In this - version

    + version

    - + - +

    7/6/2001 - The current version of Shorewall is 1.1.10. In this version

    - + - +

    6/23/2001 - The current version of Shorewall is 1.1.9. In this version

    - + - +

    6/18/2001 - The current version of Shorewall is 1.1.8. In this version

    - + - +

    6/2/2001 - The current version of Shorewall is 1.1.7. In this version

    - + - +

    5/25/2001 - The current version of Shorewall is 1.1.6. In this version

    - + - +

    5/20/2001 - The current version of Shorewall is 1.1.5. In this version

    - + - +

    5/10/2001 - The current version of Shorewall is 1.1.4. In this version

    - + - +

    4/28/2001 - The current version of Shorewall is 1.1.3. In this version

    - + - +

    4/12/2001 - The current version of Shorewall is 1.1.2. In this version

    - + - +

    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:

    - + - +

    3/25/2001 - The current version of Shorewall is 1.1.0. In this version:

    - + - +

    3/19/2001 - The current version of Shorewall is 1.0.4. This version:

    - + - +

    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.

    - + - +

    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 - + - - - + + - - - + + + +
    +

    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:

    + - +

    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:

    + - +Dynamic blacklisting is not dependent on the "blacklist" option in +/etc/shorewall/interfaces.
    +

    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 File Basics - + - - - + + - - - -
    - +
    + +

    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.

    - - - -

    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:

    - - - -

    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:
    - - - DNS names may not be used as:
    - - - These restrictions are not imposed by Shorewall simply for -your inconvenience but are rather limitations of iptables.
    - -

    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:

    - - - -

    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 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).
      • + +
    + Examples of invalid DNS names:
    + +
      +
    • mail (not fully qualified)
      • +
    • shorewall.net (only one period)
      • + +
    + DNS names may not be used as:
    + +
      +
    • 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.
      • + +
    + These restrictions are not imposed by Shorewall simply for + your inconvenience but are rather limitations of iptables.
    + +

    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:

    - +
      -
    1. copying the files that need modification from +
    2. copying the files that need modification from /etc/shorewall to a separate directory;
      3. -
    3. modify those files in the separate directory; +
    4. modify those files in the separate directory; and
      5. -
    5. specifying the separate directory in a shorewall - start or shorewall restart command (e.g., shorewall -c /etc/testconfig +
    6. specifying the separate directory in a shorewall + start or shorewall restart command (e.g., shorewall -c /etc/testconfig restart ).
      7. - +
    - -

    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 @@ - + - + - + - + Download - + - - - - - - -
    - -

    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:

    - + - -

    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.

    + +
    - + + + + + + + - - - - - - - - - + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - + +
    SERVER LOCATIONDOMAINHTTPFTP
    SERVER LOCATIONDOMAINHTTPFTP
    SourceForge
    -     		sf.net
    -     		SourceForge
    +     		sf.net
    +     		Download
    -
    -
    Slovak RepublicShorewall.netDownload .rpm
    - Download - .tgz 
    - Download - .lrp
    - - Download.md5sums    		 Download - .rpm  
    - Download - .tgz 
    - Download - .rpm
    - - Download.md5sums
    Texas, USAInfohiiway.comDownload - .rpm
    - Download - .tgz 
    - Download - .lrp
    - - Download.md5sums    		 Download .rpm  
    - Download - .tgz 
    - Download - .lrp
    - - Download.md5sums
    Hamburg, GermanyShorewall.net Download - .rpm
    - Download - .tgz
    - Download - .lrp
    - - Download.md5sums    		 Download - .rpm  
    - Download - .tgz 
    - Download - .lrp
    - Download - .md5sums
    Martinez (Zona Norte - GBA), ArgentinaCorreofuego.com.ar Download - .rpm  
    - Download - .tgz 
    - - Download .lrp
    - Download - .md5sums    		 Download - .rpm  
    - Download - .tgz 
    - - Download .lrp
    - Download - .md5sums
    Paris, FranceShorewall.netDownload .rpm
    - Download -.tgz 
    - Download -.lrp
    - Download - .md5sums    		 Download - .rpm  
    - Download - .tgz 
    - Download - .lrp
    - Download - .md5sums
    Washington State, USA
    -     		Shorewall.net
    -     		Download .rpm
    - Download - .tgz 
    - Download - .lrp
    - Download - .md5sums
    -     		- Download .rpm 
    - Download - .tgz 
    - Download - .lrp
    - Download - .md5sums
    -
    +
    Slovak RepublicShorewall.netDownload .rpm
    + Download + .tgz 
    + Download + .lrp
    + + Download.md5sums    		 Download + .rpm  
    + Download + .tgz 
    + Download + .rpm
    + + Download.md5sums
    Texas, USAInfohiiway.comDownload + .rpm
    + Download + .tgz 
    + Download + .lrp
    + + Download.md5sums    		 Download .rpm  
    + Download + .tgz 
    + Download + .lrp
    + + Download.md5sums
    Hamburg, GermanyShorewall.net Download + .rpm
    + Download + .tgz
    + Download + .lrp
    + + Download.md5sums    		 Download + .rpm  
    + Download + .tgz 
    + Download + .lrp
    + Download + .md5sums
    Martinez (Zona Norte - GBA), ArgentinaCorreofuego.com.ar Download + .rpm  
    + Download + .tgz 
    + + Download .lrp
    + Download + .md5sums    		 Download + .rpm  
    + Download + .tgz 
    + + Download .lrp
    + Download + .md5sums
    Paris, FranceShorewall.netDownload .rpm
    + Download .tgz 
    + Download .lrp
    + Download + .md5sums    		 Download + .rpm  
    + Download + .tgz 
    + Download + .lrp
    + Download + .md5sums
    Washington State, USA
    +     		Shorewall.net
    +     		Download .rpm
    + Download + .tgz 
    + Download + .lrp
    + Download + .md5sums
    +     		+ Download .rpm 
    + Download + .tgz 
    + Download + .lrp
    + Download + .md5sums
    +
    -
    - +
    +

    Browse Download Sites:

    - -
    + +
    - - - - - - - - - - - + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - + +
    SERVER LOCATIONDOMAINHTTPFTP
    SourceForge
    -     		sf.net +
    SERVER LOCATIONDOMAINHTTPFTP
    SourceForge
    +     		sf.netBrowseN/A
    Slovak RepublicShorewall.netBrowse Browse
    Texas, USAInfohiiway.comBrowseBrowse
    Hamburg, GermanyShorewall.netBrowseBrowse
    Martinez (Zona Norte - GBA), ArgentinaCorreofuego.com.arBrowse Browse
    FranceShorewall.netBrowse Browse
    N/A
    Washington State, USAShorewall.netBrowseBrowseSlovak RepublicShorewall.netBrowse Browse
    Texas, USAInfohiiway.comBrowseBrowse
    Hamburg, GermanyShorewall.netBrowseBrowse
    Martinez (Zona Norte - GBA), ArgentinaCorreofuego.com.arBrowse Browse
    FranceShorewall.netBrowse Browse
    Washington State, USAShorewall.netBrowseBrowse
    -
    - +
    +

    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 1.3 Errata - + - + - + - + - - - + + - - - + + + + +
    +
    - +

    Shorewall Errata/Upgrade Issues

    -
    - +

    IMPORTANT

    - +
      -
    1. - -

      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.

      -
      2. -
    2. - -

      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.

      -
      3. -
    3. - -

      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.

      -
      4. -
    4. -

      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.
      -

      -
      5. - +
    5. + +

      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.

      +
      6. +
    6. + +

      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.

      +
      7. +
    7. + +

      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.

      +
      8. +
    8. + +

      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.
      +

      +
      9. +
    - + - -
    + +

    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.
      -
      • - -
    - Both problems are 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.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

    + + +

    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")
      -
      • - -
    - 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:

    - -
      -
    1. If the firewall is -running a DHCP server, the client -won't be able to obtain an IP address - lease from that server.
      2. -
    2. 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.
      3. - -
    - - -

    - 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:

      + +
        +
      1. If the firewall is +running a DHCP server, the client +won't be able to obtain an IP address + lease from that server.
        2. +
      2. 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.
        3. + +
      - -

      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
    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:
    - + Error message is:
    + 
    Setting up NAT...
    iptables: Invalid argument
    Terminated

    - 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 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    
    + + + - - + +
    +
    - +

    Vexira Logo -

    + - - + +

     

    -     		- + +

    Shorewall Mailing Lists

    -     		+ (Postfix Logo) -
    - +
    + -
    - + +
    +

    -
    - 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:
    +

    +
      -
    1. against Spamassassin - (including Vipul's Razor).
      -
      2. -
    2. to ensure that the sender address is fully qualified.
      3. -
    3. to verify that the sender's domain has an A or MX record - in DNS.
      4. -
    4. to ensure that the host name in the HELO/EHLO command +
    5. against Spamassassin + (including Vipul's Razor).
      +
      6. +
    6. to ensure that the sender address is fully qualified.
      7. +
    7. to verify that the sender's domain has an A or MX record + in DNS.
      8. +
    8. to ensure that the host name in the HELO/EHLO command is a valid fully-qualified DNS name that resolves.
      9. - +
    - +

    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.
    -

    + 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.
    +

    +

    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

    - -
    - -

    Match: - + + + +

    Match: + - Format: - + Format: + - Sort by: - + Sort by: + -
    - 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.
    -

    - + + +

    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:
    -

    - - - -

    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:
    -

    - -

    - - - -


    - 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:

    - + + +

    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:
    +

    + +

    + + + +


    + 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:
    +

    + + - +

    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?

    - +

    Check out these instructions

    - +

    Last updated 2/3/2003 - Tom Eastep

    - -

    Copyright -© 2001, 2002, 2003 Thomas M. Eastep.
    -

    + href="http://www.shorewall.net/support.htm">Tom 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 @@ - + Shorewall Port Information - + - + - + - - - + + - - - + + + +
    -

    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_conntrack_ftp ports=21,49
    - loadmodule ip_nat_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:
    -

    - -
    +

    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_conntrack_ftp ports=21,49
    - options ip_nat_ftp ports=21,49
    -

    -
    -
    - + options ip_nat_ftp ports=21,49
    +

    +
    +
    +

    SMB/NMB (Samba/Windows Browsing/File Sharing)

    - +
    - -
    + +

    TCP Ports 137, 139 and 445.
    - UDP Ports 137-139.
    -
    - Also, see this page.

    -
    - + UDP Ports 137-139.
    +
    + 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 @@ - + + Shoreline Firewall (Shorewall) 1.3 @@ -13,22 +14,23 @@ - + + - + + - + - + - + + + + + + + + + +
    + @@ -37,15 +39,15 @@ - +

    Shorwall Logo - Shorewall - 1.3 - "iptables -made easy"

    + 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.
    - 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

    @@ -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 - +

    - 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: 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!!!
    -

    + +

    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 (New) -

    + -

    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/Beta
    -
    - -

    1/28/2003 - Shorewall 1.3.14-Beta2 (New) -

    - -

    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 2/8/2003 - Shoreawll 1.3.14 (New) -  
    -

    - -

    The Beta includes the following changes:
    -

    - +

    + +

    New features include

    +
      -
    1. 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.
      -
      -
      2. -
    2. 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
      -  
      3. -
    3. 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
      -
      4. - -
    - The beta may be downloaded from:
    - -
    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:
    -

    - -
      -
    1. 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,....
      -
      -
      2. -
    2. The 'shorewall check' command now prints out the applicable - policy between each pair of zones.
      -
      -
      3. -
    3. 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.
      -
      -
      4. -
    4. 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.
      -
      5. - -
    - -

    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:
    -

    - - -
      -
    1. "shorewall refresh" now reloads the traffic -shaping rules (tcrules and tcstart).
      2. -
    2. "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.
      3. -
    3. "shorewall [re]start" has been speeded up by -more than 40% with my configuration. Your milage may vary.
      4. -
    4. 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"
      5. -
    5. 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.
      6. -
    6. 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.
      7. -
    7. 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.
      8. -
    8. 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.
      -
      9. - - -
    - - -

    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 to a limited audience). -
    -
    - Features include:
    -
    - - - -
      -
    1. "shorewall refresh" now reloads the traffic - shaping rules (tcrules and tcstart).
      2. -
    2. "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.
      3. -
    3. "shorewall [re]start" has been speeded -up by more than 40% with my configuration. Your milage may vary.
      4. -
    4. 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"
      5. -
    5. 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.
      6. -
    6. 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.
      7. -
    7. 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.
      8. - - +
    8. 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.
      +
      +
      9. +
    9. 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
      +  
      10. +
    10. Support for OpenVPN Tunnels.
      +
      +
      11. +
    11. Support for VLAN devices with names of the form $DEV.$VID (e.g., +eth0.0)
      +
      +
      12. +
    12. 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
      +
    - 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 Powered by Mandrake Linux -

    - Shorewall is at the center of MandrakeSoft's recently-announced - Multi - Network Firewall (MNF) product. Here is the press - release.
    - - - -

    12/7/2002 - Shorewall Support for Mandrake 9.0 -

    - - - -

    Two months and 3 days after I pre-ordered Mandrake 9.0, it was finally - delivered. I have installed 9.0 on one of my systems and I am - now in a position to support Shorewall users who run Mandrake 9.0.

    - - - -

    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 + (New) +

    + Webmin version 1.060 now has Shorewall support included as standard. See + http://www.webmin.com. -

    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
      • - +
    - +

    More News

    @@ -680,40 +349,40 @@ command is now compatible with bash clones such as ash and dash.Donations -     		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 - + - - - + + - - - + + + +
    +

    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): - -
      • -
    • 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 - -
      • -
    • Support for Traffic Control/Shaping - integration.
      • -
    • Wide support for different GNU/Linux Distributions. + - -

      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 @@ - + +

      Shorwall Logo - Shorewall - 1.3 - "iptables - made easy" -

      + Shorewall + 1.3 - "iptables + made easy" + @@ -58,34 +59,34 @@ + + +
      - -
      - -
      - + +
      + +
      + - + - + - - - - - - - - - - - - - -
      + @@ -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

      - + +

      - 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!!!
      -       + 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 (New) -

      - -

      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/Beta
      - -

      -

      1/28/2003 - Shorewall 1.3.14-Beta2 (New) -

      - -

      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 (New) -  
      -

      - -

      The Beta includes the following changes:
      -

      - +

      + +

      New features include

      +
        -
      1. 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 +
      2. 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.

        3. -
      3. 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:
        +
      4. 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
         
        5. -
      5. 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:
        +
      6. Support for OpenVPN Tunnels.
        +
        +
        7. +
      7. Support for VLAN devices with names of the form $DEV.$VID (e.g., +eth0.0)
        +
        +
        8. +
      8. 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
           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 + + 
           [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
        -
        9. - +
      - The beta may be downloaded from:
      - -
      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 (New) -
      -

      - -

      Just includes a few things that I had on the burner:
      -

      - -
        -
      1. 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,....
        -
        -
        2. -
      2. The 'shorewall check' command now prints out the applicable - policy between each pair of zones.
        -
        -
        3. -
      3. 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.
        -
        -
        4. -
      4. 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.
        5. - -
      - -

      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:
      -

      - - -
        -
      1. "shorewall refresh" now reloads the traffic shaping - rules (tcrules and tcstart).
        2. -
      2. "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.
        3. -
      3. "shorewall [re]start" has been speeded up by -more than 40% with my configuration. Your milage may vary.
        4. -
      4. 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"
        5. -
      5. 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.
        6. -
      6. 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.
        7. -
      7. 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.
        8. -
      8. 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.
        9. - - -
      - - -

      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:
      -
      - - - -
        -
      1. "shorewall refresh" now reloads the traffic - shaping rules (tcrules and tcstart).
        2. -
      2. "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.
        3. -
      3. "shorewall [re]start" has been speeded up - by more than 40% with my configuration. Your milage may vary.
        4. -
      4. 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"
        5. -
      5. 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.
        6. -
      6. 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.
        7. -
      7. 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.
        8. - - - -
      - 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 Powered by Mandrake Linux -

      - 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 + (New) +

      + 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. - - - - - - - -

        More News

        - - - - - - - - - - - -

        - - - - - -

        SourceForge Logo -

        - - - - - -

        - - - - - -

        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

      + + + + + + + + + + + + +

      + + + + + +

      SourceForge Logo +

      + + + + + +

      + + + + + +

      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. +

      - +

      - + - +

      - +
        -
      • 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 The Errata has links to download updated components.
        • - +
      - +

      - +
        -
      • 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

      - +
      - +

      Match: - + - Format: - + Format: + - Sort by: - + Sort by: + -
      - 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."
      -
      - -
      - Russell Mosemann on the Postfix mailing list
      -
      -
      - -

      - -
        -
      • 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 ping failure 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.

        -
        • - -
      - The author gratefully acknowleges that the above list was heavily -plagiarized from the excellent LEAF document by Ray Olszewski -found at http://leaf-project.org/pub/doc/docmanager/docid_1891.html.
      - -

      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.
      +
      +
      - Russell Mosemann on the Postfix mailing list
      +
      +
      + +

      + +
        +
      • 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 ping failure 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.

        +
        • + +
      + The author gratefully acknowleges that the above list was heavily + plagiarized from the excellent LEAF document by Ray Olszewski + found at http://leaf-project.org/pub/doc/docmanager/docid_1891.html.
      + +

      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

      - -
      + +

      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.

      -
      + 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.
      -

      +

      +
      +

      -
      -
      +
      +