Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:dpi:bras_bng:modes_and_architecture [2024/11/27 05:36] – [L3-Connected BRAS] elena.krasnobryzh | en:dpi:bras_bng:modes_and_architecture [2025/04/01 08:04] (current) – [BRAS components] elena.krasnobryzh | ||
---|---|---|---|
Line 12: | Line 12: | ||
* Application of platform services (CG-NAT, Whitelist and Captive Portal, Web-filtering, | * Application of platform services (CG-NAT, Whitelist and Captive Portal, Web-filtering, | ||
* Exporting traffic information in IPFIX and Netflow v5 format (Full NetFlow, Clickstream, | * Exporting traffic information in IPFIX and Netflow v5 format (Full NetFlow, Clickstream, | ||
- | - **fastPCRF** - responsible for interaction of the platform with the telecom operator' | + | - **fastPCRF** - responsible for interaction of the platform with the telecom operator' |
- **Router** - used to announce routes using BGP and OSPF protocols with VRF support. | - **Router** - used to announce routes using BGP and OSPF protocols with VRF support. | ||
- **DHCP** - KEA local DHCP server is used. SSG can operate in one of the modes: | - **DHCP** - KEA local DHCP server is used. SSG can operate in one of the modes: | ||
Line 31: | Line 31: | ||
{{youtube> | {{youtube> | ||
L2-Connected BRAS/BNG and the subscriber are in the same L2 domain. The SSG sees the original MAC addresses, VLAN or Q-in-Q, ARP and DHCP requests, based on which RADIUS requests are generated.\\ | L2-Connected BRAS/BNG and the subscriber are in the same L2 domain. The SSG sees the original MAC addresses, VLAN or Q-in-Q, ARP and DHCP requests, based on which RADIUS requests are generated.\\ | ||
- | BRAS/BNG L2 options: | + | BRAS L2 options: |
- | * DHCP - The subscriber | + | * DHCP — The subscriber |
- | * Static IP - Subscriber | + | * Static IP — The subscriber |
- | * PPPoE - Subscriber | + | * PPPoE — Subscriber |
+ | * PPPoL2TP — Subscriber raises L2TP and PPP tunnels and by login/ | ||
==== L2-Connected BRAS/BNG specific functions ==== | ==== L2-Connected BRAS/BNG specific functions ==== | ||
Line 47: | Line 48: | ||
===== Advantages of SSG compared to other BRAS solutions ===== | ===== Advantages of SSG compared to other BRAS solutions ===== | ||
BRAS/BNG with DPI technology when operating in a distributed network has many advantages and capabilities over traditional solutions: | BRAS/BNG with DPI technology when operating in a distributed network has many advantages and capabilities over traditional solutions: | ||
- | * Traffic control and prioritization by applications and autonomous systems in the accessible band of each uplink | + | * Traffic control and prioritization by applications and autonomous systems in the accessible band of each uplink. |
- | * Limiting the bandwidth occupied by torrent when approaching the channel upper boundary | + | * Limiting the bandwidth occupied by torrent when approaching the channel upper boundary. |
- | * Traffic prioritization by applications and AS within the Subscriber’s data plan (this option is relevant for corporate clients: a number of corporate users work within single data plan. Bandwidth for them needs to be allocated so as not to interfere with each other) | + | * Traffic prioritization by applications and AS within the Subscriber’s data plan (this option is relevant for corporate clients: a number of corporate users work within |
- | * Support for subscribers | + | * Support for Subscribers |
- | * Redirection of Subscribers with zero balance to Captive Portal with an Allow list of resources. For example, bank resources for payment based on domain name or URL, including options with wildcard asterisks | + | * Redirection of Subscribers with zero balance to Captive Portal with an Allow list of resources. For example, bank resources for payment based on domain name or URL, including options with wildcard asterisks. |
- | * Ability to gather | + | * Ability to capture |
- | * Support for regulatory and law enforcement requirements, | + | * Support for regulatory and law enforcement requirements, |
- | * Interaction with SORM (work as a puller SORM-3) | + | * Interaction with SORM (work as a puller SORM-3). |