User Details
- User Since
- Jul 1 2025, 9:10 AM (63 w, 5 d)
Tue, Sep 15
Fri, Sep 11
Jul 28 2026
Jul 24 2026
Yes, I can confirm that it works the same with multiple users in the system:
vyos@vyos1:~$ sudo stat -c '%a %U:%G' .bash_history 600 vyos:users vyos@vyos1:~$ su - testuser testuser@vyos1:~$ pwd /home/testuser testuser@vyos1:~$ sudo stat -c '%a %U:%G' .bash_history 600 testuser:users
Jul 23 2026
I checked it manually and it looks like the metadata was transferred after upgrade:
vyos@vyos1:~$ sudo stat -c '%a %U:%G' .bash_history 600 vyos:users vyos@vyos1:~$ sudo stat -c '%a %U:%G' .ssh/known_hosts 644 vyos:users vyos@vyos1:~$ add system image vyos-999.202607231048-generic-amd64.iso Validating image compatibility Validating image checksums ... Would you like to copy SSH host keys? [Y/n] Copying SSH host keys Would you like to save the SSH known hosts (fingerprints) from your current configuration? [Y/n] Copying SSH known_hosts files Would you like to copy bash history? [y/N] y Copying bash history ... vyos@vyos1:~$ sudo reboot now ... vyos@vyos1:~$ sudo stat -c '%a %U:%G' .bash_history 600 vyos:users vyos@vyos1:~$ sudo stat -c '%a %U:%G' .ssh/known_hosts 644 vyos:users
Jul 22 2026
Jul 15 2026
Pull requests:
Jun 29 2026
Jun 26 2026
PR that fixes behavior and introduces validation: https://github.com/vyos/vyos-1x/pull/5297
Jun 25 2026
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:
Jun 23 2026
@ssasso, I would be grateful if you provide the output of the following command:
- sudo /usr/lib/frr/frr-reload.py --reload --debug --stdout /run/frr/config/vyos.frr.conf
Jun 19 2026
Jun 15 2026
Jun 8 2026
Jun 5 2026
Jun 4 2026
The latest rolling build works and it passes test: https://github.com/vyos/vyos-1x/actions/runs/26947164125
Jun 3 2026
Jun 1 2026
May 29 2026
@ssasso I have tested your setup using 2026.05.28-0044-rolling and I couldn't reproduce this behavior. Could you check it again?
I clarified exactly how this problem reproduces itself. When accel-pppd is running adding an interface to a Linux bond fails with PermissionError: [Errno 1] Operation not permitted. If change the order and configure bonding interface and then pppoe-server service it works fine.
May 28 2026
May 27 2026
May 26 2026
May 25 2026
May 21 2026
May 20 2026
May 19 2026
May 15 2026
May 14 2026
May 11 2026
May 4 2026
This bug was fixed by T7112.
May 1 2026
Apr 30 2026
Apr 28 2026
Apr 27 2026
Apr 21 2026
Apr 14 2026
Apr 10 2026
Apr 9 2026
Apr 7 2026
Apr 6 2026
Apr 3 2026
Apr 2 2026
Apr 1 2026
Mar 30 2026
Mar 26 2026
Mar 25 2026
Mar 24 2026
Pull requests:
Mar 18 2026
Mar 16 2026
Mar 13 2026
Mar 12 2026
Mar 10 2026
Pull requests: