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

Provide ability to filter activity IPv4/v6 mask(s) [CORE5816] #6078

Open
firebird-automations opened this issue May 5, 2018 · 1 comment

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pavel-zotov

It will be *extremely* useful (for real practice purpuces) to have ability catch via TRACE all kinds of actions that are done on one or many hosts if weknow their IP addresses.
This can be implemented just as already existing filters, i.e. by adding parameters like "include_ip_filter" and "exclude_ip_filter".

For example, if one need to log activity for all machines that are included in sub-networks with IP masks:
1) 172.16.*, 172.15.*,
2) 192.168.21.* and
3) 192.168.22.*.
- we can use following pattern:

include_ip_filter = '(172.((16)|(15)).%)|(192.168.((21)|(22)).%)'

2 hvlad: PLEASE, consider to add this ability in FB 3.x. This is need that really often occurs in practice.

@firebird-automations
Copy link
Collaborator Author

Commented by: @mkubecek

From networking point of view, string pattern matching is not natural for IP addresses. IP addresses are numbers, 32- or 128-bit, and are organized in hierarchical way. I would therefore rather suggest to use a list of network ranges, e.g. "172.16.0.0/15,192.168.22/23".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant