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

Allow hex numbers in 'mark' column of the providers file

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3850 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-05-03 20:37:35 +00:00
parent 3b830ff051
commit f2f7edf404
2 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Shorewall/compiler
View File

@ -1182,6 +1182,14 @@ __EOF__
local t n iface option first=Yes
[ -n "$MANGLE_ENABLED" ] || fatal_error "Providers require mangle support in your kernel and iptables"
#
# The following is because the %$#@ shell doesn't except hex numbers in '-eq' tests
#
case number in
0*)
number=$(($number + 0))
;;
esac
for t in $PROVIDERS; do
if [ "$t" = "$table" ]; then

2
Shorewall/shorewall.conf
View File

@ -860,7 +860,7 @@ IMPLICIT_CONTINUE=Yes
#
# Normally, Shorewall restricts the set of mark values to 1-255. If you set
# HIGH_ROUTE_MARKS=Yes, Shorewall will rather restrict the set of routing
# mark values (those specified in the /etc/shorewall/providers file) to
# mark values (those specified in the /etc/shorewall/providers file) from
# 0x0100 to 0XFF00 (with the low-order byte being zero). This allows
# connection marks to be shared between traffic shaping and policy routing
# (traffic shaping marks are always restricted to 1-255).