Ingress filter: Difference between revisions

m
no edit summary
mNo edit summary
Line 6: Line 6:
|}
|}


The filter page allows setting a processing filter for live traffic. The traffic may be filtered before it is processed.
The ingress (NIC) filter page, allows setting allow/deny filters for live traffic preprocessing. Filtered out/denied traffic, will NOT become available throughout the dashboard nor the packet ring buffer. Filtered out/denied traffic will be irretrievable for (post) analysis.
Filters can be applied for:
 
This ingress (NIC) filter is applied on live traffic only. When replaying the ring buffer, loading a pcap or using the remote traffic capture feature, filtering is not used.
 
'''Filters can be applied for:'''
* IP addresses (with possible subnet mask).
* IP addresses (with possible subnet mask).
* pairs of IP addresses (with possible subnet mask).
* pairs of IP addresses (with possible subnet mask).
Line 20: Line 23:
The more restrictive filter will be applied.  
The more restrictive filter will be applied.  
For instance if no IP address is denied but a specific MAC address is on the denylist, no traffic for that MAC address will be processed.
For instance if no IP address is denied but a specific MAC address is on the denylist, no traffic for that MAC address will be processed.
The processing filter is applied on live traffic only. When replaying a pcap or using the remote traffic capture feature, filtering is not used.
 
This ingress (NIC) filter is applied on live traffic only. When replaying the ring buffer, loading a pcap or using the remote traffic capture feature, filtering is not used.


=== IP filters ===
=== IP filters ===
325

edits