- **Disabling EAP.** within this build, disabling is not strictly required, but EAP may cause errors when enabling the ''radiusd'' unit, so it is recommended to disable it. go to the directory ''/etc/raddb/sites-available/default
+
- **Disabling EAP.** Within this build, complete removal is not required, but EAP may cause errors when enabling the ''radiusd'' unit, so it should be disabled. Go to the configuration files ''/etc/raddb/sites-available/default'' and ''/etc/raddb/sites-enabled/inner-tunnel''\\ Disable EAP in the following sections:<code bash>authorize {
-
/etc/raddb/sites-enabled/inner-tunnel''\\ Disable EAP in the following sections:<code bash>
+
-
authorize {
+
# eap {
# eap {
# ok = return
# ok = return
Line 17:
Line 15:
post-proxy {
post-proxy {
# eap
# eap
-
</code>If necessary, also remove EAP files from the modules ''/etc/raddb/mods-available/eap'' and ''/etc/raddb/mods-enabled/eap''.
+
</code> Also, if necessary, remove the EAP file from the module ''/etc/raddb/mods-enabled/eap''.
- **Client/NAS configuration.** clients here refer to RADIUS clients, in this case — fastPCRF.\\ If the FreeRADIUS server is deployed on the same node as fastPCRF, no additional configuration is required — it is enough to verify the default configuration in the file ''/etc/raddb/clients.conf''.\\ If a remote NAS needs to be defined, use the same file and add a client description, for example:<code bash>
- **Client/NAS configuration.** clients here refer to RADIUS clients, in this case — fastPCRF.\\ If the FreeRADIUS server is deployed on the same node as fastPCRF, no additional configuration is required — it is enough to verify the default configuration in the file ''/etc/raddb/clients.conf''.\\ If a remote NAS needs to be defined, use the same file and add a client description, for example:<code bash>