Hi Alan, Thanks for setting me straight. I will do more reading, The major reason for my "lazy attitude" (not giving up though) is your prompt and helpful responses (why bother reading/researching if Alan can help right away). And perhaps I took your "no. I don't rewrite documentation for vendors." response too literally. But your advice is already helping. E.g. the actual client requests behave better than the Meraki test applet. So maybe it's not even worth bothering with that particular error, because it does point to a problem on the client side, for which I don't really care much. So, thank you. Gleb On Thu, Apr 23, 2020 at 7:50 PM Alan DeKok <aland@deployingradius.com> wrote:
On Apr 23, 2020, at 5:52 PM, Gleb Lisikh <in4bit.general@gmail.com> wrote:
If you read the following instructions, where do you think the changes
will need to be made if eap.conf file is nowhere to be found?
I *did* tell you to edit mods-available/eap.
Or, if you read the documentation in raddb/README.rst, you can look for "eap.conf". The file has moved, and the move is documented.
This whole business of "I give up, you tell me what to do" is just not acceptable.
Edit /etc/freeradius/eap.conf with the following changes • Change default_eap_type to “tls” • Comment out all the authentication methods sections except for tls • Comment out “private_key_password” with # • Change private_key_file to ${certdir}/radius.key • Change certificate_file to ${certdir}/radius.crt • Change CA_file to ${cadir}/ca.crt
If you read the file I told you to read, you would see that those configuration items are in the file.
It is very much inappropriate to ask for help, and then refuse to follow the advice you're given. If you can't be bothered to follow instructions, I can't be bothered to give instructions.
Alan DeKok.