Displaying 20 results from an estimated 10000 matches similar to: "Updated rfc1918 and bogons files"
2004 Nov 12
0
Updated rfc1918 and bogons files
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To reflect recent allocations by the IANA, the following files are
available:
For Shorewall 2.0.0b and earlier:
http://shorewall.net/pub/shorewall/errata/1.4.10/rfc1918
ftp://shorewall.net/pub/shorewall/errata/1.4.10/rfc1918
For Shorewall 2.0.1 and later:
http://shorewall.net/pub/shorewall/errata/2.0.10/bogons
2004 Aug 26
0
Updated bogons file
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
An updated bogons file is available at:
http://shorewall.net/pub/shorewall/errata/2.0.8/bogons
ftp://shorewall.net/pub/shorewall/errata/2.0.8/bogons
Thanks to Lorenzo Martignoni for bringing the resent IANA allocations to
my attention.
- -Tom
- --
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \
2004 Aug 26
0
Updated bogons file -- Update
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The initial file that I uploaded was incorrect. If you downloaded a file
that still contains 72.0.0.0/8 then please download again. Sorry for the
confusion.
An updated bogons file is available at:
http://shorewall.net/pub/shorewall/errata/2.0.8/bogons
ftp://shorewall.net/pub/shorewall/errata/2.0.8/bogons
Thanks to Lorenzo Martignoni for bringing
2003 Feb 13
0
Updated rfc1918 file available
A new rfc1918 file that reflects the recent IANA allocation of 222/8 and
223/8 may be found at:
http://www.shorwall.net/pub/shorewall/errata/1.3.14/rfc1918
ftp://ftp.shorewall.net/pub/shorewall/errata/1.3.14/rfc1918
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
Shoreline, \ http://www.shorewall.net
Washington USA \ teastep@shorewall.net
2004 May 14
0
2.0.2 .lrp problem
The 2.0.2 .lrp released yesterday contained the wrong version of
/usr/share/shorewall/functions.
I have updated the .lrp with the correct version of the functions file.
[root@lists shorewall-2.0.2]# ls -l shorwall-2.0.2.lrp
-rw-r--r-- 1 root ftp 78325 May 14 06:28 shorwall-2.0.2.lrp
[root@lists shorewall-2.0.2]# grep shorwall 2.0.2.md5sums
3ae771fcbfe217006e88e69a597c6455
2004 Nov 02
3
Shorewall 2.2.0 Beta 2
http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta2
ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta2
Problems Corrected:
1. The "shorewall check" command results in the (harmless) error
message:
/usr/share/shorewall/firewall: line 2753:
check_dupliate_zones: command not found
2. The
2004 May 18
0
New 2.0.2b .lrp and new .lrp policy
I have just uploaded a new version of the 2.0.2b .lrp:
http://shorewall.net/pub/shorewall/shorewall-2.0.2b/shorwall-2.0.2b.lrp
ftp://shorewall.net/pub/shorewall/shorewall-2.0.2b/shorwall-2.0.2b.lrp
This version already includes the normal LEAF changes that are present
in the shorewall.lrp distributed with Bering and Bering-uClibc.
Thanks to K.-P. Kirchdörfer, future versions of the .lrp will
2004 Oct 25
0
Problem with 2.0.10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The packages that I uploaded earlier were unfortunately incorrect. I
have uploaded the correct packages.
The incorrect md5sums are:
14e8f2bfa08cc5ca2715c8b1179d5eb2 shorewall-2.0.10-1.noarch.rpm
54bcbb2216ad3db9870507cd9716fd99 shorewall-2.0.10.tgz
c2fe0acc7f056acb56d089cf8dafa39a shorwall-2.0.10.lrp
The correct md5sums are:
2004 Nov 02
0
Shorewall 2.2.0 Beta 2
http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta2
ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta2
Problems Corrected:
1. The "shorewall check" command results in the (harmless) error
message:
/usr/share/shorewall/firewall: line 2753:
check_dupliate_zones: command not found
2. The
2005 May 26
3
Updated Shorewall build and publish scripts
Attached please find updated build and publish scripts. They set the
''ulink.target'' parameter appropriately when converting docbook->HTML. I
have always hacked my xhtml/params.xsl file to set this parameter; these
updated scripts make that abomination unnecessary.
Paul/Mike: It might be a good idea to add a CVS project for these scripts.
-Tom
--
Tom Eastep \ Nothing is
2004 Nov 30
2
RFC1918 all of a sudden?
Is my RFC1918 file obsolete? I have been assigned an ip in the
83.0.0.0/8 range, and of cource a lot of Shorewall systems drop me with
a RFC1918 error.
So, is my ISP actually giving me a RFC1918 IP, or am I missing
something?
.
2004 Nov 22
6
Shorewall 2.0.11
No need to upgrade to this release if you already have the new bogons
file or don''t use that file. The primary change is a fix to the
install.sh script which previously gave an error on a new install.
http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.11
ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.11
Problems corrected in 2.0.11
1) The INSTALL file now include special
2004 Nov 19
0
Shorewall 2.2.0 Beta 4
http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta4
ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta4
Problems Corrected:
1. A cut and paste error resulted in some nonsense in the
description of the IPSEC column in /etc/shorewall/masq.
2. A typo in /etc/shorewall/rules has been corrected.
3. The bogons file has been updated.
4. The
2003 Oct 02
2
Shorewall 1.4.7 RC2
http://shorewall.net/pub/shorewall/Beta
ftp://shorewall.net/pub/shorewall/Beta
Problems corrected since RC1:
1) The documentation of the USERSETS column in the rules file has been
corrected.
2) If there is no policy defined for the zones specified in a rule,
the firewall script previously encountered a shell syntax error:
[: NONE: unexpected operator
Now, the absence of a
2004 Nov 09
1
Shorewall 2.2.0 Beta 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta3
ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta3
Problems Corrected:
1. Missing ''#'' in the rfc1918 file has been corrected.
2. The INSTALL file now includes special instructions for Slackware
users.
New Features:
1. In CLASSIFY rules
2004 Jul 10
0
New Article in the Shorewall Documentation
Please see http://shorewall.net/PacketHandling.html. It details the flow
of a packet through a Shorwall-generated firewall.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
2004 Apr 16
0
Shorewall 2.0 French Language Guides available
Thanks to Fabien Demassieux, French Language versions of the QuickStart
Guides and the Setup Guide are now available:
http://shorewall.net/shorewall_quickstart_guide.htm
http://shorewall.sf.net/shorewall_quickstart_guide.htm
These guides will be available shortly on the other Shorwall Mirrors
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \
2004 Jan 15
2
Crypto API and Shorewall
A number of you are flailing around trying to get the subject combination to
work.
You should all be aware that there are parts of this that don''t currently work
and that won''t work well until there are enhancements made to Shorewall (and
probably to Netfilter).
I. There is no clean way currently to support Road Warriors from a
Masquerading Netfilter firewall/gateway. As
2004 Apr 20
0
outdated bogons table in current Shorewall...
Hi,
according to:
http://www.iana.org/assignments/ipv4-address-space
the bogons table is outdated...
tha attached patch fixes that... (done against 2.0.1)
--
Regards
Thomas
PS.
please CC me as I''m not subscribed to the list
-------------- next part --------------
--- usr/share/shorewall/bogons.old 2004-04-19 18:28:00.000000000 +0300
+++ usr/share/shorewall/bogons 2004-04-20
2005 Jan 11
1
Squid and DMZ (ProxyARP)
Hello All,
I have a question about setting up the shorewall firewall for squid, I
followed the instructions on "Using Shorewall with Squid" --> "Squid Running
in the DMZ" section. For some reason I am unable to get the program to work.
I am able to have the squid work properly by using squidclient program, but
once I setup the firewall to use the redirect I am unable to