<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/etc/systemd/system, branch 1.4.0-rc2</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=1.4.0-rc2</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=1.4.0-rc2'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2024-01-10T07:11:39+00:00</updated>
<entry>
<title>https: T5902: remove virtual-host configuration</title>
<updated>2024-01-10T07:11:39+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-01-06T09:55:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=34eadcf2f74ae57342997bed77ce64bddd34219b'/>
<id>urn:sha1:34eadcf2f74ae57342997bed77ce64bddd34219b</id>
<content type='text'>
We have not seen the adoption of the https virtual-host CLI option.

What it did?
* Create multiple webservers each listening on a different IP/port
  (but in the same VRF)
* All webservers shared one common document root
* All webservers shared the same SSL certificates
* All webservers could have had individual allow-client configurations
* API could be enabled for a particular virtual-host but was always enabled on
  the default host

This configuration tried to provide a full webserver via the CLI but VyOS is a
router and the Webserver is there for an API or to serve files for a local-ui.

Changes

Remove support for virtual-hosts as it's an incomplete and thus mostly useless
"thing". Migrate all allow-client statements to one top-level allow statement.

(cherry picked from commit d0d3071e99eb65edb888c26ef2fdc9e038438887)
</content>
</entry>
<entry>
<title>pki: T5886: add support for ACME protocol (LetsEncrypt)</title>
<updated>2024-01-08T20:11:13+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-01-05T21:27:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=f8f51939ae5ad852563cc69c4e2c8c2717318c9c'/>
<id>urn:sha1:f8f51939ae5ad852563cc69c4e2c8c2717318c9c</id>
<content type='text'>
The "idea" of this PR is to add new CLI nodes under the pki subsystem to
activate ACME for any given certificate.

