-
Notifications
You must be signed in to change notification settings - Fork 26
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
add example workload (with syn attack) #111
Conversation
is that something where you can leverage netobserv to spot the attack? |
2778515
to
415435b
Compare
Maybe this syn attack traffic is not "seen" by OVS/N ... I need to check more We can see in the namespace level a lot of traffic into the And then focus on the This is exactly what we expect to see in such a scenario. |
/retest |
@jpinsonneau I see strange amount of packets (on the edges) when I change the view to show the number of packets:: I was expecting a very small amount. And BTW; I see the same in the table ... so something is not making sense here: |
@eranra default payload length is 1400, it's consistent with the values that you have: (or you were expecting less packets, but why? isn't it the purpose to send as many packets as possible?) |
I was expecting fewer packets (only one per flow with syn) ... it should be 1400 bytes total if I read the documentation correctly (and the code of the payload creation here https://github.com/bilalcaliskan/syn-flood/blob/ec6298dd2ffe52ea0f5d7eb62adc9ada5ac8d856/internal/raw/utils.go#L13 ))) We get a lot of packets per connection ... not what I expected |
maybe with sampling = 1? |
@@ -8,6 +8,9 @@ ocp-expose: | |||
oc expose service loki || true | |||
@loki_url=$$(oc get route loki -o jsonpath='{.spec.host}'); \ | |||
echo -e "\nAccess loki on OCP using: http://"$$loki_url"\n" | |||
oc expose -n sample-workload service frontend-external || true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to use make ocp-expose
just to create grafana/loki routes. Can you split in two different targets then? (maybe ocp-expose
and ocp-expose-all
, similarly to the deploy-all
that deploys more than just the infra ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed (@jotak please review again that this fits your needs )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jotak The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The workload is based on GoogleCloudPlatform/microservices-demo
Syn attack is based on docker and an example from https://github.com/bilalcaliskan/syn-flood