-
-
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
Implement support for IPv6 flow-based DDoS detection #938
Comments
Hello! Thank you for sharing your feedback. Our code relies on fact that 5 tuple can be encoded into 64 bit integer fastnetmon/src/fastnetmon_types.hpp Line 304 in 3a21ef0
I see new logic as completely different approach which stores all flows in tracking table and then does not flush it every period but just counts number of new flows for last period. |
Hi @pavel-odintsov I was wondering if this bug is fixed on the latest (1.2.3) version of FastNetmon. Thank's in advance. |
Hello!
No, we had no progress with this feature in latest version.
|
Thank you for the quick reply. Any non-binding ETA for a possible delivery of this enhancement? |
Hello!
I'm sorry but we have no ETA about this task as it's pretty large change
from design perspective.
|
The current code-base of fastnetmon is not supporting IPv6 flow-tracking. Thus, when an attacker is hitting our network, we can see at the client the pps and mbps counters increasing but not the flow counters. Thus, the flow-based DDoS detection and mitigation is useless in IPv6. AFAIK, the same issue applies at the advanced/paid version.
Thus, I would like to submit an RFE to the team to have this feature implemented and I am open to share details/requirements if needed.
Kind Regards
Stavros
The text was updated successfully, but these errors were encountered: