<chapter id="ch7">
<title>Troubleshooting</title>

<section>
<title>A Guide to Troubleshooting</title>
<para>
If you experience any problems with xsupplicant, please use the following 
guide to troubleshoot your issues:

<itemizedlist>
<listitem>
<para>
Send us a debug output of xsupplicant, and any relevant xsupplicant options.
</para>
</listitem>
<listitem>
<para>
Tell us what card driver you are using, including revision (which can usually 
be found with dmesg)!
</para>
</listitem>
<listitem>
<para>
Send us a gdb backtrace, if possible.
</para>
</listitem>
<listitem>
<para>
Send us a copy of your configuration file.
</para>
</listitem>
<listitem>
<para>
Please make sure you *DO NOT* include passwords in your configuration file, or 
in your -d 7 output.  
</para>
</listitem>
</itemizedlist>
</para>

<para>
Run xsupplicant in debug mode by using the "-d 7" and "-f" switches and gather 
the output.  If you are segfaulting, run xsupplicant in gdb, if possible and 
provide a backtrace:
</para>

<para>
<example>
<title>Getting a GDB Backtrace</title>
<programlisting role="Debugging">
gdb xsupplicant
(gdb) set args (any args you normally use)
(gdb) run
(gdb) backtrace (after segfault)
</programlisting>
</example>
</para>

<para>
This will help us find the problem easier.
</para>

<para>
Send us a copy of your configuration (but remove the passwords please).
</para>

</section>

<section>
<title>Known Problems</title>
<para>
The following is a summary of the known issues with this version of 
xsupplicant.
<itemizedlist>
<listitem>
<para>
The supplicant may get confused on wired ports that are set up to allow 
more than one client per port.
</para>
</listitem>
<listitem>
<para>
Cisco 340/350 cards do not work correctly with Xsupplicant 1.0.  This appears 
to be due to the driver (or firmware?) hijacking the 0x888e frames, which 
prevents 802.1X authentication from being possible.
</para>
<para>
UPDATE: We have been successful getting a Cisco 350 card to work with the 
built-in Linux 2.6.7 Aironet driver to the extent that it will authenticate. 
The driver still has the (common) rekeying bug.
</para>
<para>
This means that it should be fairly easy to fix the Kernel driver.  We are 
still unsure what caused this.
</para>
</listitem>
</itemizedlist>

</para>
</section>


</chapter>
