vyos-1x.git/interface-definitions/include/constraint, branch c-po-patch-1

firewall: T7177: update interface-name.xml.i constraint and smoketest to support pod interfaces from containers

2025-02-19T16:30:14+00:00

xml: T7161: provide re-usable building block for alternative routing tables

2025-02-13T16:00:01+00:00

T6214: T6213: change constraint in order to not allow string starting with dot character; use such constraint in firewall group definitions.

2024-04-09T16:50:36+00:00

xml: T5738: extend VRF building blocks with common constraint definition

2024-04-01T18:27:24+00:00

xml: T5738: use common constraint include for container network

2024-03-24T19:30:33+00:00

dhcp-client: T6093: extend regex for client class-id's with DOT

2024-03-10T19:06:42+00:00

The regex used is not working if the string contains dots. Originally authored by: Lucas

pki: T5886: add support for ACME protocol (LetsEncrypt)

2024-01-06T07:33:33+00:00

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 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.

xml: T5738: add constraint building block with alphanumeric, hypen, underscore and dot

2024-01-03T16:22:59+00:00

configverify: T5880: raise exception if interfaces sourced form dynamic interfaces

2024-01-01T00:01:25+00:00

Interfaces matching the following regex (ppp|pppoe|sstpc|l2tp|ipoe)[0-9]+ can not be used as source-interface for e.g. a tunnel. The main reason is that these are dynamic interfaces which come and go from a kernel point of view, thus it's not possible to bind an interface to them.

bgp: T591: add SRv6 support from FRR

2023-12-11T17:21:26+00:00

set protocols bgp sid vpn per-vrf export '99' set protocols bgp srv6 locator 'foo' set protocols bgp system-as '100' Will generate in FRR config router bgp 100 no bgp ebgp-requires-policy no bgp default ipv4-unicast no bgp network import-check ! segment-routing srv6 locator foo exit sid vpn per-vrf export 99 exit