Hi Tom, > New Features: > > 1) Over the years, a number of changes have been added to Shorewall > that work around defects in other products. When running a current > distribution, these workarounds are unnecessary and add to the time > required for normal Shorewall operations. > > Beginning in this release, those workarounds may be disabled by > setting WORKAROUNDS=No in shorewall.conf.
I run # shorewall update -A Updating...... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... No update required to configuration file /etc/shorewall/shorewall.conf; /etc/shorewall/shorewall.conf.bak not saved Loading Modules... Converting 'FORMAT' and 'COMMENT' lines to compiler directives... Checking /etc/shorewall/zones... Checking /etc/shorewall/interfaces... Determining Hosts in Zones... Locating Action Files... Checking /etc/shorewall/policy... Running /etc/shorewall/initdone... Adding Anti-smurf Rules Adding rules for DHCP Checking TCP Flags filtering... Checking Kernel Route Filtering... Checking Martian Logging... Checking MAC Filtration -- Phase 1... Checking /etc/shorewall/rules... Checking /etc/shorewall/conntrack... Checking MAC Filtration -- Phase 2... Applying Policies... Checking /usr/share/shorewall/action.Reject for chain Reject... Checking /usr/share/shorewall/action.Broadcast for chain Broadcast... Shorewall configuration verified # grep -i work /etc/shorewall/shorewall.conf I expected to see "WORKAROUNDS" in shorewall.conf. Is that wrong? -Thomas ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
