Displaying 7 results from an estimated 7 matches for "startup_en".
Did you mean:
startup_xen
2004 Aug 28
0
Shorewall 2.1.7
...wall/tos
2) The following builtin actions have been removed and have been
replaced by the new action logging implementation described in the
new features below.
logNotSyn
rLogNotSyn
dLogNotSyn
3) If shorewall.conf is upgraded to the latest version, it needs to be
modified to set STARTUP_ENABLED=Yes
4) The Leaf/Bering version of Shorewall was previously named:
shorwall-<version>.lrp
Beginning with 2.1, that file will now be named:
shorewall-lrp-<version>.tgz
Simply rename that file to ''shorwall.lrp'' when installing it on your
LEAF/Beri...
2006 Aug 29
3
masq problem
...rules:
there is no rule like
ACCEPT/REJECT/... loc net/fw - - -
just a few like
ACCEPT net:a.b.c.d fw tcp 21,22,443 -
routestopped:
eth2 x.x.x.x
eth2 y.y.y.y
zones:
fw firewall
net ipv4
loc ipv4
shorewall.conf: (i think it''s default but not shure)
STARTUP_ENABLED=Yes
LOGFILE=/var/log/messages
LOGFORMAT="Shorewall:%s:%s:"
LOGTAGONLY=No
LOGRATE=
LOGBURST=
LOGALLNEW=
BLACKLIST_LOGLEVEL=
MACLIST_LOG_LEVEL=info
TCP_FLAGS_LOG_LEVEL=info
RFC1918_LOG_LEVEL=info
SMURF_LOG_LEVEL=info
LOG_MARTIANS=No
IPTABLES=
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/loc...
2009 Jun 27
1
Transparent Proxy Problem with Squid3 and Shorewall
...TEST LENGTH TOS
# PORT(S) PORT(S)
202:P eth0:!10.0.0.152 0.0.0.0/0 tcp 80
#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE
zone:
# OPTIONS OPTIONS
fw firewall
net ipv4
loc ipv4
#LAST LINE - ADD YOUR ENTRIES ABOVE THIS ONE - DO NOT REMOVE
And finally shorewall.conf:
STARTUP_ENABLED=Yes
VERBOSITY=1
SHOREWALL_COMPILER=
LOGFILE=/var/log/messages
LOGFORMAT="Shorewall:%s:%s:"
LOGTAGONLY=No
LOGRATE=
LOGBURST=
LOGALLNEW=
BLACKLIST_LOGLEVEL=
MACLIST_LOG_LEVEL=info
TCP_FLAGS_LOG_LEVEL=info
RFC1918_LOG_LEVEL=info
SMURF_LOG_LEVEL=info
LOG_MARTIANS=No
IPTABLES=
PATH=/sbin:...
2013 Jun 13
3
"Multiple Internet Connections" with four interfaces
Hi,
I was reading document http://shorewall.net/MultiISP.html#idp3634200.
Inspired by the document I was trying to establish the following changes:
* one additional interface: COMA_IF
* COM[A,B,C]_IF interfaces request IP address via DHCP
* all non-RFC 1918 destined trafic is NATed from INT_IF to COMA_IF
* all non-RFC 1918 destined trafic from GW is routed via COMB_IF by default
* non-RFC 1918
2013 Sep 10
6
lsm configuration issues...
...an et w.x.y.z for the next hop... if I do the lsm
check on w.x.y.z, should I put a ttl=2? and 1 if I check a.b.c.d?
Thx,
JD
----------------------------------------------------------------------
/etc/shorewall/shorewall.conf
----------------------------------------------------------------------
STARTUP_ENABLED=Yes
VERBOSITY=1
BLACKLIST_LOGLEVEL=
LOG_MARTIANS=Yes
LOG_VERBOSITY=2
LOGALLNEW=
LOGFILE=/var/log/messages
LOGFORMAT="Shorewall:%s:%s:"
LOGTAGONLY=No
LOGLIMIT=
MACLIST_LOG_LEVEL=info
RELATED_LOG_LEVEL=
SFILTER_LOG_LEVEL=info
SMURF_LOG_LEVEL=info
STARTUP_LOG=/var/log/shorewall-init.log...
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
...''['' -r /etc/shorewall/shorewall.conf '']''
+ ''['' -n '''' '']''
+ echo ''Processing /etc/shorewall/shorewall.conf...''
Processing /etc/shorewall/shorewall.conf...
+ . /etc/shorewall/shorewall.conf
++ STARTUP_ENABLED=Yes
++ LOGFILE=/var/log/messages
++ LOGFORMAT=Shorewall:%s:%s:
++ LOGTAGONLY=No
++ LOGRATE=
++ LOGBURST=
++ LOGALLNEW=
++ BLACKLIST_LOGLEVEL=
++ LOGNEWNOTSYN=info
++ MACLIST_LOG_LEVEL=info
++ TCP_FLAGS_LOG_LEVEL=info
++ RFC1918_LOG_LEVEL=info
++ SMURF_LOG_LEVEL=info
++ BOGON_LOG_LEVEL=info
++...