From: Arran Cudbard-Bell Date: Tue, 5 Mar 2019 11:01:23 +0000 (+0800) Subject: Fix references to eap.conf X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fdcbd374fa88cbe756188e4ad039367b7e412b79;p=thirdparty%2Ffreeradius-server.git Fix references to eap.conf --- diff --git a/raddb/certs/README b/raddb/certs/README index e95f0fc048b..8ef151b82e3 100644 --- a/raddb/certs/README +++ b/raddb/certs/README @@ -64,10 +64,10 @@ $ rm -f *.pem *.der *.csr *.crt *.key *.p12 serial* index.txt* Once the final certificates have been created, you can delete the "bootstrap" command from this directory, and delete the "make_cert_command" configuration from the "tls" sub-section of -eap.conf. +"raddb/mods-available/eap". If you do not want to enable EAP-TLS, PEAP, or EAP-TTLS, then delete -the relevant sub-sections from the "eap.conf" file. +the relevant sub-sections from the "raddb/mods-available/eap" file. MAKING A ROOT CERTIFICATE @@ -183,7 +183,8 @@ with ALL operating systems. Some common issues are: see them, it will stop doing EAP. The most visible effect is that the client starts EAP, gets a few Access-Challenge packets, and then a little while later re-starts EAP. If this happens, see - the FAQ, and the comments in raddb/eap.conf for how to fix it. + the FAQ, and the comments in "raddb/mods-available/eap" for how to + fix it. - Windows requires the root certificates to be on the client PC. If it doesn't have them, you will see the same issue as above.