-
Version2.4.201 Installation MethodSecurity Onion ISO image Descriptionconfiguration Installation TypeDistributed Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU4 RAM128 Storage for /500G Storage for /nsm15T Network Traffic Collectionspan port Network Traffic Speeds1Gbps to 10Gbps StatusYes, all services on all nodes are running OK Salt StatusNo, there are no failures LogsNo, there are no additional clues DetailHi, The plan: Since I'm only interested in getting/analyzing Traffic in a particular VLAN on S.O. I set up BPF filters in SO identically for
as Unfortunately that didn't work: I'm still getting Suricata and Zeek alerts from S.O. about traffic in other VLANs. Shouldn't the BPF for Suricata and Zeek respectively make sure that only Traffic tagged with VLAN 555 makes its way to Suricata/Zeek? Only for PCAP the filter seems to work: so when starting from a Suricata Alert I opt for "PCAP" I only get packet data for alerts for VLAN 555 wheres for any suricata alerts from other VLANs there are not packets. Any clue as wo what might be wrong here, i.e. why a BPF "vlan xxx" doesn't work for Suricata/Zeek? PS: Please note that filtering out traffic on the SPAN-source-interface (i.e. where the firewall connects to is not an option since that source traffic is also mirrored to another interface aside from the one the S.O. sensor connects to). Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Just so I am clear, the BPF filter is simply |
Beta Was this translation helpful? Give feedback.
https://docs.securityonion.net/en/2.4/bpf.html#vlan You have to have a filter on both sides of the vlan tag.