The original driver will be included in the next rolling release

Can you check adding the next command?

https://github.com/vyos/vyos-1x/pull/4167

I am not sure if this a driver problem.

In July Podman was upgraded from 4.3 (debian package) to 4.9 (custom built package)

@dmbaturin, should this task be in the rolling release project, too?

Should be fixed in the next rolling release

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

It has a capcha on it so you will probably have to host it yourselves, also see note re new version yesterday. looks like the same one from May to me.

@SteveP could you provide the link to the source code (git) for the official drivers?
Where we can clone the code and build correct package for Debian?

Realtek also listed a new driver yesterday.

Bump Realtek driver version
PR https://github.com/vyos/vyos-build/pull/814

We use this https://github.com/vyos/vyos-build/blob/2359180068a653e39724a33b91bfa1ed395c1993/scripts/package-build/linux-kernel/build-realtek-r8152.py#L38

Now that I have stopped your vyos-drivers-realtek-r8152_2.18.1-1_amd64.deb module from loading in data/architectures/amd64.toml and have turned off CONFIG_MODULE_SIG_FORCE, I can load my unsigned r8152.ko re-compiled for 6.6.56 and loaded from vyos-preconfig-bootup.script as I always have and everything is working. I suspect that this is because it is loading later after the nic renaming has been done.

OK, I'll keep on it

You can add PR a delete here https://github.com/vyos/vyos-build/blob/2359180068a653e39724a33b91bfa1ed395c1993/data/architectures/amd64.toml#L9
I think it is better to figure out what could be wrong

I have compiled a kernel with CONFIG_MODULE_SIG_FORCE off so I can load unsigned drivers. This worked fine. I then made an iso with the stock r8152 drivers, all good so far. I can now load the 2.18.1 drivers on 6.6.56 after everything has booted and settled down. It still breaks the router.

https://github.com/vyos/vyos-1x/pull/4155

Hi, If we are not going forward with this could we please remove the broken driver and go back to the stock one. It is not useable at all with a r8152 loaded at the moment as it breaks eth0 too early on.

@c-po So what's interesting here is it seems like it might be something with the reconfiguration of the daemon. Try deleting and then adding the default config, like this (obviously after delete service ntp and commit):

vyos@cr01-vyos# set service ntp allow-client address 127.0.0.0/8
[edit]
vyos@cr01-vyos# set service ntp allow-client address 169.254.0.0/16
[edit]
vyos@cr01-vyos# set service ntp allow-client address 10.0.0.0/8
[edit]
vyos@cr01-vyos# set service ntp allow-client address 172.16.0.0/12
[edit]
vyos@cr01-vyos# set service ntp allow-client address 192.168.0.0/16
[edit]
vyos@cr01-vyos# set service ntp allow-client address ::1/128
[edit]
vyos@cr01-vyos# set service ntp allow-client address fe80::/10
[edit]
vyos@cr01-vyos# set service ntp allow-client address fc00::/7
[edit]
vyos@cr01-vyos# 
[edit]
vyos@cr01-vyos# set service ntp server time1.vyos.net
[edit]
vyos@cr01-vyos# set service ntp server time2.vyos.net
[edit]
vyos@cr01-vyos# set service ntp server time3.vyos.net
[edit]
vyos@cr01-vyos# commit
Archiving config...
  sftp://stor01a-rh9.int.trae32566.org/bhs/cr01-vyos Host 'stor01a-rh9.int.trae32566.org' not found in known hosts.
Fingerprint: 1083a0c4ff8380df83596781bcddf2a9
Do you wish to continue? [y/N] y

Raised https://github.com/sflow/host-sflow/issues/68 with the above information. Will move over there to continue discussion

If it's helpful, here's a tcpdump of me pinging a resolver, with the response

21:41:33.485179 1e:43:be:d9:9c:90 > 80:7f:f8:74:c8:db, ethertype 802.1Q (0x8100), length 110: vlan 10, p 0, ethertype PPPoE S (0x8864), PPPoE  [ses 0x72d] IP (0x0021), length 86: ??.??.??.?? > 1.1.1.1: ICMP echo request, id 1, seq 1, length 64
21:41:33.487988 80:7f:f8:74:c8:db > 1e:43:be:d9:9c:90, ethertype 802.1Q (0x8100), length 110: vlan 10, p 0, ethertype PPPoE S (0x8864), PPPoE  [ses 0x72d] IP (0x0021), length 86: 1.1.1.1 > ??.??.??.??: ICMP echo reply, id 1, seq 1, length 64

Looks like Linux doesn't provide the PPPoE interface MAC via SIOCGIFHWADDR :(