- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 30 2026
Jun 29 2026
1. Exposed MCP Resources
Resources expose read-only context to the language model via specific URIs. Instead of forcing the AI to read a massive monolithic configuration file, the system provides targeted data slices.
Typos-check pilot COMPLETE — 2026-06-29.
Jun 28 2026
Jun 27 2026
Jun 26 2026
I found this as a workaround but again would be handy if things would work out of the box :-)
Another option/workaround would be if something like "config replace" would be supported where the input could be a "config.cmd".
PR that fixes behavior and introduces validation: https://github.com/vyos/vyos-1x/pull/5297
PR submitted for this: https://github.com/vyos/vyos-1x/pull/5296
Jun 25 2026
@o.kuchmystyi I confirm that works, thanks.
Jun 24 2026
@ssasso you can verify it by deleting 'address-family l2vpn-evpn vni <id>':
I have found the root cause of this issue:
- VyOS generates a vni <id> block inside router bgp <asn> vrf <name> / address-family l2vpn evpn for each VRF:
FRR has a bug where no bmp connect HOSTNAME port PORT min-retry MSEC max-retry MSEC source-interface WORD always fails with "No such active connection found" even when the parameters match the active connection. Deletion only works when source-interface is omitted from the command.
Update -- confirmed to be a bug, since rolling release works perfectly.
Here you go:
Jun 23 2026
I'll have to think about how to test this now, we migrated the last Sophos UTM over the weekend, after which we migrated all tunnels from IPSec to wireguard.
Hopefully resolved by upgrading to Strongswan 6.0.6.
Could you please check latest rolling release?
Thank you.