Differences

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

--- en:dpi:dpi_components:platform:dpi_admin:testversion_install:start [2024/02/21 07:41] – [Changes in version 13.0 BETA5] elena.krasnobryzh
+++ en:dpi:dpi_components:platform:dpi_admin:testversion_install:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Test version installation ======
-{{indexmenu_n>3}}
-====Changes in version 13.0 BETA1====
-  - [LAG] LACP support. [[en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick:start|Description]]
-  - Only the basic devices for On-Stick must be specified in the LAG description. Mixing On-Stick and conventional devices in one LAG is not allowed. [[en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick:start|Description]]
-  - [LAG] Apply balancing to outgoing traffic LAG. [[en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick:start|Description]]\\ The type of balancing algorithm to be applied is specified by the ''lag.balance_algo'' parameter. Valid values:
-    * ''0'' — balancing by internal ''session_id'' (this is the default balancing). The ''session_id'' is taken as a hash
-    * ''1'' — without balancing - the packet will be sent to the paired bridge port
-    * ''2'' — hash from ''flow key <srcIP, dstIP, srcPort, dstPort, proto>''. If there is no flow, we balance by ''session_id''.\\ \\ Additional hash configuration parameters in the ''lag'' section: ''hash_seed'', ''hash_offset'', ''hash_bits''\\ How many significant bits we take from a 64-bit hash during balancing. The balancing algorithm in the general case looks like this:
-    * calculate a 64-bit hash of some fields of the packet and ''hash_seed'';
-    * we take ''hash_bits'' bits from the 64-bit hash starting from ''hash_offset'' bit;
-    * use the resulting number N to determine the port number in the LAG: ''port := N mod LAG_active_port_count'', i.e.<code bash>port := ((hash(packet, hash_seed) >> hash_offset) & (2^hash_bits - 1)) mod LAG_active_port_count</code>Example:<code bash>
-//       +------------------------------------------------+
-// hash: |                                XXXXXXXXXX------|
-//       +------------------------------------------------+
-//                                        ^         ^
-//                                        |         hash_offset = 6
-//                                        hash_bits = 10
-hash_seed=0
-hash_offset=0
-hash_bits=64</code>
-  - [LAG] Added traffic balancing tracing. [[en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick:start|Description]]
-  - [DPDK] Transition to DPDK 23.11
-  - Modified: for QUIC and QUIC_IETF: if no SNI is detected, check by AS
-  - Modified: when analyzing STUN check AS from Facebook — define VASE_DPI_PROTO_FACEBOOK_VIDEO, not WHATSAPP_VOICE
-  - [DPDK][rss-engine] Setting RSS hash flags for UDP and TCP
-  - Modified: openvpn protocol definition
-  - [BRAS][DHCP] Added: accounting of DHCP packets from subscriber in billing statistics: subscriber CPE (i.e. Wi-Fi router) without clients (e.g. at night) — sends only license renewal requests. Since these requests were intercepted by BRAS and were not included in the accounting, the session was terminated by idle timeout
-  - [BRAS][DHCP] Corrected: actions when QinQ/VLAN is changed for a subscriber
-  - [DHCP] Fixed: ''framed-pool renew''\\ In some cases incorrect DHCP responses were generated. Added tracing to DHCP packets log for ''framed-pool renew''.
-  - [DHCPv6] Fixed: receiving packets from the relay. Previously it was checked that the relay was on the fc::/7 network. Now this check is unnecessary and has been removed - the relay can have any address.
-  - [PPPoE] Fixed: DHCPv6 options parsing from Radius
-  - Fixed: SIGHUP processing only if fastDPI is fully initialized. A crash is possible if a SIGHUP is received during the fastDPI startup process
-  - [AJB][PCAP] Trace/debug packet recording moved to new API
-  - Added: wechat protocol support for UDP
-====Changes in version 13.0 BETA2====
-  - [DPI] Support for additional markup of autonomous systems ''mark1'', ''mark2'', ''mark3''. [[en:dpi:dpi_options:opt_priority:priority_config_as:start|Description]]<code bash>
-vi test.txt
-mark1
-cat test.txt|as2dscp /etc/dpi/asnum.dscp
-</code>
-  - [DPI] Prioritize SNI detection in custom signatures for autonomous systems marked as ''mark1''. [[en:dpi:dpi_options:opt_priority:priority_config_as:start|Description]]
-  - [DPI] Prioritize more specific custom SNI signatures. Example: for host ''a.b.c.d'', if the signatures ''*.d'', ''*.c.d'' and ''*.b.c.d'' are present, the protocol defined by the signature ''*.b.c.d'' :!: works only for signatures with ''*''. [[en:dpi:dpi_components:dpiui:user_guide:vas_cloud_services:custom_protocols:start#protocols|Description]]
-  - [DPI] Support for hard locks (despite hostname/SNI) - set in an additional field in the address blacklist, example: ''1.1.1.1.1 443 hard''.
-  - Improved detection of YOUTUBE, SIGNAL
-  - Added the DPITUNNEL protocol, which includes traffic anomalies commonly used for DPI traversal
-  - Updating dpiutils
-====Changes in version 13.0 BETA3====
-  - [DPI] New protocols VK_CDN_VIDEO, META_CHAT
-  - [DPI] FACEBOOK_VIDEO, META_CALLS protocol signatures improvement
-  - Updating dpiutils
-====Changes in version 13.0 BETA4====
-  - [DPI] Fixed protocol name VK_CDN_VIDEO
-  - [DPI] Fixed: SNI decoding in QUIC IETF and possibility of crusting in exceptional cases
-  - [DPI] Fixed: clearing search structures when deleting CUSTOM protocols
-  - [utils] Added ability to add comments (#) and blank lines in input files for lst2dscp, lst2tbf utilities
-====Changes in version 13.0 BETA5====
-  - [DPI] Added protocols QUIC_UNKNOWN - QUIC without SNI and QUIC_UNKNOWN_MARKED - QUIC without SNI and AS labeled MARK2. [[en:dpi:dpi_options:opt_priority:priority_config_as:start|Description]]
-  - [DPI] Fixed: stun characterization for TCP
-  - [DPI] Modified: if the stun packet viewing limit is reached - set this protocol with AS in mind
-  - [DPIutils] Updated utilities to support new protocols
-  - [Router] Mempool allocation for emit packets: we do not allow full exhaustion of the pool, there should be at least 256 free elements in the pool
-  - [Router] The error of route deletion ''errno=3'' (No record found) has been moved to TRACE to avoid clogging the log
-  - Added L2 traffic balancer mode. This enhancement allows to use SCAT as a traffic balancer based on IP addresses owned by AS and defined as ''local'' in ''asnum.dscp''. DPI functionality does not work in this mode. The ''maglev'' algorithm with fixed hash table size is used for traffic balancing: the output interface definition according to the following algorithm:\\ 1 — if src and dst ip are both local, hash is calculated based on these two addresses;\\ 2 — If only src ip local, then hash is calculated based on src ip;\\ 3 — If only dst ip local, hash is calculated based on dst ip;\\ 4 — hash is calculated based on src and dst ip.\\ Based on the calculated hash value, the output interface is determined by determining the index of the hash table cell containing the interface index from the array of output interfaces. The value from the array of output interfaces is substituted into the current context and ''pcs_accept'' is returned.\\ \\ The following settings are required for correct operation:
-    * Definition of an autonomous system with IP addresses that are used by subscribers. [[en:dpi:dpi_options:opt_statistics:statistics_asn:start|Description]]
-    * Marking a given autonomous system as local. [[en:dpi:dpi_options:opt_priority:priority_config_as:start|Description]]
-    * Define input and output interfaces in the configuration file. Input interfaces are defined in the in_dev parameter, and output interfaces in out_dev. Interfaces do not form pairs and constructions of the following kind are allowed:<code bash>in_dev=05-00.0:05-00.1:05-00.2:05-00.3:0b-00.0:0b-00.1:0b-00.2:0b-00.3
-out_dev=08-00.0:08-00.1:08-00.2:08-00.3</code> Or <code bash>in_dev=05-00.0
-out_dev=out_dev=08-00.0:08-00.1:08-00.2:08-00.3</code>
-    * Enable SORM balancing mode: ''enable_l2_lb=true''\\ \\ Input parameters:\\ ''enable_l2_lb=false|true'' - enable traffic balancer for SORM\\ ''lb_hash_out_dev_type = 0|1'' - by which value to initialize hash table:\\ 0 — use the internal index of the output interface\\ 1 — use the interface name from [in|out]_dev\\ \\ The following types can be used as ''dpdk_engine'': 0 (default), 1, and 2.
-====Changes in version 13.0 BETA6====
-  - [DPI] Improvements in QUIC_UNKNOWN, QUIC_UNKNOWN_MARKED, SIGNAL, DpiTunnel protocols
-  - [DPI] SNI/HOST embedded protocol definitions are cloud-based, SNI/IP prioritization is supported
-  - [Router] Fixed the order of router components termination
-  - [LAG] Increase max number of ports in LAG
-  - [SDS] The ''storage_tag'' value is set based on directional priority or protocol priority
-  - [CLI] The ''subs prop show active'' command has been added. The command outputs a dump of L2 properties of all active (non-expired) subscribers.
-  - [CLI] Fixed: Prohibit calling CLI commands while stopped
-  - [Router] Fixed: system error when clearing route tables. Cleaning of route tables (deleting all entries added by SCAT) is done at stop and start of fastDPI. During cleaning process EBUSY error may occur, which is fatal for netlink socket, socket should be closed.
-====Changes in version 13.0 BETA7====
-  - [DPI] Changed: SNI comparison is case-insensitive
-====Update instructions====
-You can check the current installed version with the command below
-<code bash>
-yum info fastdpi
-</code>
-If you have CentOS 6.x or CentOS 8.x installed, then switch the repository once with the command:
-<code bash>
-sed -i -e '/^mirrorlist=http:\/\//d' -e 's/^# *baseurl=http:\/\/mirror.centos.org/baseurl=http:\/\/vault .centos.org/' /etc/yum.repos.d/CentOS-*.repo
-</code>
-and then update as usual.
-To install the test version, you should issue the following command:
-<code bash>
-yum --enablerepo vasexperts-beta update fastdpi
-</code>
-Downgrade to 12.3:
-<code bash>
-yum downgrade fastdpi-12.3 fastpcrf-12.3
-</code>
-<note important>After an update or version change, a restart of the service is required.</note>

Profile

Settings

Differences