Skip to content
Permalink
Browse files

Reorganise howto files

  • Loading branch information
arr2036 committed Sep 22, 2019
1 parent 85260e8 commit 20ab1f810ba49a8837071a1c3268b36f8987fd56
@@ -19,11 +19,10 @@
*** xref:modules/sqlcounter.adoc[SQL-Counter]
*** xref:modules/sqlippool.adoc[SQL-IP-Pool]
** Vendors
*** xref:ascend.adoc[Ascend]
*** xref:bay.adoc[Bay]
*** xref:cisco.adoc[Cisco]
*** xref:proxim.adoc[ProxIM]
*** xref:vendors/ascend.adoc[Ascend]
*** xref:vendors/bay.adoc[Bay]
*** xref:vendors/cisco.adoc[Cisco]
*** xref:vendors/proxim.adoc[ProxIM]
** Tuning
*** xref:performance-testing.adoc[Performance Testing]
*** xref:tuning_guide.adoc[Tuning Guide]
** xref:supervise-radiusd.adoc[Supervise Radiusd]
*** xref:tuning/performance-testing.adoc[Performance Testing]
*** xref:tuning/tuning_guide.adoc[Tuning Guide]
@@ -587,17 +587,16 @@ membership_filter = "(|(<membership_user_dn_filter>=%{control:Ldap-UserDn})(<mem

== Closing comments

It is always simpler to debug LDAP issues using an LDAP-specific tool
such as `ldapsearch`. Adding a RADIUS server to the mix will just
make it more difficult to debug LDAP issues.
Therefore you should not configure FreeRADIUS to use LDAP until such time as
`ldapsearch` returns a positive result.

Similarly, it is not productive to ask questions about `ldapsearch`
and LDAP on the FreeRADIUS mailing list. The list members can help
with configuring FreeRADIUS to talk to LDAP, but they are unable to
help with debugging `ldapsearch`. Where possible, the local LDAP
administrator should be contacted for assistance.
It is always simpler to debug LDAP issues using an LDAP-specific tool such as
`ldapsearch`. Adding a RADIUS server to the mix will just make it more
difficult to debug LDAP issues. Therefore you should not configure FreeRADIUS to
use LDAP until such time as `ldapsearch` returns a positive result.

Similarly, it is not productive to ask questions about `ldapsearch` and LDAP on
the FreeRADIUS mailing list. The list members can help with configuring
FreeRADIUS to talk to LDAP, but they are unable to help with debugging
`ldapsearch`. Where possible, the local LDAP administrator should be contacted
for assistance.

We have not yet discovered an LDAP implementation that is truly incompatible
with FreeRADIUS. With sufficient diligence and perseverance you will be able to

This file was deleted.

File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
@@ -590,8 +590,8 @@ ldap {
# session_tracking:: If `yes`, then include `draft-wahl-ldap-session` tracking
# controls.
#
# These encode the `NAS-IP-Address`, `NAS-IPv6-Address`, `User-Name`, `Acct-Session-Id`,
# `Acct-Multi-Session-Id` as session tracking controls, in applicable LDAP operations.
# If yes, encodes `NAS-IP-Address`, `NAS-IPv6-Address`, `User-Name`, `Acct-Session-Id`,
# `Acct-Multi-Session-Id` as session tracking controls in applicable LDAP operations.
#
# Default `no`
#

0 comments on commit 20ab1f8

Please sign in to comment.
You can’t perform that action at this time.