-
Notifications
You must be signed in to change notification settings - Fork 30
NETOBSERV-2198: IPsec support #1085
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -657,6 +657,20 @@ columns: | |
default: false | ||
width: 15 | ||
feature: packetTranslation | ||
- id: IPSec | ||
name: Is IPSec operation successful? | ||
field: IPSecSuccess | ||
filter: ipsec_success | ||
default: true | ||
width: 10 | ||
feature: ipsec | ||
- id: IPSecCode | ||
name: IPSec Return Code | ||
field: IPSecRetCode | ||
filter: ipsec_retcode | ||
default: true | ||
width: 10 | ||
feature: ipsec | ||
filters: | ||
- id: cluster_name | ||
name: Cluster | ||
|
@@ -1057,6 +1071,12 @@ filters: | |
component: autocomplete | ||
category: destination | ||
hint: Specify a single port number or name. | ||
- id: ipsec_success | ||
name: IPSec processing succeeded ? | ||
component: number | ||
- id: ipsec_retcode | ||
name: IPSec processing return code | ||
component: number | ||
scopes: | ||
- id: cluster | ||
name: Cluster | ||
|
@@ -1415,6 +1435,12 @@ fields: | |
- name: K8S_ClusterName | ||
type: string | ||
description: Cluster name or identifier | ||
- name: IPSecRetCode | ||
type: number | ||
description: IPSec operation return code | ||
- name: IPSecSuccess | ||
type: boolean | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you think we will be able to get more info that that in the future ? It would be interesting to use another type here if so There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. in fact, I think we could simplify that from the user perspective, with just a single field "IPsec" that could be "true" / "false" / "error: (code)", wdyt? |
||
description: IPSec processing succeeded | ||
- name: _RecordType | ||
type: string | ||
description: "Type of record: `flowLog` for regular flow logs, or `newConnection`, `heartbeat`, `endConnection` for conversation tracking" | ||
|
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.
What about just "IPsec encryption" ?
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.
u mean use the above for name ? I used operation as it can work for both encryption or decryption