similar to: Docs - Structure Musings

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

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

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,

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

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

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

We''re starting to collect several comments for doc revisions, which is = great. Another existing source of comments and suggestions is the list = archives. Would someone be willing to spend an hour or two to (1) search = the list archives for documentation issues/suggestions, perhaps using = search terms like: docs, documentation, instructions, Quick Start, = samples, etc., and (2)

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

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

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,

On 13.11.20 13:22, Paul C. Anagnostopoulos via llvm-dev wrote: > Your suggestion for two passes is indeed my plan if simply using 3-byte sizes is not acceptable. I don't want to duplicate all the logic in a second length-calculating function, so I would just have special logic for the three matching operators with children and use the existing function for the rest, passing a null output

Would it make sense for TableGen to generate the outer OPC_SwitchOpcode offset table? At 11/13/2020 07:53 AM, Nicolai Hähnle wrote: >That said, if we are seriously thinking about the performance of the byte code, perhaps some of these opcodes should be reconsidered at a higher level anyway. > >For example: The overall bytecode always begins with an OPC_SwitchOpcode implemented as a

I took a look at all the OPC_SwitchOpcode operators in the matching tables. Almost every target starts with a large one, which is now cached by the interpreter. Instead, TableGen could build the opcode -> offset table. But there are also many other opcode switches with between 10 and 70 cases. To speed these up, we could embed a sorted opcode -> offset table right in the matcher code. Or,

Yes, we can. But I think either solution is going eliminate the relaxation step completely, Either we will always use 3-byte sizes or we will make a first pass to size everything and then a second pass to emit the code. Either way, no relaxation is necessary. >Can we skip the relaxation step if comments aren't being emitted? >Comment emission is off by default in CMake configuration.

I'm toying with the idea of writing a Samba-oriented Win95/98/NT logon window. I know it's possible to replace Windows' logon mechanism with another. Novell's Client32 does this. I know there's also standards to make a network service available to Windows' change-password mechanism (so I can fire smbpasswd on the other side). That could be an alternative to establishing

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

As a perpetual Rails dabbler, I make an awful lot of typical beginner mistakes. And the logs are always either too verbose or too sparse to help me. And it started me thinking. I came from one of the largest production OLTP systems in the world, and the one thing that helped us manage troubleshooting in both development and production was extensive, obsessive, flexible logging. Every operation

Greetings, What programming languages besides shell scripting are used in shorewall? What knowledge is needed to help in shorewall development? I figure iptables is a goood bet but is there anything else as well? Thank you for your time. Regards, Jason