- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 31 2026
Sorry, I forgot to say hello
Also, the Last Interface Success and Last Interface Failure times are misleading. The following indicates that the last time the interface passed tests was 1 day, 3:30:28.663652 ago. I imagine that the actual "Last Interface Success" was seconds or minutes ago. Either the time shown should be changed to be accurate for the label or the label should be updated to accurate describe the time shown.
Aug 30 2026
It seems the issue at stake is https://github.com/avahi/avahi/issues/379 upstream, which is patcheable but is present in avahi-daemon 0.8 which is the version running in VyOS.
We don't need ovpn-backports (for now) since the shipped kernel already includes the ovpn module.
Long due...PRs posted:
Aug 29 2026
yep hope this gets added. openvpn dco seems ready for primetime and various online benchmarks show it outperforming wireguard and using half the cpu or less in doing so, on x86 AM4 platforms using AES-NI ciphers.
I will help formatting the PR if anything, dont woryy
You are right - Public task first, then PR with the T task reference
Ok, thank you! For some reason I thought this projected wanted an issue created before opening any PRs, but I see that isn't the case in the contributing docs. Should I reference this issue in my PR?
Thanks,
yes, usually if you have a fix - you fork the vyos.vyos, branch it, implement the fix and raise a PR that VyOS Gurus review and make it merge at some point.
Alternatively, you submit a bug or feature request, and other collaborators can try and implement it.
Sorry for the confusion, no PR opened for this. I figured I'd include relevant information for a potential fix. I can open a PR with the changes to plugins/modules/vyos_user.py if I'm not missing anything.
@mson thanks for submitting this!
You mentioned a fix - is there a PR for this, or you want someone to look into this and fix, please?
I am unable to edit the task (issues with edit policy permissions). However, the following line can be ignored:
Aug 28 2026
Won't do as the requested feature is in netcommon and more advanced. I see no point in re-creating it specifically in this collection
Aug 27 2026
@Viacheslav
I used an AI assistant to draft the write-up. The bug, the diagnosis and the production validation are mine — I've been chasing this for two days on a live HA pair. Happy to answer anything about the code.
if that helps, I worked on a fix for defect 2 and created a draft PR
https://github.com/vyos/vyos-1x/pull/5430
vyos-1x#5421 closed by jestabro: post-config.d is unused Vyatta-era and will not be returned in this form. docs#2217 closed to match. We keep an operator vyos-postconfig-bootup.script runner out of tree.
Addressed alexk37 2026-08-22 follow-up on https://github.com/vyos/vyos-1x/pull/5342 (a526ccdde; rebased onto current rolling):
Addressed alexk37 2026-08-22 follow-up on https://github.com/vyos/vyos-1x/pull/5340 (6d2ee03b2; rebased onto current rolling):
@Viacheslav which option would you choose for Defect 1 ? regex extension ?
I probably shoudn't have claimed this one, should I ?
Fix proposed in https://github.com/vyos/vyos-1x/pull/5429
@Viacheslav, sure
@rockfish do you want to claim the task and add a PR fix?
FYI, this is meant for VyOS Ansible Collection but the "Submit Bug Report" link from the home page populates the form with the VyOS Rolling tag, and I was not able to update it.
Aug 26 2026
Is there any update on this at all, please? Stream is still sitting vulnerable as far as I can see. Even a Stream 2006.03-1 with just an updated kernel would have been vastly preferable, versus no mitigation and no new Stream image for >3 months since the CVE disclosures (and five months since the last Stream release).