325
edits
Ingress filter: Difference between revisions
→ingress (NIC) filter
Remco.derooy (talk | contribs) m (→IP filters) |
Remco.derooy (talk | contribs) |
||
| Line 1: | Line 1: | ||
=== | === Ingress (NIC) filter === | ||
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. | 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: | Filters can be applied for: | ||
| Line 20: | Line 18: | ||
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. | ||
NOTE: The ingress (NIC) filter is applied to live traffic only, e.i. the traffic sent to the monitoring interfaces of an Allegro. When replaying data from the ring buffer, loading a pcap or using the remote traffic capture feature, filtering is not used and/or applied. | |||
NOTE: The data recorded to/stored in the Packet Ring buffer, is of course also affected by the Ingress filter. Additional ring buffer capture rules may be configured under "Generic - Packet Ring Buffer", further explained in our wiki here [[Packet ring buffer#Packet%20ring%20buffer%20snapshot%20length%20filter|https://allegro-packets.com/wiki/Packet_ring_buffer#Packet_ring_buffer_snapshot_length_filter]] | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||