forked from extern/shorewall_code
Fix 'iprange' command
This commit is contained in:
parent
d66fc7a7e1
commit
ff26ff4697
@ -25,6 +25,8 @@ Changes in Shorewall 4.3.10
|
||||
|
||||
9) Implement nested HTB classes.
|
||||
|
||||
10) Fix 'iprange' command.
|
||||
|
||||
Changes in Shorewall 4.3.9
|
||||
|
||||
1) Logging rules now create separate chain.
|
||||
|
@ -469,7 +469,7 @@ ip_range() {
|
||||
y=2
|
||||
z=1
|
||||
|
||||
while [ $(( $first % $y )) -eq 0 ] && addr_comp $l $(( $first + $y )) ; do
|
||||
while [ $(( $first % $y )) -eq 0 ] && ! addr_comp $(( $first + $y )) $l; do
|
||||
vlsm=/$x
|
||||
x=$(( $x - 1 ))
|
||||
z=$y
|
||||
|
@ -84,7 +84,12 @@ released late in 2009.
|
||||
----------------------------------------------------------------------------
|
||||
|
||||
1. Previously, specifying a source port for SCTP in
|
||||
/etc/shorewall/tcfilters would cause an invalid rule to be generated.
|
||||
/etc/shorewall/tcfilters would cause an invalid rule to be
|
||||
generated.
|
||||
|
||||
2. The list of networks returned by the 'shorewall iprange' command
|
||||
was not minimal.
|
||||
|
||||
----------------------------------------------------------------------------
|
||||
K N O W N P R O B L E M S R E M A I N I N G
|
||||
----------------------------------------------------------------------------
|
||||
|
Loading…
Reference in New Issue
Block a user