extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-02-16 17:51:16 +01:00
Code Issues Packages Projects Releases Wiki Activity

Some documentation updates

Browse Source
This commit is contained in:
Tom Eastep 2009-06-19 13:00:58 -07:00
parent e2abf20371
commit 8cdb171087
2 changed files with 24 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/MultiISP.xml
View File

@ -1321,9 +1321,10 @@ fi</programlisting></para>
in the preceding section.</para>
<para>Like many Open Source products, LSM is poorly documented. It's
main configuration file is normally kept in /etc/lsm/lsm.conf, but the
file's name is passed as an argument to the lsm program so you can
name it anything you want.</para>
main configuration file is normally kept in
<filename>/etc/lsm/lsm.conf</filename>, but the file's name is passed
as an argument to the lsm program so you can name it anything you
want.</para>
<para>The sample <filename>lsm.conf</filename> included with the
product shows some of the possibilities for configuration. One feature
@ -1332,8 +1333,20 @@ fi</programlisting></para>
configuration file.</para>
<para>I personally use LSM here at shorewall.net (configuration is
described <link linkend="Complete">below</link>). Here are my relevant
configuration files:</para>
described <link linkend="Complete">below</link>). I have set things up
so that Shorewall [re]starts lsm during processing of the
<command>start</command> and <command>restore</command> commands. I
don't have Shorewall restart lsm during Shorewall
<command>restart</command> because I restart Shorewall much more often
than the average user is likely to do. I have Shorewall start lsm
because I have a dynamic IP address from one of my providers
(Comcast); Shorewall detects the default gateway to that provider and
creates a secondary configuration file
(<filename>/etc/lsm/shorewall.conf</filename>) that contains the link
configurations. That file is included by
<filename>/etc/lsm/lsm.conf</filename>.</para>
<para>Here are my relevant configuration files:</para>
<para><filename>/etc/shorewall/isusable</filename>:</para>

9
web/download.htm
View File

@ -66,7 +66,8 @@ shake out the bugs in the next stable release. <span
</ul>
For additional information, see this article about the <a
href="ReleaseModel.html">Shorewall Release Model</a>.
<p>In Shorewall version 4.0.*, there are four related
<p>In Shorewall version <span style="font-weight: bold;">4.0.*</span>,
there are four related
packages:</p>
<ul>
<li><span style="font-weight: bold;">Shorewall-shell</span> -- the
@ -87,7 +88,8 @@ light-weight Shorewall version that will run
compiled firewall scripts generated on a system with one of the
compiler packages installed.</li>
</ul>
In Shorewall version 4.2.*, there are two additional
In Shorewall version <span style="font-weight: bold;">4.2.*</span>,
there are two additional
packages that provide IPv6 support:<br>
<ul>
<li><span style="font-weight: bold;">Shorewall6</span> -- Provides
@ -101,7 +103,8 @@ run compiled firewall scripts generated on a system with Shorewall6
installed.<br>
</li>
</ul>
In Shorewall version 4.4.*, the Shorewall-common, Shorewall-shell and
In Shorewall version <span style="font-weight: bold;">4.4.*</span>,
the Shorewall-common, Shorewall-shell and
Shorewall-perl packages are discontinued and replaced with a single <span
style="font-weight: bold;">Shorewall</span> package which combined the
functions of Shorewall-common and Shorewall-perl. The shell-based