This is how the PKI subsystem works. You should add the LE root certificates manually so we can build a full chain using the internal PKI tools for HTTPS server.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Mar 24 2024
disabling it on a per interface basis will still crash the OS if the register read/write is implemented improperly.
What about OSPF,OSPFv3 and the other routing daemons?
confirmed fixed in 1.5-rolling-202403240925
Reopened with status "Known issue" due to revert by PR 3177.
To clearify:
Thanks will test the next release
This pretty much feels like the same issue - a fix will be present in the next 1.5 rolling release.
hardware details below
In theory that could work as a workaround as-well, it would be more precise than my current workaround, but would require the build process for my tool to download the iso, spin up a vm, and extract the info.
Sounds interesting but isn't it enough to query dpkg?
Reverted via https://github.com/vyos/vyos-1x/pull/3177
Using igb.EEE=0 or EEE=0 on the kernel commandline has no effect
My best bet would be an issue with reading back the EEE registers of the Realtek r8169 driver.
Mar 23 2024
Output for a standard check with section ['nat'] and for the test case above, with debug logging on; changes are correctly mirrored on secondary node:
Mar 22 2024
Note that the subtask T6146 is useful in itself, as a modernization of the legacy tool priority.pl, but manual ordering of config-sync sections to address this issue is fragile, given the subtleties (== design constraints) of the legacy commit algorithm (cf. T5492). It is preferable to hand the full commit proposal of the primary node to the secondary node, and allow the underlying configsession to manage priority ordering --- this may be easy to do with a simple refactor in the post-commit hook and (if needed) adjustment in the http-api request handler.