similar to: 1.3.2 Documentation

IMHO, our big picture challenge is that multiple explanations for several topics are spread out over several different docs and pages One parameter is frequently discussed in four or more places (QSG, files reference pages, file comments, main documentation, etc.) That gives multiple perspectives, which can be good, but can also lead to at least the appearance, especially to a beginner, of

I think we should add an FAQ entry for tcp_ecn. I remember Tom giving a good description in one of his many responses and there is mention of it in the pptp page, but I could not find the response from Tom about different tcp stacks. Thanks, -- Steve Herber herber@thing.com work: 206-261-0307 Systems Engineer, AMCIS, UoW home: 425-454-2399 ---------- Forwarded message ---------- Date: Sat,

Now that 1.3 is out, I thought it would be a good idea to tell you what my plans are for Shorewall and to solicit input from this list. My focus for the next several minor releases will be to incorporate recent Netfilter enhancements into Shorewall. For example, this afternoon I have integrated support for the ''multiport'' match facility. I would like to defer the next minor

I think that the time has come for me to back off a bit from my involvement with Shorewall. I just don''t have enough cycles (or energy) to keep up the pace of the last several months. As a consequence, I''m going to do the following: 1. I''m going to stop personally supporting the entry level tools (samples and quick start guide). These tools are a source of constant

Rather than have lots of folks downloading a version with a broken ''check'' command, I''ve released 1.4.1a that corrects the problem. Sorry for the back-to-back releases today... -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.sf.net Washington USA \ teastep@shorewall.net

Attached is file "QSG-issues-1.0.txt" containing a numbered and commented list of issues collected from contributors and recent lists activity. It might be cool to have these issues in some spiffy issue tracking system like RT or something, but for a low tech start it''ll probably suffice. COMMENTS - IMHO (no particular order): I have searched the archives for additional

The 3.1 Beta is now available -- check the Shorewall home page. -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

On Sat, 15 Jun 2002, Ron Shannon wrote: > > I am ready to begin the documentation changes for 1.3.2. Are > > you close to > > having any of your changes ready for release? If so, we can > > get those into > > CVS before I begin my changes -- if not, then I''ll go ahead > > and update CVS > > with the 1.3.2 material. > > > >

Hello all, I don''t want this to be a tome'' but felt a comment was in order. Many new users (Linux and Shorewall are no different) are more apt to not read the manual(RTFM) as they view it as "Taking to long" and don''t understand it''s relevance in their particular scenario. This is unfortunate in the case of Shorewall. As the documents are not only

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

I looked at the 1.3 whitelist documentation and realized that the ops example, while interesting in and of itself, did not do what I think a whitelist does. Back to symmetry, if a blacklist is a list of sites not allowed to connect in through the fire wall, maybe to a web server, for example, then a whitelist should be a list of machines that are allowed to access a service or services, again,

Just a note to mention that I have been using the RC1 release at work for a simple one interface firewall. No problems that I have seen. We use Solaris, AIX, Tru64, and Linux in my group at the U of W. I know some IP filter package is available on Solaris and Tru64. On the Tru64 system you can configure an interface with a list of cidr notation subnets to accept or deny access. I reformatted

At Tom Eastep''s request, an informal Shorewall Documentation Support = Group (DSG) is hoping to relieve some of the writing and editing burdens = that come with maintaining and improving the Shorewall documentation. = The DSG welcomes and needs your suggestions and contributions about all = aspects of the documentation, including structure, content, references, = style, grammar --

Shorewall 1.3.2 is now available. New features include: 1. A new "logwatch" command has been added to the /sbin/shorewall program. 2. Shorewall can now take advantage of the Netfilter ''multiport'' match function (kernel configuration option CONFIG_IP_NF_MATCH_MULTIPORT). 3. Dynamic blacklisting is now supported through the use of three new commands in

On Fri, 26 Apr 2002, Ron Shannon wrote: > All points agreed. > > As you suggest, the docs are better if they''re a well-integrated set. If > a choice is made to exclude an advanced subject or level of detail from > the QSG, they should be covered elsewhere. As noted before, the docs as > a whole are exceptionally good. Your extra effort on the docs certainly > shows

Thank''s to Mike Martinez, the Shorewall Documentation is now available in PDF format at: http://www.shorewall.net/pub/shorewall/Shorewall_Users_Guide-1.3.2.pdf Thanks again Mike!! -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

This is interesting... And probably requires some changes. -- Steve Herber herber@thing.com work: 206-261-0307 Systems Engineer, AMCIS, UoW home: 425-454-2399 ---------- Forwarded message ---------- Date: Thu, 6 Jun 2002 09:20:54 -0700 From: John W Baxter <jwblist@olympus.net> To: linux-list@ssc.com Subject: [SLL] New 67./8 and 68./8 now in use The /8 subnets 67.0.0.0 and 68.0.0.0,

I, too, want to thank Tom for such a great software package and all the support he has always given. I was just reading a Slashdot interview with the Nagios/NetSaint author Ethan Galstad. The whole article is interesting and I bet the questions and answers would be similar for Shorewall: http://interviews.slashdot.org/article.pl?sid=03/01/09/1216259&mode=thread&tid=156 Question 19

Andy Wiggin has contribued a Python program that reads http://www.iana.org/assignments/ipv4-address-space and creates a list of reserved subnets suitable for inclusion in /etc/shorewall/rfc1918. The list produced by Andy''s program will be included in the rfc1918 file included in version 1.3.2 (it''s available now from CVS). Thanks Andy! -Tom -- Tom Eastep \ Shorewall -

Hi folks, I''ve added a couple of ''help wanted'' ads to our SourceForge project. You can see them at http://sourceforge.net/people/?group_id=22587 I''ll add more as i have the opportunity. If you can think of other jobs we need to assign, please let me know. -- Paul <http://paulgear.webhop.net> -- Did you know? Using accepted quoting conventions makes