This did solve it. I did not search thoroughly enough it seems.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 2 2023
Jun 1 2023
this issues was resolved on https://vyos.dev/T5127. It happens when FRR tries to calculate the auto-rd per vrf . it can be solved by using router-id on each vrf or interface dummy in the VRFs ,
Chiming in here as a 'me too', on vyos-1.4-rolling-202305300317
May 31 2023
I checked 6 routers, 2 showed the issue. No idea what the impact is. All of them running 1.3.2.
Maybe this [a-zA-Z_](?:[a-zA-Z0-9_\-\.]{0,}[a-zA-Z0-9_\-])?
I have the correct host-name after reboot
vyos@r14:~$ vyos@r14:~$ vtysh -c "show run" | match host hostname r14 vyos@r14:~$ vyos@r14:~$ vyos@r14:~$ show ver Version: VyOS 1.4-rolling-202305260317 Release train: current
May 30 2023
May 29 2023
@zsdc I built the image now, and it works as expected. The issue looks resolved. Thank you.
@dutty can you try to build an image again and check now?
May 28 2023
PR for VyOS 1.3 LTS branch https://github.com/vyos/vyos-1x/pull/2019
Yes, T4737 looks the same.
In T5243#149267, @Viacheslav wrote:Maybe the related bug described in T4737
Could you show a version of FRR?show version all | match frr
Maybe the related bug described in T4737
Could you show a version of FRR?
show version all | match frr
May 27 2023
In T970#149229, @olivier.hault wrote:How far are we in the testing of this important feature ?
May 26 2023
Added extension and example for test_vif_8021q_mtu_limits.
One fix added; I'm looking at an extension for the case of test_vif_8021q_mtu_limits, as mentioned in the comment in base_interfaces_test.py.
Let me cherry-pick these and commit all at one
I discovered that conntrack are enabled by default in two files:
Example implementation:
https://github.com/vyos/vyos-1x/compare/current...jestabro:cli-defined
How far are we in the testing of this important feature ?