For dummy it works because it has the prefix /128 and it is allowed/validated https://github.com/vyos/ipaddrcheck/blob/c34294b7a18072c7bd4eaf8ec0f433bb374fad5c/src/ipaddrcheck.c#L577
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Nov 26 2025
@o.kuchmystyi
reproduced in 2025.11.26-0020-rolling, it requires an active ipsec tunnel to be established with peer B during commit:
I tried to reproduce these errors for VyOS 2025.11.25-rolling but everything works fine. @a.kudientsov could you re-check it again?
Nov 25 2025
This specific case when servers are unavailable is consistent with other vendors' behavior and likely worth fixing. Commit performance issues when TACACS servers are slow to respond or need to be contacted frequently is a different issue and we will eventually improve that.
Nov 24 2025
Nov 24 20:55:39 systemd[1]: Starting Cleanup of Temporary Directories... Nov 24 20:56:39 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Nov 24 20:56:39 systemd[1]: Finished Cleanup of Temporary Directories. Nov 24 20:56:39 systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Nov 24 20:58:53 sudo[3835]: pam_unix(sudo:session): session closed for user root Nov 24 20:58:53 systemd[1]: opt-vyatta-config-tmp-new_config_3466.mount: Deactivated successfully. Nov 24 20:58:53 sudo[3958]: vyos : TTY=pts/1 ; PWD=/home/vyos ; USER=root ; COMMAND=/usr/bin/mv /tmp/config.boot.3949 /opt/vyatta/etc/config/archive/config.boot Nov 24 20:58:53 sudo[3958]: pam_unix(sudo:session): session opened for user root(uid=0) by vyos(uid=1003) Nov 24 20:58:53 sudo[3958]: pam_unix(sudo:session): session closed for user root Nov 24 20:58:53 sudo[3961]: vyos : TTY=pts/1 ; PWD=/home/vyos ; USER=root ; COMMAND=/usr/sbin/logrotate -f -s /opt/vyatta/etc/config/archive/lr.state /opt/vyatta/etc/config/archive/lr.conf Nov 24 20:58:53 sudo[3961]: pam_unix(sudo:session): session opened for user root(uid=0) by vyos(uid=1003) Nov 24 20:58:53 sudo[3961]: pam_unix(sudo:session): session closed for user root Nov 24 20:58:53 commit[3965]: Successful change to active configuration by user vyos on /dev/pts/1
T7940 will require implementing this. I don't think I would be able to implement this all by myself and will need some guidance.
Not specific to VPP, but in general
Encryption/decryption failures for AES-GCM don't reproduce anymore, tested the following variants:
Nov 23 2025
vrf <name> option that is only used for verifying that the source address is assigned.
This was used in the past to start the old pmacct implementation in the appropriate VRF context.