similar to: Shorewall 2.2.5 documentation ''issues'' & feature request

Hi Hi Is there any accessible ocumentation, ie plain text or html, how to configure Asterisk. The book 'Asterisk: The Future of Telephony'' is availablly only as and pdf document and is thus unreadable for a blind user. Any pointers welcome. You can still escape from the Gates of hell: Use Linux! -- arimo

I''m trying to learn how to set up Puppet and am coming across a number of dead links in the wiki. Specifically: http://reductivelabs.com/trac/ReferenceIndex, referred to from http://reductivelabs.com/trac/puppet, and http://reductivelabs.com/trac/puppet/wiki/MasterConfigLayout referred to from http://reductivelabs.com/trac/puppet/wiki/DocumentationStart#AdditionalD ocumentation Are

This will be my last 2.2 release. It contains a couple of small bug fixes that I had laying around. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.5 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.5 1) Previously, if PKTTYPE=No in shorewall.conf then pkttype match would still be used if the kernel supported it. 2) A typo in the ''tunnel'' script has been corrected

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

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

The 1.3 Beta Documentation has now been commited to CVS. There will be minor additions to the Documentation between now and release (currently, I''m shooting for release around the middle of next month). Hopefully the new rules syntax will be easier for you folks to deal with in the docs. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net

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

Hello, I have the go ahead to fix documentation. For starters I will clean all extraneous crap from the markup. Then fix any errors and typos. If anyone sees any gramatical errors or typos or needed clarifications or expansions or whatever, please post them here. Or additional FAQ entries, etc, all will be considered. I hope to keep most of this conversation on the shorewall-devel list. Any

So I've gotten excluding paths to work as a standalone command. When I paste this into a script however, it ignores the exclusions. Any advice? rsync -aXvr --times --links --exclude={'*.vdi','*.vmdk','*.ova','*.qcow2','.config/discord/'} /home/path/ user at nas:/NAS/HOME/destination/ Are there supposed to be some kind of brackets around this?

Checked the mans, the archives and the docs first. Nothing there to steer by. Brutus is my NetBSD box. I setup and configured samba just the same as I did on 5 linux boxen, with the exception that I never saw the winbind options in the other (samba-2.2.1a-4) configs. When I try connecting to the NetBSD Server for a W98 client, I get: \\Brutus is not Accessible The specified computer did not

The following is taken from the Release notes for 2.2.3 (which will be released in a month or so). 2) There has been ongoing confusion about how the /etc/shorewall/routestopped file works. People understand how it works with the ''shorewall stop'' command but when they read that ''shorewall restart'' is logically equivalent to ''shorewall

On Mon, 04 Nov 2002 01:27:25 -0800 shorewall-devel-request@shorewall.net wrote: > Shorewall-devel -- confirmation of subscription -- request 168447 > > We have received a request from dummy-kddi.kddnet.de for subscription > of your email address, <s.veckes@de.kddi.com>, to the > shorewall-devel@shorewall.net mailing list. To confirm the request, > please send a message

On Wed, 23 Oct 2002 08:22:38 -0700 shorewall-devel-request@shorewall.net wrote: > Shorewall-devel -- confirmation of subscription -- request 915994 > > We have received a request from > cpe014500117825.cpe.net.cable.rogers.com for subscription of your > email address, <snafu@forkbomb.dhs.org>, to the > shorewall-devel@shorewall.net mailing list. To confirm the request,

Shorewall-users -- confirmation of subscription -- request 533537 We have received a request from 207.34.24.8 for subscription of your email address, <jgofton@danicar.net>, to the shorewall-users@shorewall.net mailing list. To confirm the request, please send a message to shorewall-users-request@shorewall.net, and either: - maintain the subject line as is (the reply''s additional

I''ve created a repository at mail.shorewall.net:/usr/local/cvs. The Shorewall Website/Documentation is in a Project called Shorewall-docs. If you would like access to the repository, send me: a) The IP address that you will be accessing the repository from. b) A user name that you want to use to access the repository. c) Your password encrypted as described at

Hi, I know this isn't a supported platform or anything, but I'm trying to get Samba 2.2.5 going on my Playstation 2 (mipsel-linux). There's an RPM for 2.0.something on the PS2-Linux CD, but I'm always a fan of running the latest version. It compiles okay, as long as I specity ./configure --host=mipsel-linux (not "--build=mipsel-linux" for some reason, like most

Graeme Boyle has contributed a nice description of his Corporate Network Shorewall environment. You can find it at http://shorewall.net/CorpNetwork.htm Thanks Graeme! -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Because of the volume of questions recently regarding Shorewall and Virtual/Aliased Interfaces (e.g., eth0:0), I have written a document that discusses this issue. It may be found at: http://www.shorewall.net/Shorewall_and_Aliased_Interfaces.html The document is linked from the "Documentation Index" and from FAQ #18. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline,

The Shorewall support page advocates including the output of "shorewall status" with problem reports that involve some sort of connection problem. I suspect that the number of people who feel comfortable analyzing problems through use this output is small. To help, I''ve created http://shorewall.net/AnalyzingShorewallStatus.html I suspect that the document isn''t

Dear Sirs, I try to setup a quite complex routing scenario with iproute2, shorewall, bonding and hundrets of vlans as well as a lot of different virtual routing tables. In the past it was often possible to get great support directly by shorewall list but since the routing becomes more complex I do see a need to have a brief consulting by an experienced engineer. Shorewall list recommended me