holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Back out Crossbeam documentaiton Changes

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2221 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-06-04 00:48:08 +00:00
parent f75f936cff
commit 1d62d894ef
1 changed files with 0 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
Shorewall-docs2/Documentation.xml
View File

@ -3535,32 +3535,6 @@ LOGBURST=5</programlisting>
the started state. The default value is <quote>no</quote>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>CROSSBEAM and CROSSBEAM_BACKBONE</term>
<listitem>
<para>(Added in Shorewall 2.4.0) — If Shorewall is running in a
Crossbeam System (<ulink
url="http://www.crossbeamsystems.com">http://www.crossbeamsystems.com</ulink>)
you need to activate this directive if you don't want the CPM to
think the system is down and send a reset signal. Also Crossbeam has
a backplane chassis that needs to be configured in such a way that
it accepts all traffic continuously. If CROSSBEAM=Yes, then during a
Shorewall start, restart or clear instead of setting default
policies to DROP and then activating established connections,
Shorewall will first set default policies to ACCEPT, activate
established connections and then sets the default policies to DROP.
After that, Shorewall starts generating rules as usual.</para>
<para>If CROSSBEAM=No, CROSSBEAM_BACKBONE is not used. If
CROSSBEAM_BACKBONE is set to Yes, CROSSBEAM_BACKBONE indicates the
network interface used by the backbone.</para>
<para>If not specified or if specified as empty (e.g., CROSSBEAM="")
then CROSSBEAM=No is assumed.</para>
</listitem>
</varlistentry>
</variablelist>
</section>