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

[wireguard]: Use metadata instead of generated sync.Map #528

Merged

Conversation

glazychev-art
Copy link
Contributor

Closes: #526

This is needed if we want to reuse an already created interface, but the mechanism is empty (for the healing cases)

Signed-off-by: Artem Glazychev artem.glazychev@xored.com

This is needed if we want to reuse already created interface,
but mechanism is empty (for example, on the Server side if wireguard.Client was restarted)

Signed-off-by: Artem Glazychev <artem.glazychev@xored.com>
@denis-tingaikin denis-tingaikin merged commit ebfdd63 into networkservicemesh:main Mar 17, 2022
nsmbot pushed a commit to networkservicemesh/cmd-nse-icmp-responder-vpp that referenced this pull request Mar 17, 2022
…k-vpp@main

PR link: networkservicemesh/sdk-vpp#528

Commit: ebfdd63
Author: Artem Glazychev
Date: 2022-03-18 06:17:52 +0700
Message:
  - Use metadata instead of generated sync.Map (#528)
This is needed if we want to reuse already created interface,
but mechanism is empty (for example, on the Server side if wireguard.Client was restarted)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/cmd-forwarder-vpp that referenced this pull request Mar 17, 2022
…k-vpp@main

PR link: networkservicemesh/sdk-vpp#528

Commit: ebfdd63
Author: Artem Glazychev
Date: 2022-03-18 06:17:52 +0700
Message:
  - Use metadata instead of generated sync.Map (#528)
This is needed if we want to reuse already created interface,
but mechanism is empty (for example, on the Server side if wireguard.Client was restarted)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/cmd-nse-firewall-vpp that referenced this pull request Mar 17, 2022
…k-vpp@main

PR link: networkservicemesh/sdk-vpp#528

Commit: ebfdd63
Author: Artem Glazychev
Date: 2022-03-18 06:17:52 +0700
Message:
  - Use metadata instead of generated sync.Map (#528)
This is needed if we want to reuse already created interface,
but mechanism is empty (for example, on the Server side if wireguard.Client was restarted)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/cmd-nsc-vpp that referenced this pull request Mar 17, 2022
…k-vpp@main

PR link: networkservicemesh/sdk-vpp#528

Commit: ebfdd63
Author: Artem Glazychev
Date: 2022-03-18 06:17:52 +0700
Message:
  - Use metadata instead of generated sync.Map (#528)
This is needed if we want to reuse already created interface,
but mechanism is empty (for example, on the Server side if wireguard.Client was restarted)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/cmd-nse-vlan-vpp that referenced this pull request Mar 17, 2022
…k-vpp@main

PR link: networkservicemesh/sdk-vpp#528

Commit: ebfdd63
Author: Artem Glazychev
Date: 2022-03-18 06:17:52 +0700
Message:
  - Use metadata instead of generated sync.Map (#528)
This is needed if we want to reuse already created interface,
but mechanism is empty (for example, on the Server side if wireguard.Client was restarted)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wireguard doesn't reuse an existing interface when possible
4 participants