Running into this as well on: 1.4-rolling-202307260317
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Aug 6 2023
Aug 6 2023
jestabro added a parent task for T5443: Add merge_defaults as Config method: T5319: Remove remaining workarounds for incorrect defaults.
Lets keep this one open for some more time and see if the issue is resolved or not.
Viacheslav changed the status of T5266: QoS- HTB error when match with a dscp parameter for queue-type 'priority', a subtask of T5048: QoS doesn't work correctly root task, from Open to Needs testing.
Viacheslav changed the status of T5266: QoS- HTB error when match with a dscp parameter for queue-type 'priority' from Open to Needs testing.
c-po changed the status of T5445: dyndns: add possibility to specify update interval (timeout) from Open to In progress.
jestabro added a parent task for T5443: Add merge_defaults as Config method: T5228: Simplify get_config_dict and add argument with_defaults.
Aug 5 2023
Aug 5 2023
Apachez added a comment to T5417: nft -o (optimizing ruleset) fails with error: "internal:0:0-0: Error: Could not process rule: File exists" .
There is a bugzilla opened for this issue: https://bugzilla.netfilter.org/show_bug.cgi?id=1697
I can confirm that updating blacklist now is vrf aware and functional:
PR created: https://github.com/vyos/vyos-1x/pull/2135
PR created: https://github.com/vyos/vyos-1x/pull/2135
Added task https://vyos.dev/T5440 to fix the issue of preconfig-script doesnt show up in /config/scripts after system upgrade (add system image).
The reason *I* use chrony with my linux qemu guests, is that it supports using the kvm_ptp to get the kvm hypervisor's time as sync source, and I then don't need the VM to chat with NTP servers.
c-po moved T5428: dhcp: client renewal fails when running inside VRF from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.4) board.
c-po edited projects for T5428: dhcp: client renewal fails when running inside VRF, added: VyOS 1.3 Equuleus (1.3.4); removed VyOS 1.3 Equuleus (1.3.3).
c-po moved T3424: PPPoE IA-PD doesn't work in VRF from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.4) board.
c-po edited projects for T3424: PPPoE IA-PD doesn't work in VRF, added: VyOS 1.3 Equuleus (1.3.4); removed VyOS 1.3 Equuleus (1.3.3).
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2134
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2134
c-po moved T3424: PPPoE IA-PD doesn't work in VRF from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
c-po changed the status of T3424: PPPoE IA-PD doesn't work in VRF from In progress to Needs testing.
Fixed in the latest rolling release
I need some help with this one.
It seems happy for now:
[email protected]:~$ systemctl list-timers NEXT LEFT LAST PASSED UNIT ACTIVATES Sat 2023-08-05 21:00:00 CEST 38min left Sat 2023-08-05 20:00:01 CEST 21min ago logrotate.timer logrotate.service
Viacheslav renamed T5266: QoS- HTB error when match with a dscp parameter for queue-type 'priority' from QoS- HTB error when match with a dscp parameter to QoS- HTB error when match with a dscp parameter for queue-type 'priority'.
Bug present in 1.3.3 as well
c-po moved T5428: dhcp: client renewal fails when running inside VRF from Open to Finished on the VyOS 1.4 Sagitta board.
c-po closed T5428: dhcp: client renewal fails when running inside VRF, a subtask of T3424: PPPoE IA-PD doesn't work in VRF, as Unknown Status.
Also watchfrr was disabled some time ago as FRR process handling was moved to systemd.
FRR mgmtd can not be disabled.
Aug 4 2023
Aug 4 2023
c-po added a parent task for T5428: dhcp: client renewal fails when running inside VRF: T3424: PPPoE IA-PD doesn't work in VRF.
The VRF error applies to DHCPv6, too
c-po changed the status of T5428: dhcp: client renewal fails when running inside VRF from In progress to Needs testing.
Apachez added a comment to T5439: Upgrade to FRR version 9.0 added new daemons which must be adjusted.
Note, if mgmtd is of no use in VyOS then the preferred is to have it disabled all together (after updating daemons.tmpl in case it gets enabled in future).
PR created: https://github.com/vyos/vyos-1x/pull/2132
Could be added the same way https://github.com/vyos/vyos-1x/blob/8f161eaae78769e5a1d573e43f00a0f439aadc28/debian/vyos-1x.postinst#L126-L139
Aug 3 2023
Aug 3 2023
Viacheslav moved T5154: Chrony - multiple listen addresses from Open to Finished on the VyOS 1.4 Sagitta board.
jestabro edited parent tasks for T5435: Expose utility function for default values at path, added: T5434: Replace remaining calls of vyos.xml library; removed: T5218: Revise vyos xml lib for bug fixes and extensions.
Apachez added a comment to T5424: Routes vanishes when using FRR with ECMP and one of the ECMP paths is no longer available.
Note also that 1.4 rolling as of today (3rd aug) uses FRR 9.0 (previously I think 8.5.4 were used or something like that).
aserkin added a comment to T5424: Routes vanishes when using FRR with ECMP and one of the ECMP paths is no longer available.
Yes, i did that as option A yesterday. And rebooted. Then removed "zebra nexthop-group keep 1" and play a bit with interfaces up/down until kernel routes vanished. Then i put "zebra nexthop-group keep 1" back and rebooted again.
Will try option B then.
Meanwhile it appeared possible to fix "Route install failed" errors. I turned on debug zebra kernel, found the nhg_id which caused route install error and created it manually using nh1/nh2 provided by vtysh -c "show nexthop-group rib <nhg_id>". Just as it is described in the original thread regarding ipv6 routes.
Apachez added a comment to T5424: Routes vanishes when using FRR with ECMP and one of the ECMP paths is no longer available.
Note that you had an "s" too much in your command.
Apachez added a comment to T5431: Services not enabled or configured are started anyway within frr-family.
Found that the defaults in daemons-file are set by VyOS in /usr/share/vyos/templates/frr/daemons.frr.tmpl
aserkin added a comment to T5424: Routes vanishes when using FRR with ECMP and one of the ECMP paths is no longer available.
There is still some problem with the workaround proposed. It seems not fully working when applied on the running system with active BGP sessions. At least i still see the next hop groups in the kernel which has only one next hop after our last tests:
c-po changed the status of T5428: dhcp: client renewal fails when running inside VRF from Open to In progress.
Hi
I would like to see last delay sessions be minimum allowed integer be 0 not 1 to 999999
Aug 2 2023
Aug 2 2023
c-po edited a custom field on T5429: vxlan: source-interface is not honored and throws config error.