I figured out the order we need to remove things in:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 3 2021
Aug 2 2021
PR for current version https://github.com/vyos/vyos-1x/pull/952
I've cleaned the build space and rebuilt the Docker container - no dice locally or in the CI stack, still fails the same way.
It looks like they're using an AWS CA in the cert chain:
Certificate chain 0 s:CN = repo.saltstack.com i:C = US, O = Amazon, OU = Server CA 1B, CN = Amazon 1 s:C = US, O = Amazon, OU = Server CA 1B, CN = Amazon i:C = US, O = Amazon, CN = Amazon Root CA 1 2 s:C = US, O = Amazon, CN = Amazon Root CA 1 i:C = US, ST = Arizona, L = Scottsdale, O = "Starfield Technologies, Inc.", CN = Starfield Services Root Certificate Authority - G2 3 s:C = US, ST = Arizona, L = Scottsdale, O = "Starfield Technologies, Inc.", CN = Starfield Services Root Certificate Authority - G2 i:C = US, O = "Starfield Technologies, Inc.", OU = Starfield Class 2 Certification Authority
i do recall the starfield certs being a problem back in the day as well, but guessing its quite unlikely for the base build environment to have an AWS root CA in its trusted list.
Aug 1 2021
Jul 31 2021
I have added a test which does not let you delete the default BGP instance when VRF bound instances exist.
This is causing a configtest failure on 1.4-rolling-202107301807 stemming from not cleaning up after bgp-evpn-l3vpn-pe-router ("Cannot delete default BGP instance. Dependent VRF instances exist"):
PR for 1.3 https://github.com/vyos/vyos-1x/pull/950
Using timeouts is a pretty bad idea as they vary on the host CPU or utilisation of a hypervisor.
it should be timeout ~1.8 sec between adding ipv6 address and create l2tp interface
Jul 30 2021
As I see it's already fixed:
vyos@r4-1.3# set protocols bgp 64512 neighbor 192.168.5.5 local-as 64513 [edit] vyos@r4-1.3# set protocols bgp 64512 neighbor 192.168.5.5 remote-as 64513 [edit] vyos@r4-1.3# commit [ protocols bgp 64512 neighbor 192.168.5.5 local-as 64513 ] local-as: 64513 and remote-as: 64513 can't be the same
PR for current https://github.com/vyos/vyos-1x/pull/949
Jul 29 2021
They should be disabled by default, but there must be the ability to re-enable OIDs back from CLI.
PR for 1.3 https://github.com/vyos/vyatta-cfg-quagga/pull/86
add option "solo" for neighbor.
PR https://github.com/vyos/vyos-1x/pull/945
Also, need to cherry-pick it to Equuleus
It was a lot of problems with high CPU utilization with these mibs T1705.
https://forum.vyos.io/t/high-cpu-usage-by-bgpd-when-snmp-is-active
Jul 28 2021
Jul 27 2021
Wireguard has its own fwmark setting, such as: