Wee note about Wireskark and LDAP.

doc/guide/admin/troubleshooting.sdf

@@ -73,11 +73,22 @@ H2: How to present your problem
 
 H2: Debugging {{slapd}}(8)
 
+After reading through the above sections and before e-mailing the OpenLDAP lists, you
+might want to try out some of the following to track down the cause of your problems:
+
 * Loglevel 256 is generally a good first loglevel to try for getting 
   information useful to list members on issues
 * Running {{slapd -d -1}} can often track down fairly simple issues, such as 
   missing schemas and incorrect file permissions for the {{slapd}} user to things like certs
 
+For those of you so inclined, a great LDAP Protocol Dissector is available in {[PRD:Wireshark}} 
+and is discussed at:
+
+{{URL:http://wiki.wireshark.org/LDAP}}
+
+It's very interesting to look inside the LDAP Protocol, but please do not try to use this tool
+in debugging normal problems.
+
 H2: Commercial Support
 
 The firms listed at {{URL:http://www.openldap.org/support/}} offer technical support services catering to OpenLDAP community. 

doc/guide/preamble.sdf

@@ -142,9 +142,10 @@ OpenLDAP ITS|http://www.openldap.org/its/
 OpenLDAP Software|http://www.openldap.org/software/
 OpenSSL|http://www.openssl.org/
 Perl|http://www.perl.org/
-TCL|http://www.tcl.tk/
 SDF|http://search.cpan.org/src/IANC/sdf-2.001/doc/catalog.html
+TCL|http://www.tcl.tk/
 UMLDAP|http://www.umich.edu/~dirsvcs/ldap/ldap.html
+Wireshark|http://www.wireshark.org/
 !endblock
 
 # Internet and X.500 terms