Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:bras_bng:radius_integration:radius_accounting:multisession [2024/09/26 15:29] – external edit 127.0.0.1 | en:dpi:bras_bng:radius_integration:radius_accounting:multisession [2024/12/05 15:08] (current) – elena.krasnobryzh |
|---|
| ==== Multiple sessions ==== | ====== Multiple sessions ====== |
| {{indexmenu_n>2}} | {{indexmenu_n>2}} |
| |
| For a given IP address there can be only one multi-session, but many different accounting sessions - one from each fastDPI server. The Accounting-Request always includes, along with the ''Acct-Session-Id'' attribute, the ''Acct-Multi-Session-Id'' attributes and the NAS attributes that identify a particular fastDPI server. | For a given IP address there can be only one multi-session, but many different accounting sessions - one from each fastDPI server. The Accounting-Request always includes, along with the ''Acct-Session-Id'' attribute, the ''Acct-Multi-Session-Id'' attributes and the NAS attributes that identify a particular fastDPI server. |
| |
| In the "one fastPCRF - multiple fastDPI" mode, the identification of the fastDPI server, the source of the accounting, becomes especially important. In SSG 8.3 the principle of ''NAS-IP-Address'' and ''NAS-Identifier'' attributes formation has been significantly changed: previously these attributes were set statically in fastpcrf.conf and were the same for all fastDPIs (actually fastPCRF acted as NAS), now these attributes are set separately for each fastDPI server in the [[dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup|fdpi_server]] fastpcrf.conf file. Thus, the fastDPIs now act as NAS servers. The attributes that identify NAS are included in all Radius requests, both Access-Request and Accounting-Request. . Only one of the attributes ''NAS-IP-Address'' or ''NAS-Identifier'' can be included in a request: the ''attr_nas_ip'' explicit setting in the ''fdpi_server'' parameter has the highest priority: | In the "one fastPCRF - multiple fastDPI" mode, the identification of the fastDPI server, the source of the accounting, becomes especially important. In SSG 8.3 the principle of ''NAS-IP-Address'' and ''NAS-Identifier'' attributes formation has been significantly changed: previously these attributes were set statically in fastpcrf.conf and were the same for all fastDPIs (actually fastPCRF acted as NAS), now these attributes are set separately for each fastDPI server in the [[dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup|fdpi_server]] fastpcrf.conf file. Thus, the fastDPIs now act as NAS servers. The attributes that identify NAS are included in all RADIUS requests, both Access-Request and Accounting-Request. . Only one of the attributes ''NAS-IP-Address'' or ''NAS-Identifier'' can be included in a request: the ''attr_nas_ip'' explicit setting in the ''fdpi_server'' parameter has the highest priority: |
| <code> | <code> |
| fdpi_server=127.0.0.1%lo:29000;attr_nas_ip=10.20.30.40;attr_nas_id=DPI-1 | fdpi_server=127.0.0.1%lo:29000;attr_nas_ip=10.20.30.40;attr_nas_id=DPI-1 |
