-
-
Notifications
You must be signed in to change notification settings - Fork 568
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
Feature request: separate incoming/outgoing whitelist #444
Comments
Hello! If you are interested in netflow or sflow you could wrote own hook script https://github.com/pavel-odintsov/fastnetmon/blob/master/src/netflow_hooks.lua or https://github.com/pavel-odintsov/fastnetmon/blob/master/src/sflow_hooks.lua and filter out some packets according to source or destination IP or direction. |
I would also be interested in this as I have some servers on a ddos protected network but sometimes an attack can leak for a few seconds but I would want to avoid them being nullrouted as usually the large network port copes fine so would only want outbound to be filtered to stop any outbound abuse. |
Do you need it for port mirror? |
I would just be using sflow so whatever that is, I don't think port mirroring? |
Yes. So you could use mentioned earlier approach and parse data with LUA :) |
Never used LUA, actually. is there an example available in the repo? |
I have shared two links above :) |
Ah, those are examples, and not the hook interface. Sorry, naming got me. |
Yes it's example script for lua ;) |
add an optional "ignore_(incoming|outgoing)" flag to each CIDR block in the /etc/networks_whitelist
this would allow high-speed one-way clients to still have protection in the opposite direction.
The text was updated successfully, but these errors were encountered: