PR https://github.com/vyos/vyos-build/pull/807

Looking at the igb module from latest vyos, it is getting signed. Why is this one not signed?

It needs to sign the modules somehow
example
https://github.com/vyos/vyos-build/blob/910eece6d3dede212a0f6172272d248601ab1090/scripts/package-build/linux-kernel/build-intel-ixgbe.sh#L83

PR: https://github.com/vyos/vyos-1x/pull/4108

PR: https://github.com/vyos/vyos-1x/pull/4146

the frr issue is fixed for versions 10.1, 10.0, 9.1. It is necessary to retest with the new build

Can't reproduce on my end:

6.6.51
sudo find / -name config-uname -r
/usr/lib/live/mount/rootfs/1.5-rolling-202409250007.squashfs/boot/config-6.6.51-vyos
sudo grep MODULE_SIG /usr/lib/live/mount/rootfs/1.5-rolling-202409250007.squashfs/boot/config-6.6.51-vyos
CONFIG_MODULE_SIG is not set

Channels have been working for a while. If the issue comes back, feel free to reopen.

Since no one complained in a long time, I presume the issue is not present in recent versions. But if it comes back, feel free to reopen.

There's a proper tsort library now and prototypes are already in the current VyOS.

I created a separate task for the issue with GeoIP database updates failing regardless of the VRF: https://vyos.dev/T6768

If cases where the issue still exists are found, feel free to reopen the task.

I have been getting headers from http://dev.packages.vyos.net/repositories/current current main" 6.6.52 is the latest there.

Hi, I have upgraded to latest rolling. That is how I know you are now on 6.6.54. I get the error modprobe: ERROR: could not insert 'r8152': Key was rejected by service.

In T6713#201597, @SteveP wrote:

Hi,

It is not working I'm afraid.

modprobe: ERROR: could not insert 'r8152': Key was rejected by service

It is a signing error. I am getting the same thing now with 6.6.52 (I just tried it) but 6.6.51 (one I am running) is fine. I can't try 6.6.54 as the headers are not there.

SteveP

I don't think it is related to secure boot.

Could it be related to this: https://portal.productboard.com/vyos/1-vyos-roadmap/c/67-secure-boot-uefi

It is not working I'm afraid.

Can you check if changing this line https://github.com/vyos/vyos-1x/blob/current/data/templates/login/tacplus_nss.conf.j2#L33 and adding those user helps?
This file can be changed locally in the router: /usr/share/vyos/templates/login/tacplus_nss.conf.j2
Change line:

exclude_users=root,telegraf,radvd,strongswan,tftp,conservr,frr,ocserv,pdns,_chrony,_lldpd,sshd,openvpn,radius_user,radius_priv_user,*{{ ',' + user | join(',') if user is vyos_defined }}

And change it to something like:

Driver added to the latest rolling release

vyos@r14# run show version all | match realtek
ii  vyos-drivers-realtek-r8152           2.18.1-1                                    amd64        auto-generated package by debmake
[edit]
vyos@r14#

PR https://github.com/vyos/vyos-build/pull/802

The deb package for vici is broken and does not include CONTENTS/usr/lib
I.e., the script to build vici works incorrectly https://github.com/vyos/vyos-build/blob/current/scripts/package-build/strongswan/build-vici.sh

vyos@r14:~$ show version all | match vici
ii  python3-vici                         5.9.11-2+vyos0                              all          Native Python interface for strongSwan's VICI protocol
vyos@r14:~$

If the device is not even listing in lspci it's more of a Hyper-V thing then VyOS.