| Both sides previous revisionPrevious revision | |
| en:playground:opt_bras_l3:bras_steps:start [2023/10/13 14:26] – ↷ Links adapted because of a move operation elena.krasnobryzh | en:playground:opt_bras_l3:bras_steps:start [2023/12/01 15:10] (current) – removed elena.krasnobryzh |
|---|
| ====== L3 BNG/BRAS - Step by Step Guide ====== | |
| {{indexmenu_n>2}} | |
| |
| * [[en:playground:opt_bras_l3:bras_steps:radius_auth_setup:start|FastDPI configuration]] | |
| * [[en:playground:opt_bras_l3:bras_steps:radius_auth_setup:bras_auth_test|Authorization implementing]] | |
| * [[en:dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup:start|FastPCRF configuration]] | |
| * [[en:dpi:bras_bng:radius_integration:radius_auth_server_integration:start|Integration with Radius server]] | |
| * [[en:dpi:bras_bng:radius_integration:radius_auth_server_integration:radius_auth_response:start|Subscriber properties attributes]] | |
| * [[en:dpi:bras_bng:radius_integration:radius_auth_server_integration:radius_auth_response:radius_auth_access_accept:start|Radius Access-Accept]] | |
| * [[en:dpi:bras_bng:radius_integration:radius_auth_server_integration:radius_auth_response:radius_auth_access_reject:start|Radius Access-Reject]] | |
| * [[en:playground:opt_bras_l3:bras_steps:radius_auth_setup:start|Radius CoA]] | |
| * [[en:dpi:bras_bng:radius_integration:radius_accounting:start|Radius Accounting]] | |
| * [[en:dpi:bras_bng:use_cases:example_freradius3:start|FreeRadius3 configuration example]] | |
| * [[en:dpi:bras_bng:use_cases:example_freradius3:bras_freerad_tricks|FreeRadius tricks]] | |
| * [[en:playground:opt_bras_l3:bras_steps:bras_auth_ctl:start|Manual authorization status handling]] | |
| |
| [[en:playground:opt_bras_l3:start|««« BRAS]] | |
| |
| |
| ===== Description ===== | |
| The fastPCRF server actually acts as an authentication server (L3 BRAS) for the fastDPI: for outgoing client traffic fastPCRF requests the Radius server for the client authentication, policing profile (analogue of the tariff plan) and service profiles. CoA (Change of Authorization) alerts are also supported - notification of the Radius server about changes in the user settings (balance exhaustion, policing changes, etc.) | |
| |
| {{ playground:opt_bras_l3:bras_steps:bras_l3_true.png?direct&600 |}} | |
| |
| When you start the Stingray Service Gateway (SSG), the authorization state of all the users is set to "unknown". Previously stored in the fastDPI internal base (UDR) user settings are applied according to this state. When an outgoing packet is received from a local IP address, the SSG analyzes the authorization state and if it is unknown the SSG sends an authorization request to the fastPCRF server. Essentially, this is an Access-Request Radius request. \\ | |
| When the Radius server reply is received, the fastPCRF sends user properties to the fastDPI, which in turn set the authorization status either to **"authorized" (Accept-Accept)** or **"unauthorized" (Accept-Reject) state**. | |
| |
| <note important>If a subscriber resides in "unauthorized" state, the Stingray Service Gateway itself doesn't limit subscriber's traffic. In order to limit traffic the special parameters should be received within the Access-Reject, they are the following: special policing [[en:dpi:dpi_options:opt_capture:capt_portal:start|(highly truncated bandwidth)]] and [[en:dpi:dpi_options:opt_capture:start|service 5 (Allow list)]] specifying the sites an unauthorized user is allowed to access - usually it is the [[en:dpi:dpi_options:opt_capture:capt_description:start|captive portal]].</note> | |
