Update of /cvsroot/leaf/doc/docmanager
In directory sc8-pr-cvs1:/tmp/cvs-serv10597
Modified Files:
docid_1891.html
Log Message:
run through tidy, and css changes
Index: docid_1891.html
===================================================================
RCS file: /cvsroot/leaf/doc/docmanager/docid_1891.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** docid_1891.html 22 Feb 2003 21:22:30 -0000 1.12
--- docid_1891.html 22 Feb 2003 21:59:06 -0000 1.13
***************
*** 1,171 ****
<h3>How do I request help?</h3>
-
<p><em>Author:   Ray Olszewski<br />
Document ID:  1891<br />
Revision:  2.2<br />
Date:  2003-01-24</em></p>
-
<hr />
! <p style="margin-top: 0cm; margin-bottom: 0cm"><a
! href="http://leaf.sourceforge.net/pub/doc/docmanager/docid_1891.html";>
<strong>Print Document</strong></a></p>
-
<hr />
<!-- begin document body -->
<p><strong>Q. If I want help troubleshooting a connectivity failure
with my LEAF router, what information should I send?</strong></p>
-
<p>A. The exact information needed will vary by what trouble needs
shooting.</p>
-
<h4>Before You Post</h4>
-
<ul>
! <li>You should check the <a
! href="http://sourceforge.net/docman/?group_id=13751";>LEAF FAQs</a>
! to see if your question has a stock answer.</li>
!
! <li>You should subscribe to the <a
! href="http://lists.sourceforge.net/mailman/listinfo/leaf-user";>leaf-user</a>
mailing list, since some people with helpful knowledge will reply
<strong>only</strong> to the list.</li>
!
! <li>You should search the <a
! href="http://www.mail-archive.com/[EMAIL PROTECTED]/">
! list archives</a>, to see if your question has already been asked
! and answered (the FAQs are not always as up-to-date as we wish they
! were).</li>
! </ul>
!
! <p>Please remember we only know what is posted in your message.
! Do not leave out any information that appears to be correct,
! or was mentioned in a previous post. There have been countless
! posts by people who were sure that some part of their
! configuration was correct when it actually contained a small error.
! We tend to be skeptics where detail is lacking.</p>
!
<p>Please keep in mind that you're asking for <strong>free</strong>
technical support. Any help we offer is an act of generosity, not
an obligation. Try to make it easy for us to help you. Follow good,
courteous practices in writing and formatting your e-mail. Provide
! details that we need if you expect good answers. <em>Exact quoting
! </em> of error messages, log entries, command output, and other
! output is better than a paraphrase or summary.</p>
!
<p>When asking for help with routing or firewalling questions,
<strong>ALWAYS</strong> include this information:</p>
-
<ul>
<li>the exact name of the LEAF distribution and version you are
running.</li>
-
<li>the exact kernel version you are running<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">uname -a</pre></li>
!
<li>the complete, exact output of<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">ip addr
show</pre></li>
!
<li>the complete, exact output of<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">ip route
show</pre></li>
!
! <li>the exact wording of any <code style="color: green; font-weight:
bold">ping</code>
! failure responses, including the "ping" command itself (there are some <a
! href="http://sourceforge.net/docman/display_doc.php?docid=4099&group_id=13751";>
! FAQ entries</a> to help you).</li>
! </ul>
!
<p>Depending on the specific problem, include some or all of:</p>
-
<ul>
! <li>the exact output of the command below is typically useful for NIC-related
problems.<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">lsmod</pre></li>
!
! <li>the exact output of the commands below is typically useful for firewall-related
problems.<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">
-EITHER- (kernel 2.2.x)
! ipchains -nvL
-OR- (kernel 2.4.x)
! iptables -nvL
-and-
! iptables -t nat -nvL
-OR- (if you use Shorewall)
! /sbin/shorewall status
</pre></li>
!
! <li>the exact output of the commands below is typically useful for port-forwarding
problems.<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">
-EITHER- (kernel 2.2.x)
! ipmasqadm mfw -nL
-and-
! ipmasqadm portfw -nL
-OR- (kernel 2.4.x)
! iptables -t nat -nvL</pre></li>
!
! <li>any messages from <code style="color: green; font-weight: bold">dhclient</code>
in your logs<br />
typically for the setup of DHCP-dynamic external connections.</li>
! <br>
! <li>any messages from <code style="color: green; font-weight: bold">ppp</code> or
! <code style="color: green; font-weight: bold">pppoe</code> in your logs<br />
! typically for the setup of PPPoE-dynamic external connections.</li>
! </ul>
!
<p>This is not an exhaustive list; we've covered only the most
common sorts of troubleshooting problems that we see. If you have a
less common problem, or you use an ISP that does something unusual,
you may need to provide other specifics to get good help.</p>
-
<p>As a general matter, please <strong>do not edit the diagnostic
information</strong> in an attempt to conceal your IP address,
netmask, nameserver addresses, domain name, etc. These aren't
secrets, and concealing them often misleads us.</p>
-
<p><strong>Passwords</strong> are the exception to this rule:
Replace each password with the letter "x".</p>
-
<p>It isn't easy to post messages directly from a LEAF system, but
it is easy to transfer diagnostic information to a floppy. Here is
how you do this:</p>
-
<ol>
<li>Format a spare 1440KB MSDOS floppy as you normally would under
DOS, Windows, or Linux. Your floppies are probably already
formatted this way.</li>
-
<li>Remove the LEAF floppy and insert the new floppy in its
place.</li>
-
<li>Mount the floppy on the LEAF system by running this
command:<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">mount -t msdos
/dev/fd0u1440 /mnt</pre></li>
!
<li>Use the appropriate command(s) from the list above to copy
information to text files on the floppy. Examples:<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">
! cp /var/log/messages /mnt/messages.txt
! ip addr show > /mnt/address.txt
! ip route show > /mnt/route.txt
! ipchains -nvL > /mnt/filter.txt
! /usr/sbin/ipmasqadm mfw -nL > /mnt/mfw.txt
! /usr/sbin/ipmasqadm portfw -nl > /mnt/portfw.txt
! cat /proc/net/ip_masq/autofw > /mnt/autofw.txt
</pre></li>
<li>Unmount the floppy by running this command:<br />
! <pre style="color: green; font-weight: bold; margin-left: 1cm">umount /mnt</pre></li>
! <li>Remove the floppy from your LEAF system.</li>
! </ol>
!
<p>At your workstation, open the files you have just put on your
floppy and cut-and-paste them into a mailing-list e-mail. The
details depend on the operating system and e-mail software you use,
but we assume you are familiar with them.</p>
-
<h4>Acknowledgments</h4>
-
<p>Many people have contributed to the current or earlier versions
of this answer, including:<br />
--- 1,171 ----
<h3>How do I request help?</h3>
<p><em>Author:   Ray Olszewski<br />
Document ID:  1891<br />
Revision:  2.2<br />
Date:  2003-01-24</em></p>
<hr />
! <p style="margin-top: 0cm; margin-bottom: 0cm">
! <a href="http://leaf.sourceforge.net/pub/doc/docmanager/docid_1891.html";>
<strong>Print Document</strong></a></p>
<hr />
<!-- begin document body -->
<p><strong>Q. If I want help troubleshooting a connectivity failure
with my LEAF router, what information should I send?</strong></p>
<p>A. The exact information needed will vary by what trouble needs
shooting.</p>
<h4>Before You Post</h4>
<ul>
! <li>You should check the
! <a href="http://sourceforge.net/docman/?group_id=13751";>LEAF
! FAQs</a> to see if your question has a stock answer.</li>
! <li>You should subscribe to the
! <a href="https://lists.sourceforge.net/mailman/listinfo/leaf-user";>leaf-user</a>
mailing list, since some people with helpful knowledge will reply
<strong>only</strong> to the list.</li>
! <li>You should search the list archives, to see if your question
! has already been asked and answered (the FAQs are not always as
! up-to-date as we wish they were).
! <ul>
! <li>
! <a href="http://sourceforge.net/mailarchive/forum.php?forum_id=5483";>
! SourceForge</a></li>
! <li>
! <a href="http://www.mail-archive.com/leaf-user%40lists.sourceforge.net/";>
! Mail Archive</a></li>
! <li><a href="http://marc.theaimsgroup.com/?l=leaf-user";>Mailing
! list ARChives</a></li></ul></li></ul>
! <p>Please remember we only know what is posted in your message. Do
! not leave out any information that appears to be correct, or was
! mentioned in a previous post. There have been countless posts by
! people who were sure that some part of their configuration was
! correct when it actually contained a small error. We tend to be
! skeptics where detail is lacking.</p>
<p>Please keep in mind that you're asking for <strong>free</strong>
technical support. Any help we offer is an act of generosity, not
an obligation. Try to make it easy for us to help you. Follow good,
courteous practices in writing and formatting your e-mail. Provide
! details that we need if you expect good answers. <em>Exact
! quoting</em> of error messages, log entries, command output, and
! other output is better than a paraphrase or summary.</p>
<p>When asking for help with routing or firewalling questions,
<strong>ALWAYS</strong> include this information:</p>
<ul>
<li>the exact name of the LEAF distribution and version you are
running.</li>
<li>the exact kernel version you are running<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
! ash# <strong>uname -a</strong>
! </pre></li>
<li>the complete, exact output of<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
! ash# <strong>ip addr show</strong>
! </pre></li>
<li>the complete, exact output of<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
! ash# <strong>ip route show</strong>
! </pre></li>
! <li>the exact wording of any
! <code style="font-weight: bold">ping</code> failure responses,
! including the <code style="font-weight: bold">ping</code> command
! itself (there are some
! <a
href="http://sourceforge.net/docman/display_doc.php?docid=4099&group_id=13751";>
! FAQ entries</a> to help you).</li></ul>
<p>Depending on the specific problem, include some or all of:</p>
<ul>
! <li>the exact output of the command below is typically useful for
! NIC-related problems.<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
! ash# <strong>lsmod</strong>
! </pre></li>
! <li>the exact output of the commands below is typically useful for
! firewall-related problems.<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
-EITHER- (kernel 2.2.x)
! ash# <strong>ipchains -nvL</strong>
-OR- (kernel 2.4.x)
! ash# <strong>iptables -nvL</strong>
-and-
! ash# <strong>iptables -t nat -nvL</strong>
-OR- (if you use Shorewall)
! ash# <strong>/sbin/shorewall status</strong>
</pre></li>
! <li>the exact output of the commands below is typically useful for
! port-forwarding problems.<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
-EITHER- (kernel 2.2.x)
! ash# <strong>ipmasqadm mfw -nL</strong>
-and-
! ash# <strong>ipmasqadm portfw -nL</strong>
-OR- (kernel 2.4.x)
! ash# <strong>iptables -t nat -nvL</strong>
! </pre></li>
! <li>any messages from
! <code style="font-weight: bold">dhclient</code> in your logs<br />
typically for the setup of DHCP-dynamic external connections.</li>
! <li style="list-style: none"><br /></li>
! <li>any messages from <code style="font-weight: bold">ppp</code> or
! <code style="font-weight: bold">pppoe</code> in your logs<br />
! typically for the setup of PPPoE-dynamic external
! connections.</li></ul>
<p>This is not an exhaustive list; we've covered only the most
common sorts of troubleshooting problems that we see. If you have a
less common problem, or you use an ISP that does something unusual,
you may need to provide other specifics to get good help.</p>
<p>As a general matter, please <strong>do not edit the diagnostic
information</strong> in an attempt to conceal your IP address,
netmask, nameserver addresses, domain name, etc. These aren't
secrets, and concealing them often misleads us.</p>
<p><strong>Passwords</strong> are the exception to this rule:
Replace each password with the letter "x".</p>
<p>It isn't easy to post messages directly from a LEAF system, but
it is easy to transfer diagnostic information to a floppy. Here is
how you do this:</p>
<ol>
<li>Format a spare 1440KB MSDOS floppy as you normally would under
DOS, Windows, or Linux. Your floppies are probably already
formatted this way.</li>
<li>Remove the LEAF floppy and insert the new floppy in its
place.</li>
<li>Mount the floppy on the LEAF system by running this
command:<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
! ash# <strong>mount -t msdos /dev/fd0u1440 /mnt</strong>
! </pre></li>
<li>Use the appropriate command(s) from the list above to copy
information to text files on the floppy. Examples:<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
! ash# <strong>cp /var/log/messages /mnt/messages.txt</strong>
! ash# <strong>ip addr show > /mnt/address.txt</strong>
! ash# <strong>ip route show > /mnt/route.txt</strong>
! ash# <strong>ipchains -nvL > /mnt/filter.txt</strong>
! ash# <strong>/usr/sbin/ipmasqadm mfw -nL > /mnt/mfw.txt</strong>
! ash# <strong>/usr/sbin/ipmasqadm portfw -nl > /mnt/portfw.txt</strong>
! ash# <strong>cat /proc/net/ip_masq/autofw > /mnt/autofw.txt</strong>
</pre></li>
<li>Unmount the floppy by running this command:<br />
! <pre width="72"
! style="background-color: #DCDCDC; border-style: ridge; padding: 1%">
! ash# <strong>umount /mnt</strong>
! </pre></li>
! <li>Remove the floppy from your LEAF system.</li></ol>
<p>At your workstation, open the files you have just put on your
floppy and cut-and-paste them into a mailing-list e-mail. The
details depend on the operating system and e-mail software you use,
but we assume you are familiar with them.</p>
<h4>Acknowledgments</h4>
<p>Many people have contributed to the current or earlier versions
of this answer, including:<br />
***************
*** 175,190 ****
Dave Emmons, Bill Pierce, Chris Hill, and Paul Batozech. Apologies
to anybody we missed.</p>
-
<!-- end document body -->
<hr />
<p style="margin-top: 0cm">If you still have questions or concerns
! regarding this document, please feel free to either <a
! href="http://lists.sourceforge.net/lists/listinfo/leaf-user";>post
! on the mailing list</a> or <a
! href="https://sourceforge.net/tracker/?func=add&group_id=13751&atid=213751";>
submit a support request</a>. A member of the LEAF community will
be glad to assist you further.</p>
-
-
-
-
--- 175,185 ----
Dave Emmons, Bill Pierce, Chris Hill, and Paul Batozech. Apologies
to anybody we missed.</p>
<!-- end document body -->
<hr />
<p style="margin-top: 0cm">If you still have questions or concerns
! regarding this document, please feel free to either
! <a href="http://lists.sourceforge.net/lists/listinfo/leaf-user";>post
! on the mailing list</a> or
! <a
href="https://sourceforge.net/tracker/?func=add&group_id=13751&atid=213751";>
submit a support request</a>. A member of the LEAF community will
be glad to assist you further.</p>
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits
