mirror of
https://gitlab.com/shorewall/code.git
synced 2024-11-27 18:13:13 +01:00
The bugs just keep on coming...
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1238 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
a73b86063e
commit
afa37f6713
@ -32,3 +32,7 @@ Changes since 2.0.0
|
||||
15) Tighten edits on bridge port names.
|
||||
|
||||
16) Make 'routeback' on interfaces work again.
|
||||
|
||||
17) Reduce useless intra-zone rules on bridges.
|
||||
|
||||
18) Make 'routeback' on hosts work again.
|
||||
|
@ -739,7 +739,8 @@ validate_hosts_file() {
|
||||
hosts=${hosts#*:}
|
||||
|
||||
eval ports=\$${iface}_ports
|
||||
|
||||
eval zports=\$${z}_ports
|
||||
|
||||
for host in $(separate_list $hosts); do
|
||||
|
||||
[ -n "$BRIDGING" ] && case $host in
|
||||
@ -748,6 +749,7 @@ validate_hosts_file() {
|
||||
startup_error "Bridged interfaces may not be defined in /etc/shorewall/interfaces: $host"
|
||||
port=${host%%:*}
|
||||
list_search $port $ports || ports="$ports $port"
|
||||
list_search ${interface}:${port} $zports || zports="$zports ${interface}:${port}"
|
||||
;;
|
||||
*.*.*.*)
|
||||
;;
|
||||
@ -755,12 +757,13 @@ validate_hosts_file() {
|
||||
known_interface $host && \
|
||||
startup_error "Bridged interfaces may not be defined in /etc/shorewall/interfaces: $host"
|
||||
list_search $host $ports || ports="$ports $host"
|
||||
list_search ${interface}:${host} $zports || zports="$zports ${interface}:${host}"
|
||||
;;
|
||||
esac
|
||||
|
||||
for option in $(separate_list $options) ; do
|
||||
case $option in
|
||||
maclist|routeback|norfc1918|nobogons|blacklist|tcpflags|nosmurfs|newnotsyn|-)
|
||||
maclist|norfc1918|nobogons|blacklist|tcpflags|nosmurfs|newnotsyn|-)
|
||||
;;
|
||||
routeback)
|
||||
[ -z "$ports" ] && \
|
||||
@ -775,6 +778,7 @@ validate_hosts_file() {
|
||||
|
||||
if [ -n "$ports" ]; then
|
||||
eval ${iface}_ports=\"$ports\"
|
||||
eval ${z}_ports=\"$zports\"
|
||||
fi
|
||||
|
||||
done < $TMP_DIR/hosts
|
||||
@ -5069,23 +5073,38 @@ activate_rules()
|
||||
echo "$zone $zone1 $chain" >> ${STATEDIR}/chains
|
||||
|
||||
if [ $zone = $zone1 ]; then
|
||||
#
|
||||
# Try not to generate superfluous intra-zone rules
|
||||
#
|
||||
eval routeback=\"\$${zone}_routeback\"
|
||||
eval interfaces=\"${zone}_interfaces\"
|
||||
eval interfaces=\"\$${zone}_interfaces\"
|
||||
eval ports="\$${zone}_ports"
|
||||
|
||||
num_ifaces=$(list_count1 $interfaces)
|
||||
|
||||
#
|
||||
# If the zone has a single interface then what matters is how many ports it has
|
||||
#
|
||||
[ $num_ifaces -eq 1 -a -n "$ports" ] && num_ifaces=$(list_count1 $ports)
|
||||
#
|
||||
# If we don't need to route back and if we have only one interface or one port to
|
||||
# the zone then assume that hosts in the zone can communicate directly.
|
||||
#
|
||||
if [ $num_ifaces -lt 2 -a -z "$routeback" ] ; then
|
||||
continue
|
||||
fi
|
||||
else
|
||||
routeback=
|
||||
num_ifaces=0
|
||||
fi
|
||||
|
||||
if [ -n "$complex" ]; then
|
||||
for host1 in $dest_hosts; do
|
||||
interface1=${host1%%:*}
|
||||
networks1=${host1#*:}
|
||||
|
||||
#
|
||||
# Only generate an intrazone rule if the zone has more than one interface (port) or if
|
||||
# routeback was specified for this host group
|
||||
#
|
||||
if [ $zone != $zone1 -o $num_ifaces -gt 1 ] || list_search $host1 $routeback ; then
|
||||
run_iptables -A $frwd_chain -o $interface1 $(match_dest_hosts $networks1) -j $chain
|
||||
fi
|
||||
|
@ -1,4 +1,4 @@
|
||||
Shorewall 2.0.1-RC4
|
||||
Shorewall 2.0.1-RC5
|
||||
|
||||
----------------------------------------------------------------------
|
||||
Problems Corrected since 2.0.0
|
||||
@ -13,9 +13,9 @@ Problems Corrected since 2.0.0
|
||||
3) Thanks to Sean Mathews, a long-standing problem with Proxy ARP and
|
||||
IPSEC has been corrected. Thanks Sean!!!
|
||||
|
||||
Problems Corrected since 2.0.1 RC3
|
||||
Problems Corrected since 2.0.1 RC4
|
||||
|
||||
1) The 'routeback' interface option now works again.
|
||||
1) The 'routeback' hosts option now works again.
|
||||
|
||||
-----------------------------------------------------------------------
|
||||
Issues when migrating from Shorewall 2.0.0 to Shorewall 2.0.1:
|
||||
|
Loading…
Reference in New Issue
Block a user