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: T5413: Blocked adding the peer with the router's public key #2540

Merged
merged 1 commit into from
Dec 9, 2023

Conversation

aapostoliuk
Copy link
Contributor

@aapostoliuk aapostoliuk commented Nov 24, 2023

Change Summary

Disabled adding the peer with the same public key as the router has.
Backported from the current version.
#2122

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes)
  • Migration from an old Vyatta component to vyos-1x, please link to related PR inside obsoleted component
  • Other (please describe):

Related Task(s)

Related PR(s)

vyos/vyatta-cfg-system#216

Component(s) name

wireguard

Proposed changes

Disabled adding the peer with the same public key as the router has.
Backported from the current version.
#2122

How to test

Smoketest result

vyos@vyos:~$ /usr/libexec/vyos/tests/smoke/cli/test_interfaces_wireguard.py
test_wireguard_add_remove_peer (main.WireGuardInterfaceTest) ... ok
test_wireguard_peer (main.WireGuardInterfaceTest) ... ok
test_wireguard_same_public_key (main.WireGuardInterfaceTest) ...
Peer "PEER01" has the same public key as the interface "wg0"

ok


Ran 3 tests in 14.169s

OK

Checklist:

  • I have read the CONTRIBUTING document
  • I have linked this PR to one or more Phabricator Task(s)
  • I have run the components SMOKETESTS if applicable
  • My commit headlines contain a valid Task id
  • My change requires a change to the documentation
  • I have updated the documentation accordingly

Disabled adding the peer with the same public key as the router has.
Backport from current
vyos#2122
@vyosbot vyosbot requested review from a team, dmbaturin, sarthurdev, zdc, jestabro, sever-sever and c-po and removed request for a team November 24, 2023 15:02
aapostoliuk added a commit to aapostoliuk/vyatta-cfg-system that referenced this pull request Nov 24, 2023
@c-po c-po added the equuleus VyOS 1.3 LTS label Nov 28, 2023
@sever-sever
Copy link
Member

Let's merge it after 1.3.5 release

@dmbaturin dmbaturin merged commit 48e512f into vyos:equuleus Dec 9, 2023
3 checks passed
@c-po
Copy link
Member

c-po commented Dec 9, 2023

Please note - after this merged we need to properly shift all migrators in 1.4 that have a higher number then 22 as there is now a 22-to-23 in an "older" LTS release. This is required so the config is still properly migrated from 1.3.6 -> 1.4.0

c-po added a commit to c-po/vyos-1x that referenced this pull request Dec 10, 2023
PR vyos#2540 backported a migration script from
current to the equuleus LTS branch. As migration scripts are executed in order
to adjust the CLI for necessary improvements in future LTS releases we need to
change the versioning of the migration files to match the new "base" version
from the previous LTS release.

In theory this could break very ancient 1.4 rolling releases (from the early
days of the OSPF refactoring) - but those versions are considered very much
unstable.

Now this is the last chance to sync up the migration scripts before the 1.4 LTS
release.
mergify bot pushed a commit that referenced this pull request Dec 10, 2023
PR #2540 backported a migration script from
current to the equuleus LTS branch. As migration scripts are executed in order
to adjust the CLI for necessary improvements in future LTS releases we need to
change the versioning of the migration files to match the new "base" version
from the previous LTS release.

In theory this could break very ancient 1.4 rolling releases (from the early
days of the OSPF refactoring) - but those versions are considered very much
unstable.

Now this is the last chance to sync up the migration scripts before the 1.4 LTS
release.

(cherry picked from commit 98ca098)
jestabro pushed a commit to jestabro/vyos-1x that referenced this pull request Dec 11, 2023
PR vyos#2540 backported a migration script from
current to the equuleus LTS branch. As migration scripts are executed in order
to adjust the CLI for necessary improvements in future LTS releases we need to
change the versioning of the migration files to match the new "base" version
from the previous LTS release.

In theory this could break very ancient 1.4 rolling releases (from the early
days of the OSPF refactoring) - but those versions are considered very much
unstable.

Now this is the last chance to sync up the migration scripts before the 1.4 LTS
release.
jestabro pushed a commit to jestabro/vyos-1x that referenced this pull request Dec 11, 2023
PR vyos#2540 backported a migration script from
current to the equuleus LTS branch. As migration scripts are executed in order
to adjust the CLI for necessary improvements in future LTS releases we need to
change the versioning of the migration files to match the new "base" version
from the previous LTS release.

In theory this could break very ancient 1.4 rolling releases (from the early
days of the OSPF refactoring) - but those versions are considered very much
unstable.

Now this is the last chance to sync up the migration scripts before the 1.4 LTS
release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
equuleus VyOS 1.3 LTS
Development

Successfully merging this pull request may close these issues.

4 participants