Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Packetbeat] Add support for ignoring interfaces #40566

Open
gaby opened this issue Aug 20, 2024 · 1 comment
Open

[Packetbeat] Add support for ignoring interfaces #40566

gaby opened this issue Aug 20, 2024 · 1 comment
Labels
enhancement Team:Security-Linux Platform Linux Platform Team in Security Solution

Comments

@gaby
Copy link

gaby commented Aug 20, 2024

Describe the enhancement:
Currently when setting the packetbeat sniffer the interface field is either an interface name or any for all interfaces. If you have N number of interfaces your only option is to use any.

  • Add support for filtering interfaces you don't want to sniff on.

Describe a specific use case for the enhancement or feature:

The enhancement would be to add support for specifying a list of interfaces that should be ignore by the sniffer. This would allow packetbeat to focus on interfaces the user cares about.

packetbeat.interfaces.ignore: [lo, eth0, veth, docker0]

Current solution

Currently the only way to accomplish this is by adding processors and drop_events, at this point the packetbeat process has sniffed those packets only to be dropped this takes cycles from actual interfaces the user cares about.

The docs say the events have the interface.name field, but I don't have that ECS for some reason. Not sure if it's related to my output being logstash instead of elasticsearch.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 20, 2024
@ycombinator ycombinator added the Team:Security-Linux Platform Linux Platform Team in Security Solution label Sep 4, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Team:Security-Linux Platform Linux Platform Team in Security Solution
Projects
None yet
Development

No branches or pull requests

3 participants