Age | Commit message (Collapse) | Author |
|
|
|
xml: T6319: add util for ancestor owner/priority
|
|
|
|
T6310: added codeql workflow
|
|
bgp: T6082: Allow the same local-as and remote-as in one peer group
|
|
op-mode: T6284: IPoE-server op-mode does not show IPv6 address field
|
|
T6305: accept ipoe interfaces on firewall ruleset
|
|
|
|
|
|
|
|
|
|
|
|
feat: added codeql caller workflow - workflow dispatch
|
|
|
|
10000: added codeql caller workflow
|
|
|
|
vyos.template: T3664: use a module-level global variable for the default template directory
|
|
template directory
as a more convenient and secure alternative to environment variable
|
|
T6307: Add dependency procps to build vyos-1x
|
|
|
|
T6298: Fix TPM incorrect path for rc_cmd
|
|
Fix import for `rc_cmd`
|
|
T6291: Add bonding.py to op-mode-standardized.json
|
|
|
|
smoketest: T6283: T6250: add testcases
|
|
show interfaces bonding lacp detail
show interfaces bonding <bondif> lacp detail
show interfaces bonding <bondif> lacp neighbors
Co-authored-by: l0crian1 <ryan.claridge13@gmail.com>
|
|
|
|
qos: T6225: Fix qos random-detect policy
|
|
Fix default values for random-detect
Remove dsmakr qdisc from gred cofig because dsmark was deleted from kernel
|
|
ntp: T4909 rewrite NTP op mode in the new format
|
|
T6269: policy: ensure correct rule parsing when using, and when not using <set table> option in policy route.
|
|
|
|
bgp: T6189: L3VPN connectivity is broken after re-enabling VRF
|
|
smoketest: T6199: remove redundant code when unpacking Kernel GZ config
|
|
|
|
After e7bb65894 ("vrf: T6189: render FRR L3VNI configuration when creating VRF
instance") we need to ensure that the VRF L3VNI configuration is removed in FRR
prior to removing the BGP VRF instance.
The reason is [1] where FRR only allows VRF BGP instance to be removed when
there is NO VNI configured anymore.
1: https://github.com/FRRouting/frr/blob/064c3494527b9e84260410006768ed38e57e1de7/bgpd/bgp_vty.c#L1646-L1650
|
|
When adding and removing VRF instances on the fly it was noticed that the vni
statement under the VRF instance in FRR vanishes. This was caused by a race
condition which was previously designed to fix another bug.
The wierd design of a Python helper below the VRF tree to only generate the
VNI configuration nodes is now gone and all is rendered in the proper place.
|
|
pppoe-server: T6234: PPPoE-server pado-delay refactoring
|
|
T6287: Config-sync add the ability to configure API port
|
|
T6056: Change static-host-mapping should not restart snmpd
|
|
We have several config XML definitions that use the same python3
script `system_host-name.py`
https://github.com/vyos/vyos-1x/blob/current/interface-definitions/system_name-server.xml.in
https://github.com/vyos/vyos-1x/blob/current/interface-definitions/system_host-name.xml.in
https://github.com/vyos/vyos-1x/blob/current/interface-definitions/system_static-host-mapping.xml.in
https://github.com/vyos/vyos-1x/blob/current/interface-definitions/system_domain-name.xml.in
https://github.com/vyos/vyos-1x/blob/current/interface-definitions/system_domain-search.xml.in
Any change in these scripts calls to restart the `service snmpd`
The service `snmpd` should be restarted only if `host-name` or
`domain-name` was changed.
It is a good idea to rewrite it to `get_config_dict` in the future.
|
|
firewall: T6257: Show member information for dynamic groups in op-mode
|
|
Add the ability to configure the API port if the API on the secondary
server works on a non-default port.
The primary node will connect to configured port for config-sync
```
set service config-sync secondary address '192.0.2.11'
set service config-sync secondary port '8443'
```
|
|
haproxy: T6179: fix rule generation
|
|
|
|
T6267: Check interface wireless module before apply config
|
|
T6169: DNS forwarding should allow underscore for srv record
|
|
This srv recors looks valid:
```
set service dns forwarding authoritative-domain _tcp.db.mongors1.example.com records srv _mongodb entry 0 hostname 'mongors1.example.com'
```
But FQDN validator cannot validate it correctly, use regex to fix
|
|
T6273: Allowed the use of "-" and "_" in PPPoE access-concentrator name
|
|
Allowed the use of "-" and "_" in PPPoE access-concentrator name
|