Eap in v4

[Aleksandr Stepanov]

there is two reasons for v4

1) multi tenant - auth and accounting comes to few providers based on NAS-Identifier
2) dynamic clients behind nat and i cant share one secret for all clients

in v3 i cant bind radius secret to NAS-Identifier or/and Called-Station-Id

-- 
Best regards, Aleksandr Stepanov.


21.03.2018, 16:28, "Alan Buxey" <alan.buxey at gmail.com>:
> thats fine - you can modify the config into all kinds of weird things
> - however, why are you looking at v4? get your stuff
> running in v3 for now.
>
> alan
>
> On 21 March 2018 at 12:44, Aleksandr Stepanov <alex-eri at ya.ru> wrote:
>>  Using default is not flexible. I want to create project with radius attached to business logic, not business on top of freerad. SQL scheme would be very different with Freeradius defaut.
>>
>>  --
>>  Best regards, Aleksandr Stepanov.
>>
>>  21.03.2018, 10:36, "Alan DeKok" <aland at deployingradius.com>:
>>>  On Mar 20, 2018, at 7:17 PM, Aleksandr Stepanov <alex-eri at ya.ru> wrote:
>>>>   solution comes faster if asked)
>>>>
>>>>   authenticate mschap {
>>>>           mschap
>>>>   }
>>>
>>>    An even faster solution is "don't destroy the default configuration". Over-writing the v4 configuration with files from v3 is wrong. If you want to upgrade, read raddb/README.md
>>>
>>>    And repeat after me: Use the default configuration. It works.
>>>
>>>    Alan DeKok.
>>>
>>>  -
>>>  List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>>  -
>>  List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html