mirror of
https://gitlab.com/shorewall/code.git
synced 2025-06-11 12:16:57 +02:00
Update release notes comment -- allow '-' in ORIGINAL DEST column for consistency
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@395 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
305c43fea2
commit
a28dac71ec
@ -2257,6 +2257,8 @@ process_rule() # $1 = target
|
||||
|
||||
# Convert 1.3 Rule formats to 1.2 format
|
||||
|
||||
[ "x$address" = "x-" ] && address=
|
||||
|
||||
case $target in
|
||||
DNAT)
|
||||
target=ACCEPT
|
||||
|
@ -38,7 +38,7 @@ New features include:
|
||||
traffic control rules during [re]start. This setting is intended
|
||||
for use by people that prefer to configure traffic shaping when
|
||||
the network interfaces come up rather than when the firewall
|
||||
is started. By setting TC_ENABLED=Yes and CLEAR_TC=No and by
|
||||
not supplying an /etc/shorewall/tcstart file, your traffic
|
||||
shaping rules can still use the 'fw' classifier based on packet
|
||||
marking defined in /etc/shorewall/tcrules.
|
||||
is started. If that is what you want to do, set TC_ENABLED=Yes and
|
||||
CLEAR_TC=No and do not supply an /etc/shorewall/tcstart file. That
|
||||
way, your traffic shaping rules can still use the 'fwmark'
|
||||
classifier based on packet marking defined in /etc/shorewall/tcrules.
|
||||
|
Loading…
x
Reference in New Issue
Block a user