Thanks for verifying. Interesting, is it also using the custom Podman package?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 7 2024
Aug 6 2024
1.4 is not affected
vyos@r15:~$ show version all | match podman
ii podman 4.9.5 amd64 Engine to run OCI-based containers in Pods
vyos@r15:~$
vyos@r15:~$
vyos@r15:~$ show container image
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/vyos-flowspec-netfilter 1.0 2b8b95eddb07 2 weeks ago 91.5 MB
docker.io/adguard/adguardhome v0.107.52 6543abecfa41 4 weeks ago 71.4 MB
vyos@r15:~$
vyos@r15:~$
vyos@r15:~$ cat /etc/containers/policy.json
{
"default": [
{
"type": "insecureAcceptAnything"
}
]
}
vyos@r15:~$
vyos@r15:~$
vyos@r15:~$ show version
Version: VyOS 1.4-rolling-202408051021
Release train: sagitta
Release flavor: isoVerified on my 1.4 install the policy.json is present, but missing in the latest rolling release
Aug 5 2024
Aug 4 2024
Aug 3 2024
New PR created for matching functionality in policy local-route: https://github.com/vyos/vyos-1x/pull/3938
Aug 2 2024
Aug 1 2024
The server has 8GB RAM
@bernhardschmidt my PR for this made it into current rolling, which rather than just widening the table range, allows using 'set vrf' instead of 'set table' to policy route directly to VRFs with out-of-range RT IDs.
How much RAM does this server have?
Do you have an example of the log when it fails? Which exact messages do you see?
Request to drop privileges https://support.zabbix.com/browse/ZBXNEXT-9380
Jul 31 2024
There are issues with cgroups when enabling VRF
$ git diff diff --git a/data/templates/zabbix-agent/10-override.conf.j2 b/data/templates/zabbix-agent/10-override.conf.j2 index 7c296e8fd..0acf775be 100644 --- a/data/templates/zabbix-agent/10-override.conf.j2 +++ b/data/templates/zabbix-agent/10-override.conf.j2 @@ -1,3 +1,4 @@ +{% set zabbix_command = 'ip vrf exec ' ~ vrf ~ ' ' if vrf is vyos_defined else '' %} [Unit] After= After=vyos-router.service @@ -7,7 +8,9 @@ ConditionPathExists=/run/zabbix/zabbix-agent2.conf [Service] EnvironmentFile= ExecStart= -ExecStart=/usr/sbin/zabbix_agent2 --config /run/zabbix/zabbix-agent2.conf --foreground +ExecStart={{ zabbix_command }}/usr/sbin/zabbix_agent2 --config /run/zabbix/zabbix-agent2.conf --foreground +CapabilityBoundingSet=CAP_NET_ADMIN CAP_SYS_ADMIN CAP_SYS_RESOURCE CAP_BPF CAP_DAC_OVERRIDE CAP_FOWNER +AmbientCapabilities=CAP_NET_ADMIN CAP_SYS_ADMIN CAP_SYS_RESOURCE CAP_BPF CAP_DAC_OVERRIDE CAP_FOWNER WorkingDirectory= WorkingDirectory=/run/zabbix Restart=always diff --git a/interface-definitions/service_monitoring_zabbix-agent.xml.in b/interface-definitions/service_monitoring_zabbix-agent.xml.in index 3754e9145..e44b31312 100644 --- a/interface-definitions/service_monitoring_zabbix-agent.xml.in +++ b/interface-definitions/service_monitoring_zabbix-agent.xml.in @@ -185,6 +185,7 @@ </properties> <defaultValue>3</defaultValue> </leafNode> + #include <include/interface/vrf.xml.i> </children> </node> </children>
I was hoping some combination of the newer QAT driver 4.24 and newer kernel in the latest rolling releases might fix this... but seemingly not.
I finally managed to give 1.5 a run and the first thing I did was check this. Perfect! Thank you everyone,