User Details
- User Since
- Oct 31 2021, 3:16 PM (159 w, 5 d)
May 28 2024
@Viacheslav here you go:
May 13 2024
Dec 28 2022
@higebu that box works well!
Dec 27 2022
Any update on this PR merge? :(
Any update on the PR merge? thanks
Dec 9 2022
According to this https://forum.vyos.io/t/vagrant-auth-failure-on-new-vagrant-images/9871/2
This issue is due to T874.
My understanding is that is not changeable, so my proposal is to add the "vagrant insecure key" for the vyos user during the vagrant box creation.
Nov 24 2022
Nov 7 2022
Nov 5 2022
Note: this requires https://phabricator.vyos.net/T4800 to be completed.
Well, after a better code reading, the var should be named chroot_includes_dir instead of includes_chroot_dir.
Aug 26 2022
Aug 22 2022
I think I found the "problematic" commit.
https://github.com/vyos/vyos-1x/commit/41477cc85208507be55f8db4e412ad78eae764eb#diff-8e6f3b9122c8406707eb59334978290d083995acf7de0323111d4eed1656693dL311
With an older version:
vagrant@s1:~$ sudo bridge vlan port vlan-id eth1 1000 PVID Egress Untagged eth2 1001 PVID Egress Untagged br0 1 PVID Egress Untagged 1000 1001 vagrant@s1:~$ show version
Aug 4 2022
From the strongswan 5.9.6 changelog:
Actively initiating duplicate CHILD_SAs within the same IKE_SA is now largely prevented. This can happen if trap policies are installed and an IKE_SA with its CHILD_SAs is reestablished (e.g. with break-before-make reauthentication or dpd_action=restart). This does not prevent duplicates if they are initiated by the two peers concurrently.
Jun 27 2022
Hi,
I think this is a BUG, not a feature.
If I enable mpls on an interface, then the proper sysctl flags must be applied and be persistent.
Apr 14 2022
Relevant configuration on one PE router:
Nov 8 2021
When I manually add the "vrf red" with vtysh, then the frr config is like the one you reported.
Nov 2 2021
Additional note: this, of course, breaks the 'red' vrf connectivity.
If I manually add, using vtysh, the
vrf red vni 3000
everything on the 'red' vrf works fine.