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

Network Monitor #146

Closed
wants to merge 2 commits into from
Closed

Network Monitor #146

wants to merge 2 commits into from

Conversation

mbertrone
Copy link
Contributor

This PR adds a transparent service called Network Monitor.
The purpose of this module is collecting info over a link, that can be used by a remote backend server to detect attacks and anomalies.

Note: right now the implementation is not fully completed; the module is returning pseudo-random metrics.

add datamodel draft
add stub for service

datamodel:
use uint64 everywhere, since float are not supported by yang
and decimal64 are not supported by our codegen toolchain

Signed-off-by: Matteo Bertrone <m.bertrone@gmail.com>
to return pseudo random numebers

Signed-off-by: Matteo Bertrone <m.bertrone@gmail.com>
@mbertrone mbertrone requested a review from a team as a code owner June 7, 2019 15:27
Copy link
Contributor

@frisso frisso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@acloudiator
Copy link
Contributor

@mbertrone This seems to be a nice feature. Will it be applied to the framework; like all the polycube services benefit from this or only specific services? Thanks!

@frisso I recommend keeping this on hold before we merge to master, as this isn't a fully functional feature. Do you share the same thought?

@frisso
Copy link
Contributor

frisso commented Jun 7, 2019

@acloudiator

  1. This is a generic service, so in principle you could plug it in any place (any netdev, and any connection between services). However, this particular service will be specialized in SYN flooding attacks, so in practice its effectiveness is limited only to that scope.
  2. To facilitate the work of other partners in the ASTRID EU project, it would be nice if we can integrate it in the master. It should be a matter of weeks to have it 100% ready, dataplane included.

@acloudiator
Copy link
Contributor

  1. To facilitate the work of other partners in the ASTRID EU project, it would be nice if we can integrate it in the master. It should be a matter of weeks to have it 100% ready, dataplane included.

IMHO, We may first have it working in separate branch.
Then we may validate/pass some tests before we merge into master.

Please do let me know If you still think otherwise. Thanks!

Copy link
Contributor

@acloudiator acloudiator left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mbertrone can you please point to any test case or result to validate this feature? I don't see it here in any document. Thanks!

@mbertrone
Copy link
Contributor Author

After @frisso suggestion to rename the service synflood detector, and in order to avoid misunderstanding on service purpose, I'm going to close this PR.
Please refer to #152

@mbertrone mbertrone closed this Jun 11, 2019
@mbertrone mbertrone deleted the network_monitor branch June 20, 2019 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants