extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-12-22 22:30:58 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update comments and release documentation

Browse Source
This commit is contained in:
Tom Eastep 2009-10-26 10:03:51 -07:00
parent 8251948d2a
commit cc0adc218f
2 changed files with 18 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Shorewall/Perl/Shorewall/Providers.pm
View File

@ -142,7 +142,9 @@ sub setup_route_marking() {
sub copy_table( $$$ ) {
my ( $duplicate, $number, $realm ) = @_;
#
# Hack to work around problem in iproute
#
my $filter = $family == F_IPV6 ? q(sed 's/ via :: / /' | ) : '';
if ( $realm ) {
@ -164,7 +166,9 @@ sub copy_table( $$$ ) {
sub copy_and_edit_table( $$$$ ) {
my ( $duplicate, $number, $copy, $realm) = @_;
#
# Hack to work around problem in iproute
#
my $filter = $family == F_IPV6 ? q(sed 's/ via :: / /' | ) : '';
if ( $realm ) {

24
Shorewall/releasenotes.txt
View File

@ -190,26 +190,26 @@ Shorewall 4.4.3
what command was being executed. Now, this information is only
detected when it is needed.
4) Nested zones where the parent zone was defined by a wilecard
4) Nested zones where the parent zone was defined by a wildcard
interface (name ends with +) in /etc/shorewall/interfaces did
not work correctly in some cases.
5) IPv4 addresses embedded in IPv6 (e.g., ::192.168.1.5) were
incorrectly reported as invalid.
6) The messages issued when an optional provider was not usable were
confusing; the message intended to be issued when the provider
shared an interface ("WARNING: Gateway <gateway> is not reachable --
Provider <name> (<number>) not Added") was being issued when the
provider did not share an interface. Similarly, the message
intended to be issued when the provider did not share an interface
("WARNING: Interface <interface> is not usable -- Provider <name>
(<number>) not Added") was being issued when the provider did share
an interface.
7) Under certain circumstances, optional providers were not detected
6) Under certain circumstances, optional providers were not detected
as being usable.
Additionally, the messages issued when an optional provider was not
usable were confusing; the message intended to be issued when the
provider shared an interface ("WARNING: Gateway <gateway> is not
reachable -- Provider <name> (<number>) not Added") was being
issued when the provider did not share an interface. Similarly, the
message intended to be issued when the provider did not share an
interface ("WARNING: Interface <interface> is not usable --
Provider <name> (<number>) not Added") was being issued when the
provider did share an interface.
----------------------------------------------------------------------------
K N O W N P R O B L E M S R E M A I N I N G
----------------------------------------------------------------------------