Personally, I would just create a directory in /usr/local/share/ca-certificates/ for each CA certificate named the same as that part of the config node (ex: IPA.TRAE32566.ORG in my example), then run update-ca-certificates...I just don't know how to implement this myself.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 24 2024
Oct 23 2024
Oct 22 2024
Oct 21 2024
The original driver will be included in the next rolling release
I am not sure if this a driver problem.
You can add PR for the documentation without a task
Oct 20 2024
Oct 19 2024
Initial PR is here, https://github.com/vyos/vyos-1x/pull/4166.
Issue fixed by Github
Oct 18 2024
@dmbaturin, should this task be in the rolling release project, too?
Probably related driver T6713
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?
Oct 17 2024
Realtek also listed a new driver yesterday.
Bump Realtek driver version
PR https://github.com/vyos/vyos-build/pull/814
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.
Oct 16 2024
@marekm: Bugfixes will be towards current (aka 1.5-rolling as of writing) which then is being cherrypicked and backported by VyOS Networks to whatever older releases that needs that and are compatible with the change/fix/added feature.
OK, I'll keep on it
That looks like a very much breaking change to me, not perfectly compatible. No more access to source code for LTS branches means it may not be possible to work on bug fixes (not just new functionality) anymore. So, to submit three PRs with bug fixes in the LTS branch to qualify for a subscription, one first needs to have a subscription. I don't think this will encourage more contributors to help the project. Is this intentional?
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.
Oct 15 2024
PR for current/Circinus/Sagitta:
https://github.com/vyos/vyos-http-api-tools/pull/19
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.