Defining and enabling virtual servers

FreeRADIUS has two virtual servers enabled by default. They are located under the sites-enabled sub-directory of the FreeRADIUS configuration directory. They are:

• default: The name pretty much says what the virtual server does. This virtual server handles all the default requests that are not explicitly specified to be handled by a virtual_server directive. We have used this virtual server exclusively up to now.
• inner-tunnel: This virtual server is used for certain tunneled EAP requests like TTLS and PEAP.

These two virtual servers allow FreeRADIUS to handle normal RADIUS authentication requests (default) as well as EAP/TTLS and EAP/PEAP requests (inner-tunnel) out of the box.

If you look at the eap.conf file located under the FreeRADIUS configuration directory you can see the configuration of the two EAP methods specifying the inner-tunnel virtual server. The following is an excerpt from the eap.conf file:

eap {
    ...
    ttls {
    {
        ...
   ...