vyos@vyos# set pki certificate NAME acme
Possible completions:
+  domain-name          Domain Name
   email                Email address to associate with certificate
   listen-address       Local IPv4 addresses to listen on
   rsa-key-size         Size of the RSA key (default: 2048)
   url                  Remote URL (default:
                        https://acme-v02.api.letsencrypt.org/directory)

Users choose if the CLI based custom certificates are used
  set pki certificate EXAMPLE acme certificate &lt;base64&gt;
or if it should be generated via ACME.

The ACME server URL defaults to LetsEncrypt but can be changed to their staging
API for testing to not get blacklisted.
  set pki certificate EXAMPLE acme url https://acme-staging-v02.api.letsencrypt.org/directory

Certificate retrieval has a certbot --dry-run stage in verify() to see if it
can be generated.

After successful generation, the certificate is stored in under
/config/auth/letsencrypt. Once a certificate is referenced in the CLI (e.g. set
interfaces ethernet eth0 eapol certificate EXAMPLE) we call
vyos.config.get_config_dict() which will (if with_pki=True is set) blend in the
base64 encoded certificate into the JSON data structure normally used when
using a certificate set by the CLI.

Using this "design" does not need any change to any other code referencing the
PKI system, as the base64 encoded certificate is already there.

certbot renewal will call the PKI python script to trigger dependency updates.

(cherry picked from commit b8db1a9d7baf91b70c1b735e58710f1e2bc9fc7a)

# Conflicts:
#	debian/control
</content>
</entry>
<entry>
<title>T5897: frr should be stopped before vyos-router</title>
<updated>2024-01-04T17:16:52+00:00</updated>
<author>
<name>Date Huang</name>
<email>tjjh89017@hotmail.com</email>
</author>
<published>2024-01-04T10:16:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d8a66a1022fa2f6b62ca6b09e16756a7440f749d'/>
<id>urn:sha1:d8a66a1022fa2f6b62ca6b09e16756a7440f749d</id>
<content type='text'>
Signed-off-by: Date Huang &lt;tjjh89017@hotmail.com&gt;
(cherry picked from commit 6d16ab081b70bc4ea837b66dfe032ec6bdb563d7)
</content>
</entry>
<entry>
<title>mdns: T5723: Always reload systemd daemon before applying changes</title>
<updated>2023-12-01T05:39:38+00:00</updated>
<author>
<name>Indrajit Raychaudhuri</name>
<email>irc@indrajit.com</email>
</author>
<published>2023-11-07T20:03:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=ccee236ee5f60969e07df5578dd1cb95f8573d82'/>
<id>urn:sha1:ccee236ee5f60969e07df5578dd1cb95f8573d82</id>
<content type='text'>
Additionally, templatize system service override and move it to the
runtime path.

(cherry picked from commit eb906739047187c322b6ce9efe7c9479bed9a024)
</content>
</entry>
<entry>
<title>T5480: Ability to disable SNMP for keepalived service VRRP</title>
<updated>2023-09-06T09:16:19+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2023-09-05T10:52:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=7a79dd77fa11fac4030e66057dde2d51f063b934'/>
<id>urn:sha1:7a79dd77fa11fac4030e66057dde2d51f063b934</id>
<content type='text'>
By default we enable `--snmp` for keepalived unit service
Add ability to disable it

set high-availability vrrp disable-snmp

(cherry picked from commit 5ae730a52de2f284e45cd433bb0cf66c8508f2f7)
</content>
</entry>
<entry>
<title>T3355: import startup scripts from vyatta-cfg repo for vyos-router</title>
<updated>2023-07-09T18:45:15+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-07-09T18:45:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=00f95c93b6c3aca25d5f4ba0e29b4f8db954952c'/>
<id>urn:sha1:00f95c93b6c3aca25d5f4ba0e29b4f8db954952c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T5282: remove systemd management directive for frr.service</title>
<updated>2023-06-12T16:29:45+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2023-06-12T15:41:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=01028cf993e4c75462d62215e04b3934df95207d'/>
<id>urn:sha1:01028cf993e4c75462d62215e04b3934df95207d</id>
<content type='text'>
frr.service startup and shutdown is now explicitly managed by
vyos-router, so remove the systemd management directive.
</content>
</entry>
<entry>
<title>dns: T5144: Streamline ddclient systemd service override</title>
<updated>2023-06-04T08:59:49+00:00</updated>
<author>
<name>Indrajit Raychaudhuri</name>
<email>irc@indrajit.com</email>
</author>
<published>2023-06-04T07:27:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=c14825f55d286d54ca3c04703ecbded1cb4c2cca'/>
<id>urn:sha1:c14825f55d286d54ca3c04703ecbded1cb4c2cca</id>
<content type='text'>
Templatize systemd override for ddclient service and move the generated
override files in /run. This ensures that the override files are always
generated afresh after boot.

Additionally, simplify the systemd override file by removing the
redundant/superfluous overrides.
</content>
</entry>
<entry>
<title>router-advert: T5240: verify() that no more then 3 IPv6 name-servers configured</title>
<updated>2023-05-28T13:23:33+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-05-28T13:23:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=8ef017a3496467433c311af63116af7657c58037'/>
<id>urn:sha1:8ef017a3496467433c311af63116af7657c58037</id>
<content type='text'>
This is a radvd limitation.
</content>
</entry>
<entry>
<title>hostapd: T5151: Override ConditionFileNotEmpty</title>
<updated>2023-04-10T17:19:30+00:00</updated>
<author>
<name>Andrew Gunnerson</name>
<email>accounts+github@chiller3.com</email>
</author>
<published>2023-04-10T17:19:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=8eb85739c9656ba1447d61364117c9c06b0f867b'/>
<id>urn:sha1:8eb85739c9656ba1447d61364117c9c06b0f867b</id>
<content type='text'>
Debian's `debian/2%2.10-12` update of the hostap packaging added a
ConditionFileNotEmpty directive for `/etc/hostapd/&lt;...&gt;` paths, which
doesn't match the `/run/hostapd/&lt;...&gt;` paths that VyOS uses. This commit
updates the override file to use the proper VyOS paths.

https://salsa.debian.org/debian/wpa/-/commit/d204ceb5a2dc33db888eb55b5fee542a1005e69c

Signed-off-by: Andrew Gunnerson &lt;accounts+github@chiller3.com&gt;
</content>
</entry>
</feed>
