Using DPI as pre-filter for SORM [Документация VAS Experts]

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:dpi_prefilter [2015/04/06 15:43] translator1en:dpi_prefilter [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
Line 1: Line 1:
-==== Using DPI as pre-filter for СОРМ ==== 
- 
-The additional СОРМ licenses purchase is needed eventually to serve increasing number of subscribers and increase of speed in billing plans.\\ 
-SKAT allows reduction of traffic that is mirrored to СОРМ. This is achieved by filtering of components that СОРМ does not analyse. For example: p2p (torrent), video traffic and so on. The expected traffic reduction is from 40% to 70%, depending on the traffic's structure and filtering list.\\ 
- 
-Pre-filter license purchase peculiarities:\\ 
-  * The BASE license is sufficient to filter the traffic. 
-  * In case of using SKAT to filter the traffic between 10 Gb/s and 20 Gb/s (the traffic is received by 2 SPAN ports with subsequent merge and transfer to the third port for СОРМ) you need the license SKAT-40 BASE. However it is charged as SKAT-20 BASE license. The usage of SKAT-40 Base license is limited to the filter in this case. 
- 
-The usage diagram:\\ 
-{{sorm_schema1_en.png?700|}} 
- 
-Configuration example to filter the torrent traffic. The traffic is between 10 Gb/s and 20 Gb/s: 
- 
-First we create the file protocols.dscp: 
-<code> 
-echo "bittorrent drop" > protocols.txt 
-cat protocols.txt|lst2dscp /etc/dpi/protocols.dscp 
-</code> 
- 
-Change configuration in the file /etc/dpi/fastdpi.conf: 
-<code> 
-  in_dev=dna0:dna1 
-  out_dev=dna2:dna2 
-  only_tcp=0 
-  mem_preset=1 
-</code> 
- 
-Check filtering results: 
- 
-Execute 
-<code>tail -200 /var/log/dpi/fastdpi_stat.log</code> 
- 
-In statistics lines 
-<code> 
-  IF dna1 : 
-  ... 
-     Drop: [8054507798 bytes][68.92 %] 
-           [9406449 pkts ][67.16 %] 
-  ... 
-</code>   
-we find the percentage and volume of filtered traffic.