<x-flowed>Troubleshooting Request HOWTO:
Authors: Mike Noyes [EMAIL PROTECTED],
and Rick Onanian [EMAIL PROTECTED]
v1.1, 24 Nov 2000
A lrp.c0wz.com document for the LEAF Project.
________________________________________________________________________
1. Introduction
This HOWTO was created to help insure accurate and timely
troubleshooting of problems. It is intended to assist new list members,
and is in no way mandatory. However, following these instructions will
allow more people to assist you, and facilitate a faster resolution to
your problem.
1.1 Acknowledgements
We thank the following people for their corrections and suggestions:
Ray Olszewski, Charles Steinkuehler, Jeff Newmiller, Gary Shea,
Michelle Konzack, Wayne Fool, Jonathan French, Michael Leone,
Dave Emmons, Bill Pierce, Chris Hill, and Paul Batozech.
1.2 Distribution Policy
A copy of the license is available at:
http://sourceforge.net/docman/display_doc.php?docid=1812&group_id=13751
2. Things to do Before Posting
o Read all available documentation on the site where you obtained the
LEAF disk image, or files you are using.
o Check the FAQs at:
http://sourceforge.net/docman/?group_id=13751
o Fix all known bugs
- see "FAQs sec05: Fixes for Known Bugs"
o Subscribe to the LEAF mailing list at:
http://lists.sourceforge.net/mailman/listinfo/leaf-user
This is not necessary, but it is the polite thing to do.
o Optional: Search the LEAF mailing list archives at:
http://www.geocrawler.com/lists/3/SourceForge/7325/0/
This may take some time and effort. If you're not familiar with
search engines, you may find this difficult. However, in most cases
it's faster than asking list members for help.
3. Preparing a Post
When preparing a post, keep in mind that you're asking for free
technical support from people. They have no vested interest in helping
you. So, it is to your advantage to make it as easy as possible for them
to help, by including all appropriate diagnostic information. Also, be
aware that other people's machines are not the same as yours. If your
post is formatted correctly, some of the most knowledgeable people (UNIX
gurus) will be able to read it. The following is a list of things to
keep in mind:
o Keep your lines under 80 characters, and under 72 if possible.
Sometimes it is necessary to include lines longer than 80
characters. You can accomplish this by using " \" to continue a
line. Example:
averylongcommandthatyouwanttosplit \
intomultiplelinesforpostingtothelist \
sothatotherpeoplecandiagnoseyourproblem
o Use plain ASCII text. Not all email clients can properly view
styled or HTML text. Some will simply strip out the codes used for
style/HTML text, while others will display the codes in the message
and leave the recipient with a messy email message. In extreme
cases (e.g. pine), the recipient will see nothing at all.
- see "Appendix B" for instructions
o The post should have an informative Subject line, with the
important information near the beginning.
o Include all information in the body of the post. It is
inappropriate to send attachments to the list.
o Please don't edit the diagnostic information in an attempt to
conceal your IP address, netmask, nameserver address, domain name,
etc. These things aren't secret. If someone wants to do something
bad to you, he can get this information in no time.
o When you post files that include passwords, you should replace all
password characters with the letter "x".
3.1 How to Get Your Diagnostic Information Into a Post
Initially, floppies are the only way you can move information from the
LEAF box to a machine that is able to post to the list. After you have
the LEAF box working, you can use other methods to transfer the
information (e.g. ssh).
You can copy appropriate information to a floppy using the commands in
section 4.x. Before you can do this, you must understand how to mount a
floppy.
- see "Appendix C" for details on mounting and copying information to
floppies
4. Diagnostic Information
State which version of the LEAF you are using, and where you got it
from. If you used a disk image, please specify the filename. If you are
connecting to the Internet, specify the interface type (e.g. modem,
cable, xDSL, T1 etc.). Then, list a summary of instructions you have
read to get you where you are now.
Use the sections below to determine any additional information you
believe would help in diagnosing your problem. Note that lines beginning
with "#" are shell commands that assume you have mounted a floppy in
accordance with "Appendix C".
4.1 Hardware Problems
Not all of the following information is necessary. Provide appropriate
information for your troublesome hardware.
Tip: you can review boot messages with the <Shift> + <Page-Up> key
combination.
motherboard make, model, and revision
ethernet card (NIC) make, model, and revision
# free > /mnt/memory.txt
# df > /mnt/rdisk.txt
# dmesg > /mnt/dmesg.txt
# cp /var/log/syslog /mnt/syslog.txt
# cp /var/log/messages /mnt/messages.txt
# cat /proc/interrupts > /mnt/irqs.txt
# cat /proc/ioports > /mnt/io.txt
4.2 Configuration Errors
# cp /etc/network.conf /mnt/network.txt
# cp /etc/lrp.conf /mnt/lrpconf.txt
PPP Questions
modem make, model, and int/ext
# cp /etc/ppp/options /mnt/options.txt
# cp /etc/ppp/peers/provider /mnt/provide1.txt
# cp /etc/chatscripts/provider /mnt/provide2.txt
# cp /var/log/debug /mnt/debug.txt
# setserial -a /dev/ttyS0 > /mnt/ttys0.txt
# setserial -a /dev/ttyS1 > /mnt/ttys1.txt
4.3 Router Configuration
Create an ASCII art network diagram of the proposed network. Include all
interfaces on the LEAF box when you create the diagram. Also, use a mono
spaced font (e.g. Courier), and spaces instead of tabs. Templates are
available at:
http://lrp.c0wz.com/dox/diagrams
# cp /etc/network.conf /mnt/network.txt
# cp /etc/network_direct.conf /mnt/network2.txt
# netstat -nr > /mnt/route.txt
# netstat -nre > /mnt/route2.txt
Linux-2.2.x-based LEAF (EigerStein or Oxygen)
# ip addr show > /mnt/addr.txt
# ip route show > /mnt/iproute.txt
# ip neighbour show > /mnt/nbr.txt
4.4 Firewall Troubleshooting
# netstat -an > /mnt/netcon.txt
Linux-2.2.x-based LEAF (EigerStein or Oxygen)
# svi network ipfilter list > /mnt/ipfilter.txt
4.5 LEAF Package Problems
Watch as the LEAF box boots. Notice what packages it lists as it loads.
If it says (nf!) or (cpt!) after loading a package, include this
information in your post.
# free > /mnt/memory.txt
# df > /mnt/rdisk.txt
6. Appendix B - Instructions to Configure Email Clients
o Outlook Express users:
http://www.private-rx.net/no_html.shtml
http://support.microsoft.com/support/IE/InProductHelp/news_wrap.asp
o Netscape users:
http://help.netscape.com/kb/consumer/19980130-2.html
o Eudora users:
http://www.eudora.com/techsupport/kb/908hq.html
http://www.eudora.com/techsupport/kb/1900hq.html
7. Appendix C - Copying Diagnostic Information to a Floppy
1. Format a spare floppy as you normally would under DOS or Windows
(your floppies are probably already formatted). Remove the LEAF
disk and insert the new floppy in its place.
2. Mount the floppy by running this command:
# mount -t msdos /dev/fd0 /mnt
3. Then use the appropriate command(s) from section 4.x to copy
information to a text file on the floppy. Examples:
# cp /var/log/messages /mnt/messages.txt
# cp /etc/network.conf /mnt/network.txt
# cat /proc/interrupts > /mnt/irqs.txt
4. IMPORTANT! Don't forget to run sync, and umount the floppy before
removing it from the LRP box. Commands:
# sync
# umount /mnt
________________________________________________________________________
End of Troubleshooting Request HOWTO
--
Mike Noyes <[EMAIL PROTECTED]>
http://leaf.sourceforge.net/
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/leaf-user
</x-flowed>
