BRAS L2 DHCP Radius Proxy Example [Документация VAS Experts]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
en:dpi:bras_bng:use_cases:dpi_bestpractice_brasl2radiusproxy [2023/08/28 13:48] – created elena.krasnobryzhen: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>2}} {{indexmenu_n>2}}
 ===== Description ===== ===== Description =====
-{{ dpi:qoe:use_cases:bras_l2_dhcp_radius_proxy.png?direct&600 |}}+{{ :en:dpi:bras_bng:use_cases:dpi_bestpractice_brasl2radiusproxy:bras_l2_dhcp_radius_proxy.png?nolink&900 |}}
 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. It is necessary to specify the Static Route, since VAS Experts DPI does not support OSPF and BGP at the moment.+  - Router - is responsible for packets transmission to the Internet and the backward routing. At the moment the Static Route scenario and the scenario with [[en:dpi:dpi_components:router|OSPF and BGP routing configuration]] on SSG are possible.
  
 ===== Scenario ===== ===== Scenario =====
-{{ dpi:qoe:use_cases:bras_l2_dhcp_radius_proxy_сценарий.png?direct&600 |}}+{{ :en:dpi:bras_bng:use_cases:dpi_bestpractice_brasl2radiusproxy:scenario_dhcp.png?nolink&700 |}}
 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, you can also transmit session parameters affecting the passage of subscriber traffic. When passed, the Session-Timeout is the lease time. When obtaining DHCP and traffic (IP) parameters separately, you can specify different Session-Timeout values, which, of course, will be quite convenient, for example, issue a lease time of 6 hours, but at the same time re-authorize traffic parameters every hour. 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, you can also transmit session parameters affecting the passage of subscriber traffic. When passed, the Session-Timeout is the lease time. When obtaining DHCP and traffic (IP) parameters separately, you can specify different Session-Timeout values, which, of course, will be quite convenient, for example, issue a lease time of 6 hours, but at the same time re-authorize traffic parameters every hour.
 The subscriber's equipment identifier is the MAC address, VLAN number or the values ​​of the Option-82 fields. The subscriber's equipment identifier is the MAC address, VLAN number or the values ​​of the Option-82 fields.