Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
en:dpi:bras_bng:use_cases:dpi_bestpractice_brasl2radiusproxy [2023/08/28 13:48] – created elena.krasnobryzh | en:dpi:bras_bng:use_cases:dpi_bestpractice_brasl2radiusproxy [2024/09/26 15:29] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 2: | Line 2: | ||
{{indexmenu_n> | {{indexmenu_n> | ||
===== Description ===== | ===== Description ===== | ||
- | {{ dpi:qoe: | + | {{ :en:dpi:bras_bng:use_cases: |
BRAS DHCP L2 mode means that the subscriber recieves an IP-address via DHCP Proxy and proceeds to ААА in the Billing system. Then the subscriber is terminated by Stingray Service Gateway(SSG) and transferred to border equipment. | BRAS DHCP L2 mode means that the subscriber recieves an IP-address via DHCP Proxy and proceeds to ААА in the Billing system. Then the subscriber is terminated by Stingray Service Gateway(SSG) and transferred to border equipment. | ||
Line 10: | Line 10: | ||
- FastPCRF - proxying requests between fastDPI and Radius | - FastPCRF - proxying requests between fastDPI and Radius | ||
- Radius server - accepts requests from fastPCRF and generates responses with specified attributes | - Radius server - accepts requests from fastPCRF and generates responses with specified attributes | ||
- | - Router - is responsible for packets transmission to the Internet and the backward routing. | + | - Router - is responsible for packets transmission to the Internet and the backward routing. |
===== Scenario ===== | ===== Scenario ===== | ||
- | {{ dpi:qoe:use_cases:bras_l2_dhcp_radius_proxy_сценарий.png?direct&600 |}} | + | {{ :en:dpi:bras_bng:use_cases:dpi_bestpractice_brasl2radiusproxy: |
By DHCP request - In this case, when BRAS fixes DHCP requests from the subscriber network, it generates the corresponding Radius requests to obtain DHCP lease parameters that are communicated to the subscriber. In addition, in response to DHCP authentication, | By DHCP request - In this case, when BRAS fixes DHCP requests from the subscriber network, it generates the corresponding Radius requests to obtain DHCP lease parameters that are communicated to the subscriber. In addition, in response to DHCP authentication, | ||
The subscriber' | The subscriber' |