2. FreeRADIUS implementation

1. Install FreeRADIUS with database driver

Add the package "freeradius-mysql" as a dependency to nmsprime-provbase

adapt install scripts

like starting & enabling,

create database & users

populating schema's

Validation Rule: If device type = TR-69 config file parameters must be in JSON (also for validation)

NOTE:

A new definition for string replacement syntax seems to be required for JSON TR-69 since it uses {}-brackets.
For example in DOCSIS configfile a {provbase.ro_community.0} will be replaced with SQL datas –> this syntac must be replaced
See 3. TR-69 implementation example API call

Configfile MUST be second entry after "Name"

add "username" and "password" to Modem table and MVC

dynamically display or hide fields depending on if configfile is DOCSIS or TR-69

rename

type select e.g. enum ('CMTS', 'BRAS') or similar

	NMS PRIME Model (MVC)	FreeRADIUS table	database relation	Always

	NMS PRIME Model (MVC)	FreeRADIUS table	database relation	Always
1.	QoS	usergroup	1 : 1	YES. every QoS entry is a RADIUS usergroup)
2.	Modem	radcheck	1 : 1	NO. Only for Non-DOCSIS devices
3.	NetGw	nas	1 : 1	Only for NetGw of type BRAS/BNG

Reference:

Create Mapping between with an QoS Observer and RADIUS usergroup
(take care that create, delete, update syncs with FreeRADIUS)

Fields that MUST be synchronised

Create Mapping between with an Modem Observer and RADIUS radcheck
(take care that create, delete, update syncs with FreeRADIUS)

Fields that MUST be synchronised

nmsprime.modem.username –> radius.radcheck.UserName

nmsprime.modem.password –> radius.radcheck.Value

...

Create Mapping between RADIUS user and RADIUS usergroup according to subscribed QoS

Create mapping between NetGw (only of type BRAS) and RADIUS nas

Github: