holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Fix error message

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1707 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-10-20 22:29:06 +00:00
parent 532a2d0990
commit b03f513e26
3 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
STABLE2/changelog.txt
View File

@ -66,3 +66,6 @@ Changes in 2.0.10
2) Correct log rule number generation. 2) Correct log rule number generation.
3) Add clarification to /etc/shorewall/tcrules. 3) Add clarification to /etc/shorewall/tcrules.
4) Apply part of Ian Allen's fix for down interface in the SUBNET
column of /etc/shorewall/masq.

2
STABLE2/firewall
View File

@ -4225,7 +4225,7 @@ setup_masq()
;; ;;
*) *)
networks=$(get_routed_networks $networks) networks=$(get_routed_networks $networks)
[ -z "$networks" ] && fatal_error "Unable to determine the routes through interface $networks" [ -z "$networks" ] && fatal_error "Unable to determine the routes through interface \"$source\""
networks="$networks" networks="$networks"
;; ;;
esac esac

5
STABLE2/releasenotes.txt
View File

@ -141,3 +141,8 @@ Problems corrected in version 2.0.10
3) The /etc/shorewall/tcrules file now includes a note to the effect 3) The /etc/shorewall/tcrules file now includes a note to the effect
that rule evaluation continues after a match. that rule evaluation continues after a match.
4) The error message produced if Shorewall couldn't obtain the routes
through an interface named in the SUBNET column of
/etc/shorewall/masq was less than helpful since it didn't include
the interface name.