Draft PR re-opened following fix of regression with option 'recursive'; simplified logic and added optional args to get_config_defaults to mirror get_config_dict. The latter allows easy manipulation of defaults in cases where the automatic merge is not sufficient.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 5 2023
Jun 4 2023
Jun 3 2023
Jun 2 2023
There are no network or broadcast addresses in v6 like there are in v4. The first address (ex: 2a10:ffff:ffff::/64) is the Anycast address for "All Routers" on a subnet in v6 land.
Well, in an example like yours, using the network address as an IP is not really best practice even tho its works.
So, the validator forces the users to do it the right way, which is probably a good thing.
Validator doesn't allow setting network address to the interface
the same way you can't add 10.2.3.0/24 to interface
But natively it seems working
vyos@r14# sudo ip a add 10.5.0.0/24 dev eth0 [edit] vyos@r14# ping 10.5.0.0 PING 10.5.0.0 (10.5.0.0) 56(84) bytes of data. 64 bytes from 10.5.0.0: icmp_seq=1 ttl=64 time=0.062 ms ^C
This did solve it. I did not search thoroughly enough it seems.
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 ?
All of the modem specific settings appear to be done through the web GUI of the modem.
May 25 2023
I could have sworn it took quite a while for the wlb.out to be populated when testing earlier on. However as I´ve built out the config a bit more I am now only able to reproduce it a few seconds after reboot - so your theory holds. Let's close out the bug report for now and I´ll reopen if something changes down the line.
Virtual-ethernet interfaces veth implemented in T4825
For veth in "netns" it should be a separate task.
I can't reproduce it VyOS 1.4-rolling-202305250317
set load-balancing wan flush-connections set load-balancing wan interface-health eth0 failure-count '3' set load-balancing wan interface-health eth0 nexthop '192.168.122.1' set load-balancing wan interface-health eth0 success-count '5' set load-balancing wan interface-health eth0 test 1 target '1.1.1.1' set load-balancing wan interface-health eth0 test 2 target '8.8.8.8' set load-balancing wan interface-health eth2 failure-count '10' set load-balancing wan interface-health eth2 nexthop 'dhcp' set load-balancing wan interface-health eth2 success-count '10' set load-balancing wan interface-health eth2 test 1 target '1.1.1.1' set load-balancing wan interface-health eth2 test 2 target '8.8.8.8' set load-balancing wan rule 1 failover set load-balancing wan rule 1 inbound-interface 'eth1.10' set load-balancing wan rule 1 interface eth0 weight '100' set load-balancing wan rule 1 interface eth2 weight '10'