Displaying 20 results from an estimated 10000 matches similar to: "Shorewall development and announcement lists moving to SourceForge"
2005 Jul 07
0
Shorewall users mailing list moved to SourceForge.net
Hi folks,
As the subject says, the Shorewall users mailing list has been
moved to SourceForge.net. I''m still manually processing a number of
subscribe and unsubscribe requests that have occurred since we requested
the import.
The list archives are now available via:
http://sourceforge.net/mail/?group_id=22587
and you can manage your subscription to the new list at:
2006 Mar 02
4
The inaugural Shorewall survey!
Greetings to all of the Shorewall community!
We''d like to find out a little more about the environments in which
Shorewall runs, and to this end i''ve created a survey. It is mostly
designed to allow Shorewall users to see how their environment compares
with that of the average Shorewall user (if such a thing exists!), but
the results may be used by the Shorewall team to assist
2003 May 21
1
Order sensitivity in shorewall configs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi folks (mostly Tom),
In which shorewall configs is the ordering of entries significant? I
know about rules & policies, and if i remember correctly zones under
some circumstances (when one is a sub-zone of another), but are there
any others?
I am trying to work out (for my multi-firewall preprocessing script)
whether i need to process
2004 Apr 24
0
Announce: shoregen 0.1.1 release
Hi folks,
As requested earlier in the week, i''ve done some cleaning on my little
script to manage shorewall configurations across multiple firewalls, and
the results are available now.
You can find a (rather banal) pointer at:
http://paulgear.webhop.net/linux/#shoregen
Download it at:
http://paulgear.webhop.net/linux/RPMS/noarch/shoregen-0.1.1-1.noarch.rpm
For you non-RPM types,
2005 May 29
1
devel.shorewall.net
Hi folks,
Over the weekend Ron has made some good progress with functionality
available at http://devel.shorewall.net, and i''ve converted all of the
content i had placed at http://shorewall.dyndns.org (which is now a
redirect to the former). Please have a look around and give your
feedback, either here or on the site itself.
--
Paul
<http://paulgear.webhop.net>
--
Did you know?
2005 Jun 24
4
Chat servers?
Anyone know how/where we can get some?
It has been raised before:
http://lists.shorewall.net/pipermail/shorewall-users/2004-July/013594.html
I''d like to see an IRC or Jabber service for both support and development.
--
Paul
<http://paulgear.webhop.net>
--
Did you know? OpenOffice.org has built-in PDF creation. Better yet,
it''s compatible with Microsoft Office, and
2003 May 10
2
LAST LINE business
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
Quick question: can anyone remember the reason why all the config files
end in ''#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE''
or something similar?
I''m starting work on a shorewall preprocessor that will allow multiple
firewalls to be administered from a single system (not a GUI, though),
and
2005 May 27
10
Help wanted notices
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
2005 Jun 24
13
Test environments?
Hi folks,
When we first started talking about Shorewall post-Tom, a few people
offered to help with testing. Would those people please raise their
hands again? :-)
I''m investigating Nicolas Helleringer''s recent message on
shorewall-users
(http://lists.shorewall.net/pipermail/shorewall-users/2005-June/018898.html),
and a good test environment would come in really handy,
2005 May 26
11
Quick poll: CVS commits
Hi folks,
I''m conducting a straw poll for your opinions on whether we should send
CVS commit logs (probably with diffs) to the shorewall-devel list, or to
another (new) list?
I can see advantages to both ways: separate lists mean that people who
aren''t contributing code don''t get flooded with code noise, but a single
list will help keep everyone involved in the
2003 Jan 30
4
ACCEPT vs DNAT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
Can someone refresh my memory on the difference between the following
(where dmz contains an RFC 1918 address host)?
ACCEPT net dmz tcp 80 - all
DNAT net dmz tcp 80
I''m trying to generate a script for maintaining multiple interconnected
firewalls from shared policy, rules, and zone files, and i
2005 Jun 03
0
Re: routestopped doc error
Lars Jensen wrote:
> Hi paul,
>
> The documentation for the routestopped configuration file at
> http://shorewall.sourceforge.net/Documentation.htm#Routestopped says
> that the host must be listed separated by commas. If this is done, an
> error occurs upon reboot, and shorewall doesn''t load at all (debian). It
> is necessary to include double quotes also, like this:
2007 Aug 13
0
Survey time again?
Hi folks,
I''m feeling the need to get an updated feel for where our users are at
with respect to Shorewall, and i''m thinking about running a survey again.
My thoughts at the moment are that we should have two separate surveys:
one to find out about users and their thoughts, and the other to find
out about the systems on which Shorewall is running.
If you have any thoughts
2005 May 27
3
Re: Shorewall development web site (Mike Noyes)
Hello,
I leave for a couple days .. (Well months) and look at what has
happened. :-)
I would throw my support in behind Xoops .. to be honest ..
If a portal is what we are trying to achieve here.
I just happen to think that sometimes .. More work goes into web design
etc than goes into actual Code.
But thats because I am a lamer at web design :-)
I am coming in here a bit late .. But tell
2005 May 26
28
Shorewall development web site
Hi folks,
Last night and this morning i''ve hacked up a quick web site for
coordinating our development work based on Drupal (http://drupal.org).
You can find it at:
http://shorewall.dyndns.org
I''ve put a few ideas in there - feel free to use the comments or sign
up for an account and create your own pages (particularly in the two
books about development and web site work).
2002 May 14
3
[Shorewall-users] Redirect loc::80 to fw::3128 not work (fwd)
I''m beginning to believe that the use of the last column in the rules file
to designate redirection/forwarding is too subtle for many users. For 1.3,
I think I''ll do something like the following:
Current rule:
ACCEPT net loc:192.168.1.3 tcp 80 - all
New rule:
FORWARD net loc:192.168.1.3 tcp 80
Current rule:
ACCEPT net fw::3128 tcp 80 - all
New rule:
REDIRECT net
2005 Jun 30
10
Long Shorewall Startup Times Revisited
Hello,
With reference to the problems listed below. I too am having
incredibly long start up times. I''m talking minutes here (around 5
minutes).
My configuration is not complex I don''t think. We are you using ldap
too and the settings are bellow. The network is up as I''m restarting
shorewall whilst the machine is running.
Any suggestions? Is there no way to
2005 Jun 01
5
use of shell code in shorewall/params
The params file appears to be simply "sourced" by the firewall script,
which means one can put any Bourne shell code into it and it will
execute it. This feature isn''t documented, so I''m wondering if it can
be documented and thus guaranteed to always work. I''d like to dig out
the IP parameters of my interface cards from the ifcfg-eth? files and
set shorewall
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
2005 Jan 05
22
Shorewall and IPV6
As 2.2.0 is nearing release, I''ve begun to think about what I''ll do for
2.3 and I think that it is time for Shorewall to add support for IPV6.
Because of parsing ambiguities, the need to maintain upward
compatibility with both Shorewall and 6Wall, and different available
functionality in IPV4 and IPV6 Netfilter, I believe that it is going to
be necessary for some files to be