2002-09-16 19:13:39 +02:00
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
< html >
< head >
2003-02-20 00:21:55 +01:00
2002-09-29 23:42:38 +02:00
< meta http-equiv = "Content-Type"
content="text/html; charset=windows-1252">
2002-09-16 19:13:39 +02:00
< title > Upgrade Issues< / title >
2003-02-20 00:21:55 +01:00
2002-09-16 19:13:39 +02:00
< meta name = "GENERATOR" content = "Microsoft FrontPage 5.0" >
2003-02-20 00:21:55 +01:00
2003-01-31 22:50:51 +01:00
< meta name = "ProgId" content = "FrontPage.Editor.Document" >
2003-02-20 00:21:55 +01:00
2002-09-16 19:13:39 +02:00
< meta name = "Microsoft Theme" content = "none" >
< / head >
2002-09-29 23:42:38 +02:00
< body >
2003-02-20 00:21:55 +01:00
2002-09-29 23:42:38 +02:00
< table border = "0" cellpadding = "0" cellspacing = "0"
style="border-collapse: collapse;" width="100%" id="AutoNumber1"
bgcolor="#400169" height="90">
2003-02-20 00:21:55 +01:00
< tbody >
< tr >
< td width = "100%" >
2002-09-29 23:42:38 +02:00
< h1 align = "center" > < font color = "#ffffff" > Upgrade Issues< / font > < / h1 >
2003-02-20 00:21:55 +01:00
< / td >
< / tr >
< / tbody >
2002-09-29 23:42:38 +02:00
< / table >
2003-02-20 00:21:55 +01:00
2002-09-29 23:42:38 +02:00
< p > For upgrade instructions see the < a
href="Install.htm">Install/Upgrade page< / a > .< / p >
2003-02-20 00:21:55 +01:00
< h3 > < / h3 >
2003-01-31 22:50:51 +01:00
2003-02-20 00:21:55 +01:00
< h3 > Version > = 1.4.0< / h3 >
If you are upgrading from a version < 1.4.0, then:< br >
2003-01-31 22:50:51 +01:00
< ul >
2003-02-20 00:21:55 +01:00
< li > The < b > noping < / b > and < b > forwardping< / b > interface options are no
longer supported nor is the < b > FORWARDPING < / b > option in shorewall.conf. ICMP
echo-request (ping) packets are treated just like any other connection request
and are subject to rules and policies.< / li >
< li > Interface names of the form < device> :< integer> in /etc/shorewall/interfaces
now generate a Shorewall error at startup (they always have produced warnings
in iptables).< / li >
< li > The MERGE_HOSTS variable has been removed from shorewall.conf. Shorewall
1.4 behaves like 1.3 did when MERGE_HOSTS=Yes; that is zone contents are
determined by BOTH the interfaces and hosts files when there are entries
for the zone in both files.< / li >
< li > The < b > routestopped< / b > option in the interfaces and hosts file has
been eliminated; use entries in the routestopped file instead.< / li >
< li > The Shorewall 1.2 syntax for DNAT and REDIRECT rules is no longer
accepted; you must convert to using the new syntax.< / li >
< li value = "6" > The ALLOWRELATED variable in shorewall.conf is no longer
supported. Shorewall 1.4 behavior is the same as 1.3 with ALLOWRELATED=Yes.< / li >
< li value = "6" > Late-arriving DNS replies are not dropped by default; there
is no need for your own /etc/shorewall/common file simply to avoid logging
these packets.< / li >
< li value = "6" > The 'firewall', 'functions' and 'version' file have been
moved to /usr/share/shorewall.< / li >
< li value = "6" > The icmp.def file has been removed. If you include it from
/etc/shorewall/icmpdef, you will need to modify that file.< / li >
< li value = "8" > The 'multi' interface option is no longer supported. <20> Shorewall
will generate rules for sending packets back out the same interface that they
arrived on in two cases:< / li >
2003-01-31 22:50:51 +01:00
< / ul >
2003-02-20 00:21:55 +01:00
< ul >
< ul >
< li > There is an < u > explicit< / u > policy for the source zone to or from
the destination zone. An explicit policy names both zones and does not use
the 'all' reserved word.< / li >
< / ul >
< ul >
< li > There are one or more rules for traffic for the source zone to or
from the destination zone including rules that use the 'all' reserved word.
Exception: if the source zone and destination zone are the same then the rule
must be explicit - it must name the zone in both the SOURCE and DESTINATION
columns.< / li >
< / ul >
< / ul >
< ul >
< / ul >
< h3 > Version > = 1.3.14< / h3 >
< img src = "images/BD21298_3.gif" alt = "" width = "13" height = "13" >
<20> <> <20> Beginning in version 1.3.14, Shorewall treats entries in < a
href="Documentation.htm#Masq">/etc/shorewall/masq < / a > differently. The change
involves entries with an < b > interface name< / b > in the < b > SUBNET< / b > (second)
< b > column< / b > :< br >
< ul >
< li > Prior to 1.3.14, Shorewall would detect the FIRST subnet on the
interface (as shown by "ip addr show < i > interface< / i > ") and would masquerade
traffic from that subnet. Any other subnets that routed through eth1 needed
their own entry in /etc/shorewall/masq to be masqueraded or to have SNAT
applied.< / li >
< li > Beginning with Shorewall 1.3.14, Shorewall uses the firewall's
routing table to determine ALL subnets routed through the named interface.
Traffic originating in ANY of those subnets is masqueraded or has SNAT
applied.< / li >
< / ul >
You will need to make a change to your configuration if:< br >
2003-01-31 22:50:51 +01:00
< ol >
2003-02-20 00:21:55 +01:00
< li > You have one or more entries in /etc/shorewall/masq with an interface
name in the SUBNET (second) column; and< / li >
< li > That interface connects to more than one subnetwork.< / li >
2003-01-31 22:50:51 +01:00
< / ol >
2003-02-20 00:21:55 +01:00
Two examples:< br >
< br >
<20> < b > Example 1< / b > -- Suppose that your current config is as follows:< br >
<20> <> < br >
2003-01-31 22:50:51 +01:00
< pre > [root@gateway test]# cat /etc/shorewall/masq< br > #INTERFACE<43> <45> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> SUBNET<45> <54> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> ADDRESS< br > eth0<68> <30> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> eth2<68> <32> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> 206.124.146.176< br > eth0<68> <30> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> 192.168.10.0/24<32> <34> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> 206.124.146.176< br > #LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE< br > [root@gateway test]# ip route show dev eth2< br > 192.168.1.0/24<32> scope link< br > 192.168.10.0/24<32> proto kernel<65> scope link<6E> src 192.168.10.254< br > [root@gateway test]#< / pre >
2003-02-20 00:21:55 +01:00
< blockquote > In this case, the second entry in /etc/shorewall/masq is no longer
required.< br >
< / blockquote >
< b > Example 2< / b > -- What if your current configuration is like this?< br >
2003-01-31 22:50:51 +01:00
< pre > [root@gateway test]# cat /etc/shorewall/masq < br > #INTERFACE<43> <45> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> SUBNET<45> <54> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> ADDRESS < br > eth0<68> <30> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> eth2<68> <32> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> 206.124.146.176< br > #LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE < br > [root@gateway test]# ip route show dev eth2 < br > 192.168.1.0/24<32> scope link< br > 192.168.10.0/24<32> proto kernel<65> scope link<6E> src 192.168.10.254 < br > [root@gateway test]#< / pre >
2003-02-20 00:21:55 +01:00
< blockquote > In this case, you would want to change the entry in /etc/shorewall/masq
to:< br >
< / blockquote >
2003-01-31 22:50:51 +01:00
< pre > #INTERFACE<43> <45> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> SUBNET<45> <54> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> ADDRESS < br > eth0<68> <30> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> 192.168.1.0/24<32> <34> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> 206.124.146.176< br > #LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE< / pre >
2003-02-20 00:21:55 +01:00
< img src = "images/BD21298_3.gif" alt = "" width = "13" height = "13" >
<20> <> <EFBFBD> Version 1.3.14 also introduced simplified ICMP echo-request (ping)
handling. The option OLD_PING_HANDLING=Yes in /etc/shorewall/shorewall.conf
is used to specify that the old (pre-1.3.14) ping handling is to be used
(If the option is not set in your /etc/shorewall/shorewall.conf then OLD_PING_HANDLING=Yes
is assumed). I don't plan on supporting the old handling indefinitely so
I urge current users to migrate to using the new handling as soon as possible.
See the < a href = "ping.html" > 'Ping' handling documentation< / a > for details.< br >
2002-11-09 19:06:34 +01:00
< h3 > Version 1.3.10< / h3 >
2003-02-20 00:21:55 +01:00
If you have installed the 1.3.10 Beta 1 RPM and are now upgrading to
version 1.3.10, you will need to use the '--force' option:< br >
< br >
< blockquote >
2002-11-09 19:06:34 +01:00
< pre > rpm -Uvh --force shorewall-1.3.10-1.noarch.rpm<70> < / pre >
2003-02-20 00:21:55 +01:00
< / blockquote >
2003-01-31 22:50:51 +01:00
< h3 > Version > = 1.3.9< / h3 >
2003-02-20 00:21:55 +01:00
The 'functions' file has moved to /usr/lib/shorewall/functions. If
you have an application that uses functions from that file, your application
will need to be changed to reflect this change of location.< br >
2002-09-29 23:42:38 +02:00
< h3 > Version > = 1.3.8< / h3 >
2003-02-20 00:21:55 +01:00
< p > If you have a pair of firewall systems configured for failover
or if you have asymmetric routing, you will need to modify
2003-01-31 22:50:51 +01:00
your firewall setup slightly under Shorewall
2003-02-20 00:21:55 +01:00
versions > = 1.3.8. Beginning with version 1.3.8,
you must set NEWNOTSYN=Yes in your
2002-11-09 19:06:34 +01:00
/etc/shorewall/shorewall.conf file.< / p >
2003-02-20 00:21:55 +01:00
2002-09-29 23:42:38 +02:00
< h3 > Version > = 1.3.7< / h3 >
2003-02-20 00:21:55 +01:00
< p > Users specifying ALLOWRELATED=No in /etc/shorewall.conf
will need to include the following rules
in their /etc/shorewall/icmpdef file (creating
this file if necessary):< / p >
2002-09-29 23:42:38 +02:00
< pre > run_iptables -A icmpdef -p ICMP --icmp-type echo-reply -j ACCEPT< br > run_iptables -A icmpdef -p ICMP --icmp-type source-quench -j ACCEPT< br > run_iptables -A icmpdef -p ICMP --icmp-type destination-unreachable -j ACCEPT< br > run_iptables -A icmpdef -p ICMP --icmp-type time-exceeded -j ACCEPT< br > run_iptables -A icmpdef -p ICMP --icmp-type parameter-problem -j ACCEPT< / pre >
2003-02-20 00:21:55 +01:00
< p > Users having an /etc/shorewall/icmpdef file may remove the ". /etc/shorewall/icmp.def"
command from that file since the icmp.def file is now empty.< / p >
< h3 > < b > < a name = "Bering" > Upgrading < / a > Bering to
Shorewall > = 1.3.3< / b > < / h3 >
< p > To properly upgrade with Shorewall version
1.3.3 and later:< / p >
2002-09-29 23:42:38 +02:00
< ol >
2003-02-20 00:21:55 +01:00
< li > Be sure you have a backup --
you will need to transcribe any Shorewall
configuration changes that you have made
to the new configuration.< / li >
< li > Replace the shorwall.lrp package
provided on the Bering floppy with the
later one. If you did not obtain the
later version from Jacques's site, see
additional instructions below.< / li >
< li > Edit the /var/lib/lrpkg/root.exclude.list
file and remove the /var/lib/shorewall
entry if present. Then do not forget to
backup root.lrp !< / li >
2002-09-16 19:13:39 +02:00
< / ol >
2003-02-20 00:21:55 +01:00
< p > The .lrp that I release isn't set up for a two-interface firewall like
Jacques's. You need to follow the < a href = "two-interface.htm" > instructions
for setting up a two-interface firewall< / a > plus you also need to add
the following two Bering-specific rules to /etc/shorewall/rules:< / p >
< blockquote >
2002-09-29 23:42:38 +02:00
< pre > # Bering specific rules:< br > # allow loc to fw udp/53 for dnscache to work< br > # allow loc to fw tcp/80 for weblet to work< br > #< br > ACCEPT loc fw udp 53< br > ACCEPT loc fw tcp 80< / pre >
2003-02-20 00:21:55 +01:00
< / blockquote >
2002-09-29 23:42:38 +02:00
< h3 align = "left" > Version 1.3.6 and 1.3.7< / h3 >
2003-02-20 00:21:55 +01:00
< p align = "left" > If you have a pair of firewall systems configured for
failover or if you have asymmetric routing, you will need to modify
your firewall setup slightly under Shorewall versions 1.3.6
and 1.3.7< / p >
2002-09-29 23:42:38 +02:00
< ol >
2003-02-20 00:21:55 +01:00
< li >
< p align = "left" > Create the file /etc/shorewall/newnotsyn and in it add
the following rule< br >
< br >
< font face = "Courier" > run_iptables -A newnotsyn -j RETURN
# So that the connection tracking table can be rebuilt< br >
<20> <> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> # from non-SYN packets
after takeover.< br >
<20> < / font > < / p >
< / li >
< li >
< p align = "left" > Create /etc/shorewall/common (if you don't already
have that file) and include the following:< br >
< br >
< font face = "Courier" > run_iptables -A common -p tcp --tcp-flags
ACK,FIN,RST ACK -j ACCEPT #Accept Acks to rebuild connection< br >
<20> <> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD>
#tracking table. < br >
. /etc/shorewall/common.def< / font > < / p >
< / li >
2002-09-29 23:42:38 +02:00
< / ol >
2003-02-20 00:21:55 +01:00
2002-09-29 23:42:38 +02:00
< h3 align = "left" > Versions > = 1.3.5< / h3 >
2003-02-20 00:21:55 +01:00
< p align = "left" > Some forms of pre-1.3.0 rules file syntax are no
longer supported. < / p >
2002-09-29 23:42:38 +02:00
< p align = "left" > Example 1:< / p >
2003-02-20 00:21:55 +01:00
< div align = "left" >
2002-09-29 23:42:38 +02:00
< pre > ACCEPT net loc:192.168.1.12:22 tcp 11111 - all< / pre >
2003-02-20 00:21:55 +01:00
< / div >
2002-09-29 23:42:38 +02:00
< p align = "left" > Must be replaced with:< / p >
2003-02-20 00:21:55 +01:00
< div align = "left" >
2002-09-29 23:42:38 +02:00
< pre > DNAT net loc:192.168.1.12:22 tcp 11111< / pre >
2003-02-20 00:21:55 +01:00
< / div >
< div align = "left" >
2002-09-29 23:42:38 +02:00
< p align = "left" > Example 2:< / p >
2003-02-20 00:21:55 +01:00
< / div >
< div align = "left" >
2003-01-31 22:50:51 +01:00
< pre > ACCEPT loc fw::3128 tcp 80 - all< / pre >
2003-02-20 00:21:55 +01:00
< / div >
< div align = "left" >
2002-09-29 23:42:38 +02:00
< p align = "left" > Must be replaced with:< / p >
2003-02-20 00:21:55 +01:00
< / div >
< div align = "left" >
2003-01-31 22:50:51 +01:00
< pre > REDIRECT loc 3128 tcp 80< / pre >
2003-02-20 00:21:55 +01:00
< / div >
2002-09-29 23:42:38 +02:00
< h3 align = "left" > Version > = 1.3.2< / h3 >
2003-02-20 00:21:55 +01:00
< p align = "left" > The functions and versions files together with the
'firewall' symbolic link have moved from /etc/shorewall to /var/lib/shorewall.
If you have applications that access these files, those applications
should be modified accordingly.< / p >
< p > < font size = "2" > Last updated 2/14/2003 -
< a href = "support.htm" > Tom Eastep< / a > < / font > < / p >
< p > < font face = "Trebuchet MS" > < a href = "copyright.htm" > < font size = "2" > Copyright< / font >
<20> < font size = "2" > 2001, 2002, 2003 Thomas M. Eastep.< / font > < / a > < / font > < br >
< / p >
< br >
< br >
< br >
2003-01-31 22:50:51 +01:00
< br >
< br >
2002-09-16 19:13:39 +02:00
< / body >
2002-09-29 23:42:38 +02:00
< / html >
