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

some correctiosn ot the support guide, I doubt this will

Browse Source 
help, but let's see..


git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3761 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
judas_iscariote 2006-03-30 19:54:29 +00:00
parent 4d750aa835
commit d4cd2e60bd
1 changed files with 27 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

55
docs/support.xml
View File

@ -94,6 +94,23 @@
<graphic align="center" fileref="images/Troubleshoot.png" /> <graphic align="center" fileref="images/Troubleshoot.png" />
<orderedlist> <orderedlist>
<important>
<para><emphasis role="bold">Please don't use distribution specific
programs like "service" or init scripts to start/restart Shorewall
while trying to solve a problem</emphasis>, just follow carefully the
instructions below.</para>
</important>
<important>
<para>As a general matter, <emphasis role="bold">please do not edit
the diagnostic information</emphasis> in an attempt to conceal your IP
address, netmask, nameserver addresses, domain name, etc. These
<emphasis role="bold">aren't secrets</emphasis>, and concealing them
often misleads us (and 80% of the time, a cracker could derive them
anyway from information contained in the SMTP headers of your
post).</para>
</important>
<listitem> <listitem>
<para>If your problem is that an <emphasis <para>If your problem is that an <emphasis
role="bold">error</emphasis> occurs when you try to role="bold">error</emphasis> occurs when you try to
@ -134,20 +151,20 @@ gateway:~#</programlisting>
similar to this:</para> similar to this:</para>
<blockquote> <blockquote>
<programlisting>Shorewall-2.5.4 Status at gateway - Tue Aug 30 14:07:29 PDT 2005 <programlisting>Shorewall-3.0.6 Status at gateway - Thu Mar 30 14:07:29 PDT 2006
Shorewall is running Shorewall is running
State:Started (Tue Aug 30 07:18:07 PDT 2005)</programlisting> State:Started (Thu Mar 30 14:07:29 PDT 2006)</programlisting>
</blockquote> </blockquote>
<para>If Shorewall has not started properly, you will see output <para>If Shorewall has not started properly, you will see output
similar to this:</para> similar to this:</para>
<blockquote> <blockquote>
<programlisting>Shorewall-2.5.4 Status at gateway - Tue Aug 30 14:08:11 PDT 2005 <programlisting>Shorewall-3.0.6 Status at gateway - Thu Mar 30 14:08:11 PDT 2006
Shorewall is stopped Shorewall is stopped
State:Stopped (Tue Aug 30 14:08:11 PDT 2005)</programlisting> State:Stopped (Thu Mar 30 14:08:11 PDT 2006)</programlisting>
</blockquote> </blockquote>
<para>The "State:" refers to the <ulink <para>The "State:" refers to the <ulink
@ -190,15 +207,6 @@ State:Stopped (Tue Aug 30 14:08:11 PDT 2005)</programlisting>
(IP address) and what host (IP address) you are trying to connect (IP address) and what host (IP address) you are trying to connect
to.</para> to.</para>
</listitem> </listitem>
<listitem>
<para><emphasis role="bold">Please do not edit the diagnostic
information</emphasis> in an attempt to conceal your IP address,
netmask, nameserver addresses, domain name, etc. These <emphasis
role="bold">aren't secrets</emphasis>, and concealing them often
misleads us and may prevent your problem from being looked at all
together.</para>
</listitem>
</orderedlist> </orderedlist>
</listitem> </listitem>
@ -245,11 +253,12 @@ State:Stopped (Tue Aug 30 14:08:11 PDT 2005)</programlisting>
<listitem> <listitem>
<para>Please keep in mind that you're asking for <emphasis <para>Please keep in mind that you're asking for <emphasis
role="bold">free</emphasis> technical support. Any help we offer is an role="bold">free</emphasis> technical support. Any help we offer is an
act of generosity, not an obligation. Try to make it easy for us to act of generosity, not an obligation. <emphasis role="bold">Try to
help you. Follow good, courteous practices in writing and formatting make it easy for us to help you</emphasis>. Follow good, courteous
your e-mail. Provide details that we need if you expect good answers. practices in writing and formatting your e-mail. Provide details that
Exact quoting of error messages, log entries, command output, and we need if you expect good answers. Exact quoting of error messages,
other output is better than a paraphrase or summary.</para> log entries, command output, and other output is better than a
paraphrase or summary.</para>
</listitem> </listitem>
<listitem> <listitem>
@ -275,16 +284,6 @@ State:Stopped (Tue Aug 30 14:08:11 PDT 2005)</programlisting>
useful.</para> useful.</para>
</listitem> </listitem>
<listitem>
<para>As a general matter, <emphasis role="bold">please do not edit
the diagnostic information</emphasis> in an attempt to conceal your IP
address, netmask, nameserver addresses, domain name, etc. These
<emphasis role="bold">aren't secrets</emphasis>, and concealing them
often misleads us (and 80% of the time, a hacker could derive them
anyway from information contained in the SMTP headers of your
post).</para>
</listitem>
<listitem> <listitem>
<para>Do you see any <quote>Shorewall</quote> messages <para>Do you see any <quote>Shorewall</quote> messages
(<quote><command>/sbin/shorewall show log</command></quote>) when you (<quote><command>/sbin/shorewall show log</command></quote>) when you