Displaying 9 results from an estimated 9 matches for "delayblacklistload".
2004 Sep 23
0
Blacklist bug in 2.1.9
With version 2.1.9, if DELAYBLACKLISTLOAD=No (or if the option is
unspecified), the blacklist is not loaded. You can fix the problem by
changing line 5135 in /usr/share/shorewall/firewall from:
if [ -n "$DELAYBLACKLISTLOAD" ]; then
to
if [ -z "$DELAYBLACKLISTLOAD" ]; then
-Tom
--
Tom Eastep \ Nothing is fool...
2004 Sep 16
0
Shorewall-2.1.9
...d. Regardless of the setting of RETAIN_ALIASES,
~ addresses added during "shorewall start" are still deleted at a
~ subsequent "shorewall stop" or "shorewall restart".
3) Users with a large black list (from /etc/shorewall/blacklist) may
~ want to set the new DELAYBLACKLISTLOAD option in
~ shorewall.conf. When DELAYBLACKLISTLOAD=Yes, Shorewall will
~ enable new connections before loading the blacklist rules. While
~ this may allow connections from blacklisted hosts to slip by during
~ the loading of the blacklist, it can substantially reduce the time
~ that...
2008 Nov 13
3
Does code in /etc/shorewall/start exec before or after Shorewall starts?
In the docs at http://www.shorewall.net/Shorewall-perl.html,
"Your ipsets must be loaded before Shorewall starts. You are free to
try to do that with the following code in /etc/shorewall/start"
implies that code in /etc/shorewall/start is executed BEFORE Shorewall starts.
In the default /etc/shorewall/start
# /etc/shorewall/start
#
# Add commands below that you want to be
2005 May 02
1
Shorewall 2.2.4
...t also ensure that you have a route to 224.0.0.0/4 on you
internal (local) interface.
2. A new ''started'' extension script has been added. The difference
between this extension script and /etc/shorewall/start is that this one
is invoked after delayed loading of the blacklist
(DELAYBLACKLISTLOAD=Yes) and after the ''shorewall'' chain has been
created (thus signaling that the firewall is completely up.
/etc/shorewall/started should not change the firewall
configuration directly but may do so indirectly by running
/sbin/shorewall with the ''nolock'' opt...
2006 Aug 29
3
masq problem
...sr/share/shorewall
RESTOREFILE=
IPSECFILE=zones
FW=
IP_FORWARDING=Keep
ADD_IP_ALIASES=Yes
ADD_SNAT_ALIASES=No
RETAIN_ALIASES=No
TC_ENABLED=Internal
CLEAR_TC=Yes
MARK_IN_FORWARD_CHAIN=No
CLAMPMSS=No
ROUTE_FILTER=Yes
DETECT_DNAT_IPADDRS=No
MUTEX_TIMEOUT=60
ADMINISABSENTMINDED=Yes
BLACKLISTNEWONLY=Yes
DELAYBLACKLISTLOAD=No
MODULE_SUFFIX=
DISABLE_IPV6=Yes
BRIDGING=No
DYNAMIC_ZONES=No
PKTTYPE=Yes
RFC1918_STRICT=No
MACLIST_TABLE=filter
MACLIST_TTL=
SAVE_IPSETS=No
MAPOLDACTIONS=No
FASTACCEPT=No
BLACKLIST_DISPOSITION=DROP
MACLIST_DISPOSITION=REJECT
TCP_FLAGS_DISPOSITION=DROP
-- Matej --
-----------------------...
2007 Nov 10
2
Access Point with Ethernet.
...ewall:/usr/share/shorewall
RESTOREFILE=
FW=fw
IP_FORWARDING=On
ADD_IP_ALIASES=Yes
ADD_SNAT_ALIASES=No
RETAIN_ALIASES=No
TC_ENABLED=No
CLEAR_TC=Yes
MARK_IN_FORWARD_CHAIN=No
CLAMPMSS=No
ROUTE_FILTER=Yes
DETECT_DNAT_IPADDRS=No
MUTEX_TIMEOUT=60
NEWNOTSYN=Yes
ADMINISABSENTMINDED=Yes
BLACKLISTNEWONLY=Yes
DELAYBLACKLISTLOAD=No
MODULE_SUFFIX=
DISABLE_IPV6=No
BRIDGING=No
DYNAMIC_ZONES=No
PKTTYPE=Yes
DROPINVALID=Yes
RFC1918_STRICT=No
MACLIST_TTL=
BLACKLIST_DISPOSITION=DROP
MACLIST_DISPOSITION=REJECT
TCP_FLAGS_DISPOSITION=DROP
/etc/shorewall/start:
(not configured)
/etc/shorewall/stop
(not configured)
/etc/shorewall/...
2009 Jun 27
1
Transparent Proxy Problem with Squid3 and Shorewall
...root}@${system}:${destination}''
IP_FORWARDING=On
ADD_IP_ALIASES=Yes
ADD_SNAT_ALIASES=No
RETAIN_ALIASES=No
TC_ENABLED=Internal
TC_EXPERT=No
CLEAR_TC=Yes
MARK_IN_FORWARD_CHAIN=No
CLAMPMSS=No
ROUTE_FILTER=Yes
DETECT_DNAT_IPADDRS=No
MUTEX_TIMEOUT=60
ADMINISABSENTMINDED=Yes
BLACKLISTNEWONLY=Yes
DELAYBLACKLISTLOAD=No
MODULE_SUFFIX=
DISABLE_IPV6=Yes
BRIDGING=No
DYNAMIC_ZONES=No
PKTTYPE=Yes
RFC1918_STRICT=No
MACLIST_TABLE=filter
MACLIST_TTL=
SAVE_IPSETS=No
MAPOLDACTIONS=No
FASTACCEPT=No
IMPLICIT_CONTINUE=Yes
HIGH_ROUTE_MARKS=No
USE_ACTIONS=Yes
OPTIMIZE=0
EXPORTPARAMS=Yes
EXPAND_POLICIES=Yes
KEEP_RT_TABLES=No
D...
2005 Mar 10
7
norfc1918 not working in SW 2.2.1?
Hello all,
Yesterday I noticed that my system was "leaking" traffic towards the
10/8 network, I have shorewall installed on multiple machines ranging
from single interface devices to ones with 10+ interfaces. I tested all
the boxes and they are showing the same behavior.
All systems are CentOS 3.4, 2.4.21-27.0.2.ELsmp.
Shorewall version: 2.2.1
For the host mentioned is a single
2005 May 31
11
More Tests for 2.4.0-RC2 - strange behaviour
...+ MARK_IN_FORWARD_CHAIN=
+ SHARED_DIR=/usr/share/shorewall
+ FUNCTIONS=
+ VERSION_FILE=
+ LOGFORMAT=
+ LOGRULENUMBERS=
+ ADMINISABSENTMINDED=
+ BLACKLISTNEWONLY=
+ MODULE_SUFFIX=
+ ACTIONS=
+ USEDACTIONS=
+ SMURF_LOG_LEVEL=
+ DISABLE_IPV6=
+ BRIDGING=
+ DYNAMIC_ZONES=
+ PKTTYPE=
+ RETAIN_ALIASES=
+ DELAYBLACKLISTLOAD=
+ LOGTAGONLY=
+ LOGALLNEW=
+ DROPINVALID=
+ RFC1918_STRICT=
+ MACLIST_TTL=
+ SAVE_IPSETS=
+ RESTOREFILE=
+ RESTOREBASE=
+ TMP_DIR=
+ CROSSBEAM=
+ CROSSBEAM_BACKBONE=
+ ALL_INTERFACES=
+ ROUTEMARK_INTERFACES=
+ ROUTEMARK=256
+ PROVIDERS=
+ stopping=
+ have_mutex=
+ masq_seq=1
+ nonat_seq=1
+ aliase...