similar to: RE: Docs

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. > > > >

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

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

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 --

Ron and Steve, 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. Please let me know. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net

I just installed Shorewall for the first time and had no working knowledge of iptables other than a couple magazine articles prior to this time. The use of the QSG is fresh in my mind. It was the single most helpful guide of any on the site. Comments: 1) The /etc/shorewall/masq section shows the use of the third column but then says you don''t need it if you have a dynamic ip. Its

On Wed, 5 Jun 2002, Ron Shannon wrote: > Bummer. Will the robots.txt handle it? (http://httpd.apache.org/docs/misc/howto.html#stoprob) > Nope -- most of the offending bots just ignore robots.txt. The CVS interface is still available at: http://www.shorewall.net/cgi-bin/cvsweb.cgi There is just no link to it from the index. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM:

hi, Postmaster wrote: > Hello, > > hope one can give me a hint. > > I am trying to setup secured connections for > wavelan clients with no success. > > On the windows side, the eventviewer is saying: > Bogus data reveived from 010010050001. ups, my falt. i broke one priv key. Now the connection is working. I still can not route default taffic through tincd. The

This is becoming a FAQ and should probably be added to the docs. Thanks, -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net ---------- Forwarded message ---------- Date: Sun, 28 Apr 2002 16:09:01 -0700 (Pacific Daylight Time) From: Tom Eastep <teastep@shorewall.net> To: Carl Spelkens

---------- Forwarded Message ---------- Subject: Re: [Shorewall-users] strange UDP scan results on a Shorewall=20 firewall Date: Sun, 3 Mar 2002 08:33:20 -0800 From: Tom Eastep <teastep@shorewall.net> To: "Scott Duncan" <sduncan@cytechconsult.com> On Saturday 02 March 2002 04:30 am, Scott Duncan wrote: > Yes, the net->all policy is the same on all three (REJECT log

Shorewall 1.3.9 is available. In this release: 1. DNS Names are now allowed in Shorewall config files (I still recommend against using them however). 2. The connection SOURCE may now be qualified by both interface and IP address in a Shorewall rule. 3. Shorewall startup is now disabled after initial installation until the file /etc/shorewall/startup_disabled is removed. 4. The

Let me know if there are any problems. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

I have purchased a license for Vexira MailArmor (an antivirus product) and the good news is that it is installed and working at shorewall.net. The bad news is that I have yet to get Vexira running together with SpamAssassin :-( As things currently stand, list posts will be protected from viruses but may contain Spam. I''ll continue to work to correct this situation. -Tom -- Tom Eastep

The 1.2 firewall contains messy logic to support the old sample configurations in that any rule that contains "none" in any of its columns is ignored. I''m considering removing that messiness in 1.3 and seek the opinion of the list. Thanks, -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

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 have implemented the ability to specify ''all'' in the SOURCE and DESTINATION columns of the rules file and I''m not sure I like the result. The code is in CVS if any of you are interested in giving it a try. If you do try it, please let me know what you think. If you specify ''all'' in those columns it must not be qualified (may not be followed by

Hi group, I am a newbie to Taffic contol. I came across many new terms and technical documantation and technology along with this new intrest of mine. After 2 weeks i am unable to find a good starting point. there are cbq, HTB, classifies MARK and all sorts of things The apge at by MAB given me a introduction to all sorts of Terms. I am now reading LARTC How to as any Linux traffic doc. points

I have following smb.conf: hosts deny = all hosts allow = 192.168.x.0/32 127.0.0.1/32 name resolve order = wins lmhosts hosts bcast interfaces = 192.168.x.y/32 127.0.0.1/32 socket address = 192.168.x.y bind interfaces only = yes disable netbios = yes remote browse sync = 192.168.x.255

Rafa³ Dutko has just discovered a potentially serious bug in version 1.3.0 and 1.3.1. In both versions, where an interface option appears on multiple interfaces, the option may only be applied to the first interface on which it appears. A corrected firewall script for 1.3.1 is available at: http://www.shorewall.net/pub/shorewall/errata/1.3.1/firewall and

I've a 7 box (actually, it's RHEL, but the general list there is moribund), and I'm trying to configure it "correctly" so that it gets its hostname from the DHCP server. All I've found so far is a script to use from hooks of some kind. *Surely* there's just a configuration file option somewhere.... mark