| Age | Commit message (Collapse) | Author |
|---|
|
Updated language of "VLANs are enabled/disabled" to "VLANs enabled/disabled"
Co-authored-by: Christian Breunig <christian@breunig.cc>
|
|
Updated language of amRoot to " (This bridge is the root)"
Co-authored-by: Christian Breunig <christian@breunig.cc>
|
|
When using the VyOS internal PKI subsystem to request a certificate using ACME,
the issuer CA is not automatically imported in the PKI subsystem on the first
run due to a race condition.
Issue is fixed by adding all newly requested and granted ACME certificates to
the list of ACME certificates "on disk" which are used to extract the issuing
CA certificate.
|
|
The service certbot expects symbolic links for
/config/auth/letsencrypt/live/<cert_name>/*.pem
however, the default behavior of copytree copies the linked files during
image upgrade. Set copytree argument to preserve symlinks.
|
|
Created stp.py to create output for spanning-tree info
Modified show-bridge.xml.in to add:
show bridge spanning-tree
show bridge spanning-tree detail
show bridge <interface> spanning-tree
show bridge <interface> spanning-tree detail
|
|
|
|
T7278: Remove cracklib hack from postconfig script template
|
|
firewall: T5493: Implement remote-group
|
|
|
|
|
|
|
|
T7138: Fix show qos
|
|
wireguard: T7246: verify Base64 encoded 32byte boundary on keys
|
|
Not 31 bytes or 33 bytes, but exactly 32. This matters, because 32 does not
divide evenly by .75, so there's a padding character and the penultimate
character does not include the whole base64 alphabet.
Extend the base64 validator with an optional argument to define the length
to match of the decrypted Base64 encoded string.
Source: https://lists.zx2c4.com/pipermail/wireguard/2020-December/006222.html
|
|
T7189: VPP source of the tunnel interface should be checked and configured
|
|
|
|
T7181: VPP add initial source NAT implentation
|
|
T7121: Set up communication vyconfd to vyos-commitd
|
|
pki: T7249: fix shebang to support CLI backend
|
|
* bgp: T7157: Allow using route-maps for VRF route leaking in BGP
Added the possibility of using route-map in route leaking.
* Improve the constraint error message
---------
Co-authored-by: Daniil Baturin <daniil@baturin.org>
|
|
Fixes an error:
interpreter/vyatta-cfg-run: line 162: `vyatta_config_commit-confirm': not a valid identifier
Which prevented to renew the certificates. This will only fix renewing of the
certificates. Nothing changed in how daemons will be restarted if a certificate
is updated.
|
|
|
|
|
|
This change corrects a behavior witnessed in T7138. If a policy name had a `-` in it, the command would fail, returning nothing.
|
|
|
|
vyos-commitd exchanges messages with vyconfd, to replace the shim
redirection of legacy commands to vyos-configd.
|
|
|
|
|
|
|
|
Changed priority for VPP interfaces: all VPP interfaces must be configured after Ethernet interfaces
|
|
T7219: Add check for remote and group command to verify
|
|
T7092: Add Container Registry Mirror
|
|
|
|
|
|
Rename directory in EFI system partition from:
From: \EFI\VyOS (RAID disk 1)
To: \EFI\VyOS
This prevents GRUB dropping to a grub prompt rather than showing the VyOS boot menu, after installing with the RAID1 option.
Refer bug: https://vyos.dev/T7049
|
|
|
|
T7200: Reduce memory size usage for vpp smoke tests
|
|
T6948: Keep DHCP server leases in sync with hostd records
|
|
wireguard: T7166: Call vxlan dependency if interface exist
|
|
|
|
policy: T7116: Remove unsupported use of BGP community "internet"
|
|
Allow to bridge bonding interfaces:
```
set vpp interfaces bonding bond0 member interface 'eth1'
set vpp interfaces bridge br10 member interface bond0
```
|
|
* wlb: T7196: Migrate interface wildcards to nftables format
* wlb: T7196: Fix exclude/interface verify check
* wlb: T7196: Extra sanity check on ipv4 address function
|
|
This has been split into a separate commit in case this is overkill for
the fix. 1.2 and 1.3 installs predate the change to FRR that removed support,
but "internet" is already broken on 1.4.
|
|
add more memory validation
|
|
Allow to configure VPP loopback interface as BVI interface
In the VPP a bridge-domain is the L2 bridge and does not have
its own interface
Loopback is required if we want to ping from/to the bridge.
```
set vpp interfaces bridge br10 member interface lo23 bvi
```
|
|
* snmp: T7180: Fixed verification of engineid in snmpv3
EngineID must be configured if snmpv3 user is configured.
Fixed engineid help string.
|
|
lldp: T7165: add support to enable only rx/tx on specific interfaces
|
|
T7171: Add dstport option to GENEVE tunnels
|
|
|
