====== Work within the GRE/PPTP/L2TP/IPIP tunnels ======
+
====== Operation in PPPoE/PPTP/L2TP/IPIP/GRE (including ERSPAN) tunnels ======
{{indexmenu_n>5}}
{{indexmenu_n>5}}
+
<note important>By default, DPI does not parse tunnels (tagged VLAN/QINQ and MPLS traffic are not considered tunnels), since tunnels may carry traffic from different operators or customers with conflicting IP sets. However, in non-standard deployments (before BRAS), tunnel parsing is required.</note>
-
<note important>DPI doesn't parse the tunnels ((tagged VLAN/QINQ and MPLS traffic are not considered as tunnel)) by default, since the traffic of different operators or clients with a conflicting IPs can be transmitted, but for non-standard connection (before BRAS), tunneling parsing is necessary.</note>
+
In the Lawful Interception prefilter, tunnel parsing is enabled automatically when the ''tap_dev'' parameter is present.\\
+
In other cases, tunnel parsing must be explicitly enabled using a configuration parameter in the file ''/etc/dpi/fastdpi.conf'':
-
In the Lawful Interception prefilter, tunnel parsing is enabled automatically by the presence of the tap_dev parameter. In other cases, you will need to explicitly enable parsing with the configuration parameter in the **/etc/dpi/fastdpi.conf** file
+
<code bash>
+
check_tunnels=1
+
</code>
-
<code>check_tunnels=1</code>
+
This parameter enables parsing of PPPoE/PPTP/L2TP/IPIP/GRE (including ERSPAN) tunnels.
