| Both sides previous revisionPrevious revision | |
| en:dpi:changelog:versions:ver_14 [2025/12/26 12:56] – elena.krasnobryzh | en:dpi:changelog:versions:ver_14 [2025/12/26 13:02] (current) – [Changes in version 14.1] elena.krasnobryzh |
|---|
| ===DPI=== | ===DPI=== |
| - [DPI][ajb_save_vlan] Fixed an error when the engine operates in read-only mode | - [DPI][ajb_save_vlan] Fixed an error when the engine operates in read-only mode |
| - [DPDK][tap_device] Fixed: setting the tx queue length using the ''dpdk_tx_queue_size'' option. Previously, the TAP device tx queue length was always set to 256, which caused VMware VMXNET3 Ethernet Controller to report: ETHDEV: Invalid value for nb_tx_desc(=256), should be: <= 4096, >= 512, and a product of 1 | - [DPDK][tap_device] Fixed: setting the tx queue length using the ''dpdk_tx_queue_size'' option. Previously, the tx queue length of the TAP device was always set to 256, which caused errors on the VMware VMXNET3 Ethernet Controller: ETHDEV: Invalid value for nb_tx_desc(=256), should be: <= 4096, >= 512, and a product of 1 |
| - [LAG] Fixed: added load balancing for pass packets | - [LAG] Fixed: added load balancing for pass packets |
| - [DPI][ip_node stg] Added bucket occupancy statistics. The new CLI command ''stat storage ip4 detail'' displays bucket fill statistics in IPv4 node storage | - [DPI][ip_node stg] Added statistics on bucket occupancy. The new CLI command ''stat storage ip4 detail'' outputs statistics on bucket filling in the IPv4 node storage |
| - [DPI] Added validation for the MULTIPROXY_STRONG protocol | - [DPI] Added validation for the MULTIPROXY_STRONG protocol |
| - [DPI] Improved scalability on 128-core systems | - [DPI] Improved scalability on 128-core systems |
| - [DPI][log] Improved the logging subsystem in cases of log file overflow | - [DPI][log] Improved the logging subsystem in cases of log file overflow |
| - [DPI][tethering] Added tethering detection. The parameter ''tethering_ttl_allowed = 128:64'' [hot] defines the list of allowed TTL values for subscriber traffic that are not considered tethering. Values are separated by ':'. Up to 256 values (0–255) are supported. [[en:dpi:dpi_options:opt_statistics:statistics_ipfix|Description]] | - [DPI][tethering] Added tethering detection. The parameter ''tethering_ttl_allowed = 128:64'' [hot] defines the list of allowed TTL values for subscriber traffic that are not considered tethering. Values are separated by ':'. The number of values is up to 256 (0–255). [[en:dpi:dpi_options:opt_statistics:statistics_ipfix|Description]] |
| |
| ===BNG=== | ===BNG=== |
| - [BNG][framed-route] Fixed: Framed-Route handling when the subscriber login changes. Previously, Framed-Route subnets remained bound to the old login, and all services and policing for these subnets were taken from the old login | - [BNG][framed-route] Fixed: Framed-Route delivery when a subscriber login is changed. Previously, when the login was changed, Framed-Route subnets remained attached to the old login, and all services and policing for Framed-Route subnets were taken from the old login. |
| - [BNG] Added the ''bras_disable_l3_auth'' option — explicit prohibition of L3 auth in L2 BNG mode for all subscribers. For example, only DHCP authorization will work for subscribers with the AS local meta. Default value: ''off'' (L3 auth allowed) ''bras_disable_l3_auth=off''. This option is meaningful only if ''enable_auth=1''. The option is incompatible with ''bras_dhcp_auth_mix=0'': if ''bras_dhcp_auth_mix=0'' is set, ''bras_disable_l3_auth'' is assumed to be ''off'' (L3 auth allowed), and a warning is logged to the alert log | - [BNG] Added the ''bras_disable_l3_auth'' option — an explicit prohibition of L3 auth in L2 BNG mode for all subscribers. For example, only DHCP authorization will work for subscribers with the AS local meta. Default value: ''off'' (L3 auth allowed) ''bras_disable_l3_auth=off''. This option is meaningful only if ''enable_auth=1''. The option is incompatible with the ''bras_dhcp_auth_mix=0'' mode: if ''bras_dhcp_auth_mix=0'' is set, ''bras_disable_l3_auth'' is forced to ''off'' (L3 auth allowed) and a warning is logged to the alert log. |
| - [BNG] Added a new subscriber flag — prohibit L3 auth for a specific subscriber. This flag can only be set or cleared via CLI: a new parameter ''disable_l3_auth=[1:0]'' was added to the ''subs prop set'' command (''1'' — disable L3 auth, ''0'' — allow). By default, L3 auth is allowed | - [BNG] Added a new subscriber flag — prohibition of L3 auth for a specific subscriber. This flag can be set or cleared only via CLI: a new parameter ''disable_l3_auth=[1:0]'' has been added to the ''subs prop set'' command (''1'' — disable L3 auth, ''0'' — enable). By default, L3 auth is enabled. |
| - [BNG][srcIP spoofing] Added filtering by source AS flags on the subs→inet path before packet processing to block outbound operator-side DDOS with IP spoofing.\\ Added a new fastdpi.conf option ''ip_filter_source_as_flags'' (hot) — subs traffic AS filtering. Bitmask of AS flags for source IP on the subs side.\\ Only packets whose source IP AS contains at least one of the specified flags are allowed; otherwise, the packet is dropped. AS flag values (bitmask): | - [BNG][srcIP spoofing] Added filtering by source AS flags on the subs→inet path before packet processing to block operator-originated DDoS attacks with IP address spoofing.\\ Added a new fastdpi.conf option ''ip_filter_source_as_flags'' (hot)[hot] — filtering subs traffic by AS. Bit mask of AS (autonomous system) flags for the source IP on the subs side.\\ Only packets whose source IP AS contains at least one of the specified flags are allowed for processing. Otherwise, the packet is dropped. AS flag values (bit mask): |
| * 0 - filtering disabled (default) — ''ip_filter_source_as_flags=0x0'' | * 0 — filtering disabled (default) — ''ip_filter_source_as_flags=0x0'' |
| * 0x0100 - pass | * 0x0100 — pass |
| * 0x0200 - local | * 0x0200 — local |
| * 0x0400 - peer | * 0x0400 — peer |
| * 0x0800 - term | * 0x0800 — term |
| * 0x1000 - mark1 | * 0x1000 — mark1 |
| * 0x2000 - mark2 | * 0x2000 — mark2 |
| * 0x4000 - mark3 | * 0x4000 — mark3 |
| - [BNG][PPP] Added database session utilization statistics to the ''ppp show stat'' command | - [BNG][PPP] Added database session utilization statistics to the ''ppp show stat'' command |
| - [BNG][PCEF][Policing] Added configuration of global policing from parameters passed in the ''VasExperts-Policing-Profile'' attribute with the ''BR##'' prefix | - [BNG][PCEF][Policing] Added configuration of common policing from parameters passed in the ''VasExperts-Policing-Profile'' attribute with the ''BR##'' prefix |
| - [BNG][PCEF][Services] Added configuration of a personal (''noname'') user service profile from parameters passed in the ''VasExperts-Service-Profile'' attribute with the ''BP##'' prefix | - [BNG][PCEF][Services] Added configuration of a personal (''noname'') user profile for services from parameters passed in the ''VasExperts-Service-Profile'' attribute with the ''BP##'' prefix |
| - [BNG][PCEF][rating-group] New options (cold, fastDPI restart required): | - [BNG][PCEF][rating-group] New options (cold, fastDPI restart required): |
| * ''rating_group_count'' — number of rating groups, ''0'' — RG disabled. Default value: ''0'' | * ''rating_group_count'' — number of rating groups, ''0'' — RG disabled. Default value: ''0'' |
| * ''rating_group_max_subs'' — maximum number of subscribers with RG. Default value: ''0'' (RG disabled)\\ RG storage is initialized only if billing statistics are enabled. Memory calculation for RG statistics storage: counter size per RG = 32 bytes. Total required memory:<code>32 * rating_group_count * rating_group_max_subs * num_thread</code> Example: for 10k subscribers, 256 RGs, and 8 processing threads, 625M of memory is required:<code>rating_group_count = 256 | * ''rating_group_max_subs'' — maximum number of subscribers with RG. Default value: ''0'' (RG disabled)\\ RG storage is initialized only if billing statistics are enabled. Memory calculation for RG statistics: counter size per RG = 32 bytes. Total required memory:<code>32 * rating_group_count * rating_group_max_subs * num_thread</code> For example, for 10k subscribers, 256 RGs, and 8 processing threads, 625M of memory is required:<code>rating_group_count = 256 |
| rating_group_max_subs = 10000 | rating_group_max_subs = 10000 |
| num_thread = 8 | num_thread = 8 |
| memory_required = 32 * 256 * 10000 * 8 = 625M</code> | memory_required = 32 * 256 * 10000 * 8 = 625M</code> |
| - [BNG][PCEF][rating-group][RADIUS Accounting] Output of RG statistics in RADIUS Accounting. RG statistics are sent in separate Interim-Update packets. Only non-zero RGs are transmitted. Due to the 4096-byte RADIUS packet size limit, RG data may be split into multiple Interim-Update packets.\\ To distinguish Interim-Update packets containing RG data, a new VSA ''VasExperts-Acct-Type'' (id=28, vendor 43823, integer) is used with the following values: | - [BNG][PCEF][rating-group][RADIUS Accounting] Output of RG statistics in RADIUS Accounting. RG statistics are transmitted in separate Interim-Update packets. Only non-zero RG data are sent. Due to the 4096-byte RADIUS packet size limit, RG data may be split across multiple Interim-Update packets.\\ To distinguish Interim-Updates containing RG data, a new VSA ''VasExperts-Acct-Type'' (id=28, vendor 43823, integer type) is used with the following values: |
| * ''0'' — standard Interim Update Accounting | * ''0'' — standard Interim Update Accounting |
| * ''1'' — RG data\\ Each rating group and its counters are transmitted in a *single* VSA containing the following attributes: | * ''1'' — RG data\\ Each rating group and its counters are transmitted in *one* VSA containing the following attributes: |
| * ''VasExperts-Acct-Rating-Group'' | * ''VasExperts-Acct-Rating-Group'' (new attribute of type short, 16-bit integer) — RG number; |
| * ''VasExperts-Acct-Input-Octets-64'' | * ''VasExperts-Acct-Input-Octets-64'' |
| * ''VasExperts-Acct-Output-Octets-64'' | * ''VasExperts-Acct-Output-Octets-64'' |
| * ''VasExperts-Acct-Input-Packets-64'' | * ''VasExperts-Acct-Input-Packets-64'' |
| * ''VasExperts-Acct-Output-Packets-64''\\ Packet and byte counters are output according to the ''acct_swap_dir'' option (as in Accounting).\\ RG transmission specifics: | * ''VasExperts-Acct-Output-Packets-64''\\ Packet/byte counters by direction are output according to the ''acct_swap_dir'' option (as in Accounting).\\ RG transmission specifics: |
| * RGs are optional and may be absent for a subscriber; in this case, no RG accounting is sent | * RGs are optional data and may be absent for a subscriber; accordingly, no RG accounting data will be transmitted for such a subscriber; |
| * if the RADIUS server does not acknowledge receipt of an RG packet, it is not retransmitted — fresh data will be sent in the next Interim-Update | * if receipt of an RG packet by the RADIUS server is not confirmed, it is not retransmitted — fresh data will be sent in the subscriber’s next Interim-Update; |
| * if a subscriber has RG statistics, current RG data is sent in Interim-Update packets before Acct-Stop at session termination | * if a subscriber has RG statistics, current RG data are sent in Interim-Update packets before sending Acct-Stop at session termination. |
| - [BNG][PCEF][rating-group][CLI] Added the ''subs traffic stat'' CLI command. For a specified subscriber, the command displays billing statistics and rating group statistics, if enabled | - [BNG][PCEF][rating-group][CLI] Added the ''subs traffic stat'' CLI command. The command outputs billing statistics and rating group statistics for the specified subscriber, if enabled. |
| - [BNG][PCEF][rating-group][RADIUS Accept] Added assignment of an RG service during authorization. RG statistics accumulation can be enabled only if service 9 (billing statistics) is enabled for the subscriber. RG is assigned at authorization by specifying a special service 9 profile named "RG":<code>VasExperts-Service-Profile :="9:RG"</code> If service 9 is disabled, RG accumulation is also disabled.\\ Examples: | - [BNG][PCEF][rating-group][RADIUS Accept] Added configuration of the RG service during authorization. RG statistics accumulation can be enabled only if service 9 (bill stat) is enabled for the subscriber. RG is assigned at the subscriber level during authorization by specifying a special service 9 profile named 'RG': <code>VasExperts-Service-Profile :="9:RG"</code> When service 9 is disabled, RG accumulation is also disabled.\\ Examples of configuring service 9 and RG: <code># service 9 enabled, RG disabled. Standard RADIUS Accounting is sent. |
| <code># service 9 enabled, RG disabled. Standard RADIUS Accounting is sent. | VasExperts-Enable-Service :="9:on"</code> <code># service 9 enabled, RG enabled. RG data are sent in RADIUS Accounting. |
| VasExperts-Enable-Service :="9:on"</code> | VasExperts-Service-Profile :="9:RG"</code> <code># service 9 disabled, RG disabled. Standard RADIUS Accounting and RG are not sent. |
| <code># service 9 enabled, RG enabled. RG data is sent in RADIUS Accounting. | |
| VasExperts-Service-Profile :="9:RG"</code> | |
| <code># service 9 disabled, RG disabled. Neither standard RADIUS Accounting nor RG is sent. | |
| VasExperts-Enable-Service :="9:off"</code> | VasExperts-Enable-Service :="9:off"</code> |
| | - [BNG][SHCV][hot] Added activity monitoring for static IP L2 subscribers (subscribers for whom RADIUS returned the ''VasExperts-L2-User=1'' flag during L3 authorization).\\ New options (all hot): |
| | * ''bras_subs_shcv_interval'' — inactivity interval, seconds; ''0'' — SHCV disabled |
| | * ''bras_subs_shcv_retry_timeout'' — ARP request response wait time, seconds; default = ''3'' |
| | * ''bras_subs_shcv_retry_count'' — number of ARP requests; default = ''3'' |
| | * ''bras_shcv_trace'' — SHCV tracing; default = ''off''\\ \\ If no traffic is received from the subscriber for ''bras_subs_shcv_interval'' seconds, fastDPI starts pinging the subscriber by sending unicast ARP requests on behalf of the subscriber gateway. The ARP response wait time is ''bras_subs_shcv_retry_timeout'' seconds. If no response is received to ''bras_subs_shcv_retry_count'' consecutive ARP requests, or the ARP response contains a different MAC address, the subscriber is considered inactive, its authorization status is reset, and the accounting session is stopped. |
| | - [BNG][DHCP][hot] New values ''2'' and ''4'' are available for the ''bras_dhcp_check_secondary_keys'' option. Full option description:\\ \\ ''bras_dhcp_check_secondary_keys'' — control of secondary unique keys (opt82/QinQ) [hot]\\ In DHCP, the primary keys are ClientId (opt61) or, if ClientId is not specified, the client MAC address. In secondary key control mode, if another DHCP session is found by at least one secondary key, it will be closed (Acct Stop is sent). |
| | * ''0'' (default) — do not control secondary keys |
| | * ''1'' — control all secondary keys — QinQ and opt82 |
| | * ''2'' — control only opt82 |
| | * ''4'' — control only QinQ |
| | - [BNG][L2TP] Fixed: crash when receiving a duplicate out-of-order ctl packet |
| | - [BNG][dhcp-relay] Added the ability to preserve the siaddr field value.\\ New flag in the ''bras_dhcp_server'' option: ''keep_siaddr=1'' — preserve the DHCP packet siaddr field. Example:<code bash>bras_dhcp_server=188.227.73.42%eth0;arp_proxy=1;reply_port=67;keep_siaddr=1</code> By default, the siaddr field may be modified to hide the real DHCP server address. |
| | - [BNG][CLI] Added the `subs db stat` command to display L2 BNG database statistics |
| | - [BNG][DHCP6] Fixed: crash when processing DHCPv6 with an invalid UDP header length |
| | |
| | ===NAT=== |
| | - [CG-NAT] Added ''rx_dispatcher=3'' — a method with uniform load balancing across an arbitrary number of threads with support for NAT 1:1 and the requirement to assign specific addresses |
| | - [CG-NAT] Accounting of translation lifetime in the ''fdpi_ctrl list status --service 11 --login UserName (--ip IP)'' command. Additional fields were added to the command output: ''active_sess_tcp'' — number of active NAT translations for TCP and ''active_sess_udp'' — number of active NAT translations for UDP.\\ Translation activity is determined by the time of its last use and the lifetime parameter configured in the cluster options. |
| | - [CG-NAT][CLI] Accounting of translation lifetime in the ''nat show <internal_ip> [<lifetime>]'' command. Displays a list of all NAT translations for the specified gray IP. A translation record looks as follows: |
| | * nat_type — NAT type (0 — CGNAT, 1 — NAT 1:1) |
| | * protocol — L4 protocol (0 — TCP, 1 — UDP) |
| | * internal_ip — gray IP |
| | * internal_port — gray port |
| | * dest_ip — destination IP |
| | * dest_port — destination port |
| | * external_ip — white IP |
| | * external_port — white port |
| | * active — translation activity flag (true if active)\\ Translation activity is determined by the time of its last use and the lifetime parameter configured in the cluster options. If ''<lifetime>'' (in seconds) is specified, its value is used as the translation lifetime. |
| | |
| | ===CLI=== |
| | - [CLI] Added the ''subs bind show'' command to view the list of IP addresses bound to the login ''<login>'':<code>subs bind show <login> [memory|udr]</code>Two modes: |
| | * ''memory'' (default) displays IP-to-login bindings as currently configured in fastDPI |
| | * ''udr'' — displays IP-to-login bindings from UDR\\ The output of these two modes may differ: not all IP↔login bindings are stored in UDR; for example, for Framed-Route subnets, the login binding is created only in memory, while the framed-route subnets themselves are stored in UDR in a separate table; see the ''cli framed route ?'' CLI command group |
| | - [CLI] Added the ''stat http'' CLI command. This command outputs internal statistics similar to those in fastdpi_stat.log: |
| | * Detailed statistics on HTTP |
| | * Detailed statistics on SSL_SAVEBL |
| | * Detailed statistics on QUIC_IETF_SAVEBL |
| | * Detailed statistics on BitTorrent |
| | - [CLI] Fixed the ''list status --service 11'' (NAT) and ''nat show'' commands |
| | |
| | ===IPFIX=== |
| | - [IPFIX] Storage of TTL information from the IP packet header. [[en:dpi:dpi_options:opt_statistics:statistics_ipfix#шаблон_экспорта_в_формате_ipfix_netflow_v10_для_протокола_ipv4|Description]]\\ TTL statistics added to Full NetFlow in IPFIX format: |
| | * Packet TTL, id 192. The field is used for both directions: subs2inet and inet2subs |
| | * Rating group, id 2020 |
| | - [IPFIX] Fixed an error in time conversion to unix format |
| | - [IPFIX] New 64-bit fields added to Full NetFlow IPFIX. [[en:dpi:dpi_options:opt_statistics:statistics_ipfix#шаблон_экспорта_в_формате_ipfix_netflow_v10_для_протокола_ipv4|Description]]\\ ''service_flags'' — information about the tags assigned to the flow in DPI. Detected tethering is reported via IPFIX in bit 1 of the service_flags field. 63 bits are available for further use.\\ ''detection_flags'' — reserved for detection methods.\\ ''action_flags'' — reserved for transmitting actions applied to the flow. |
| | - [IPFIX] Fixed TTL transmission in Full NetFlow IPFIX in a single field with identifier 192 depending on direction. [[en:dpi:dpi_options:opt_statistics:statistics_ipfix#шаблон_экспорта_в_формате_ipfix_netflow_v10_для_протокола_ipv4|Description]] |
| | |
| | ===Utilities=== |
| | - [utils] Added the name2custom utility to view the list of protocols loaded from the cloud (as opposed to built-in ones) |
| | |
| | ===RADIUS=== |
| | - [FastRADIUS] Added support for logging to syslog. New parameter ''syslog_level'' in fdpi_radius.conf — the level of logging messages from the alert log to syslog. ''0'' — syslog logging disabled (default). |
| | - [FastRADIUS] Added extraction of the 3GPP User Location Info RADIUS attribute and its export to IPFIX |
| |
