will you add podman exporter as well?

For me, "exclude-section" looks better choice than just "exclude".

In T6444#196023, @Viacheslav wrote:

Needs to think.
I think there should be an exclude-section or exclude

i see in your repo you install the latest sphinx version in you CI pipeline?
please try sphinx < 8.0.0

It seems the bug even if configuration applied in one commit:

set interfaces ethernet eth1 vif 21
set interfaces ethernet eth1 vif 22
set interfaces bridge br1 member interface eth1.21 isolated
set interfaces bridge br1 member interface eth1.22 isolated
commit

check:

vyos@r1# bridge --json -d link | jq '.[] | {ifname, isolated}'
{
  "ifname": "eth1.21",
  "isolated": false
}
{
  "ifname": "eth1.22",
  "isolated": false
}

Does this also mean that we can no longer use unsigned drivers with non EFI systems? I can't at the moment. It would be nice if we could choose to use the pre 6.6.52 behaviour if we want to.

I have also signed my Realtek driver with the same cert but that did not work. Perhaps we could pick that back up over on T6713

The rolling images are currently not yet secure boot signed. We are in the design and validation how we can to this from a CI/CD perspective in a secure way.

I have installed the latest rolling release and upon reboot I am getting:

I have installed the latest rolling release and the r8152 driver does seem ok (interface now comes up) however, eth0 now disappears. It is being renamed to eth5 (the r8152). This is eerily similar to T1066 I was involved in back in 2019. Turned out to be a kernel bug. Was not working with kernel 4.19.52 and was fixed in kernel 4.19.54

Yes, that‘s correct behavior.

That's actually an interesting idea to force config commit messages if archive option is set to git

Hi c-po

Hi c-po

@SteveP you need to install the MOK, see https://docs.vyos.io/en/latest/installation/secure-boot.html

For those keen to test secure boot support please see https://docs.vyos.io/en/latest/installation/secure-boot.html