<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/migration-scripts/interfaces/22-to-23, branch equuleus</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=equuleus</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=equuleus'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2024-01-12T20:53:17+00:00</updated>
<entry>
<title>wireguard: T5924: harden migration script logic 22-to-23</title>
<updated>2024-01-12T20:53:17+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-01-12T20:53:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=516c2c43392907493f4157ea7d6d2149b725688b'/>
<id>urn:sha1:516c2c43392907493f4157ea7d6d2149b725688b</id>
<content type='text'>
The original commit 2c1c36135 ("wireguard: T5413: Blocked adding the peer with
the router's public key") did not honor the fact that there might be no
private-key CLI node defined for a WireGuard interface. If this is the case,
private-key defaults to "default". This fact needs to be handled in the
migration script.
</content>
</entry>
<entry>
<title>wireguard: T5413: Blocked adding the peer with the router's public key</title>
<updated>2023-11-24T14:57:10+00:00</updated>
<author>
<name>aapostoliuk</name>
<email>a.apostoliuk@vyos.io</email>
</author>
<published>2023-11-24T14:21:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=2c1c3613567e23e14ce89bbf872e6e9dee16badb'/>
<id>urn:sha1:2c1c3613567e23e14ce89bbf872e6e9dee16badb</id>
<content type='text'>
Disabled adding the peer with the same public key as the router has.
Backport from current
https://github.com/vyos/vyos-1x/pull/2122
</content>
</entry>
</feed>
