Displaying 20 results from an estimated 10000 matches similar to: "Shorewall 4.3.7"
2007 Jun 09
20
Shorewall 4.0.0 Beta 4
I''ve uploaded Beta 4. It corrects a bad bug involving exclusion in the
hosts file. In addition, it contains the first release of a new
Bridge/firewall implementation that uses the reduced-function physdev
match found in kernel 3.6.20 and 3.6.21.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \
2007 Jun 09
20
Shorewall 4.0.0 Beta 4
I''ve uploaded Beta 4. It corrects a bad bug involving exclusion in the
hosts file. In addition, it contains the first release of a new
Bridge/firewall implementation that uses the reduced-function physdev
match found in kernel 3.6.20 and 3.6.21.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \
2012 Sep 03
10
Shorewall 4.5.8 Beta 1
Shorewall 4.5.8 Beta 1 is now available for testing.
----------------------------------------------------------------------------
I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E
----------------------------------------------------------------------------
1) This release includes the defect repair from Shorewall 4.5.7.1.
2) The restriction that TTL and HL rules could
2012 Sep 03
10
Shorewall 4.5.8 Beta 1
Shorewall 4.5.8 Beta 1 is now available for testing.
----------------------------------------------------------------------------
I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E
----------------------------------------------------------------------------
1) This release includes the defect repair from Shorewall 4.5.7.1.
2) The restriction that TTL and HL rules could
2005 May 05
4
Shorewall 2.3.0
http://shorewall.net/pub/shorewall/2.3/shorewall-2.3.0
ftp://shorewall.net/pub/shorewall/2.3/shorewall-2.3.0
WARNING: This is a development release and may be unstable
New Features in version 2.3.0
1) Shorewall 2.3.0 supports the ''cmd-owner'' option of the owner match
facility in Netfilter. Like all owner match options, ''cmd-owner'' may
only be applied to
2010 Jun 17
4
shorewall 4.4.10 failing to start; won't recognize ipset "capability"
I have been using shorewall for years with ipsets. I have encountered a
problem after upgrading from 4.2.11 to 4.4.10. When I run
''shorewall-check'' or ''shorewall start'', it halts with the error:
----------------------------------------------------------------------
ERROR: ipset names in Shorewall configuration files require Ipset Match
in your kernel and
2011 Jul 25
4
ipsets
I haven''t debugged this enough to understand what is happening, but I
observe the following:
someipset = bitmap:ip,mac
1) br0:+someipset
2) br0:+someipset[2]
The first 1) doesn''t match anything in rules or tcrules, the second 2)
matches fine. (Also using +someipset[1] doesn''t match anything)
Is it possible/sensible/feasible to have shorewall figure out the
2011 Jul 05
24
Shorewall 4.4.21 RC 3
RC 3 is now available for testing.
Problems corrected:
1) The Shorewall and Shorewall6 ''load'' and ''reload'' commands
previously used the setting of RSH_COMMAND and RCP_COMMAND from
/etc/shorewall/shorewall.conf (/etc/shorewall6/shorewall6.conf).
These commands now use the .conf file in the current working
directory.
2) The new parameterized
2011 Jul 05
24
Shorewall 4.4.21 RC 3
RC 3 is now available for testing.
Problems corrected:
1) The Shorewall and Shorewall6 ''load'' and ''reload'' commands
previously used the setting of RSH_COMMAND and RCP_COMMAND from
/etc/shorewall/shorewall.conf (/etc/shorewall6/shorewall6.conf).
These commands now use the .conf file in the current working
directory.
2) The new parameterized
2012 Nov 24
20
Shorewall 4.5.10 Beta 2
Beta 2 is now available for testing.
Problems Corrected since Beta 1:
1) References to the obsolete USE_ACTIONS option have been removed
from the manpages.
2) NFLOG has been documented for some time as a valid ACTION in the
rules files but support for that action was never implemented
until this release.
3) The Checksum Target capability detection in the rules compiler was
2012 Nov 24
20
Shorewall 4.5.10 Beta 2
Beta 2 is now available for testing.
Problems Corrected since Beta 1:
1) References to the obsolete USE_ACTIONS option have been removed
from the manpages.
2) NFLOG has been documented for some time as a valid ACTION in the
rules files but support for that action was never implemented
until this release.
3) The Checksum Target capability detection in the rules compiler was
2009 Dec 08
1
EmergingThreats fwrules ipset updater
hi
i''ve created an emergingthreats fwrules ipset updater for use with my
shorewall.
maybe others find this usefull too.
short howto:
* get bash script (emerging-ipset-update.txt) from
http://doc.emergingthreats.net/bin/view/Main/EmergingFirewallRules
* add the configured ipsets to shorewall configfile "blacklist"
* if not already configured: configure your interfaces for
2004 Feb 08
3
Shoerwall 1.4.10a
This is a rollup of two fixes:
a) A fix for obscure [re]start errors involving the /etc/shorewall/masq
file.
b) A change which allow ''maclist'' with Atheros WiFi cards.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
2005 May 06
0
Behavior of SAVE_IPSETS
After I''ve played with ipsets for several days, I''m beginning to become
disenchanted with the way the SAVE_IPSETS=Yes works.
I spent almost an hour configuring a bunch of ipsets to be just the way
that I wanted them only to wipe them out with a "shorewall restart" :-(
So, I think that I will change the implementation as follows:
a) The ipset contents will only be
2003 Mar 05
3
Shorewall 1.4.0 RC1
The first release candidate is now available at:
http://www.shorewall.net/pub/shorewall/Beta
ftp://ftp.shorewall.net/pub/shorewall/Beta
The only change between Beta 1 and RC1 is that the ''check'' command is back
in RC1.
Function from 1.3 that has been omitted from this version includes:
1) The MERGE_HOSTS variable in shorewall.conf is no longer
supported. Shorewall 1.4
2008 Dec 25
2
Problems with exclusion in host definition - shorewall 4.2.3 latest
Hi,
usually my shorewall inst. uses compiler=perl.
While some tests I changed my config to compiler=shell, and in this case
I get an error like this:
--------------------------------------------------------
Setting up TCP Flags checking...
iptables v1.3.8: host/network `169.254.0.0/16!169.254.1.0'' not found
Try `iptables -h'' or ''iptables --help'' for more
2002 Dec 07
6
More speedups in CVS
The ''firewall'' and ''functions'' file in CVS together produce a 30%+ speedup
of ''shorewall restart'' on my firewall when compared to 1.3.11a.
Please test with these files -- I don''t anticipate making any more
performance changes for 1.3.12 and I want to be sure that I didn''t break
anything.
-Tom
--
Tom Eastep \ Shorewall
2011 Mar 13
16
Shorewall 4.4.19 Beta 1
Beta 1 is now available for testing.
----------------------------------------------------------------------------
I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E
----------------------------------------------------------------------------
1) Previously /var/log/shorewall*-init.log was created in the wrong
Selinux context. The rpm''s have been modified to
2011 Mar 13
16
Shorewall 4.4.19 Beta 1
Beta 1 is now available for testing.
----------------------------------------------------------------------------
I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E
----------------------------------------------------------------------------
1) Previously /var/log/shorewall*-init.log was created in the wrong
Selinux context. The rpm''s have been modified to
2013 Dec 17
1
shorewall add fails with IPSET=
Hi all
I have a CentOS6 box with shorewall-4.5.21.
If I have IPSET= in shorewall.conf and I issue the command "shorewall add
ppp:192.168.33.3 ptp", I get the error:
/usr/share/shorewall/lib.cli: line 585: [: too many arguments
ERROR: Zone ptp, interface ppp does not have a dynamic host list
The error is corrected setting the actual path to ipset in shorewall.conf,
or via the patch: