This can be close. The commit is working again after upgrading to the latest rolling
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Apr 11 2021
Apr 11 2021
Submitted following PR:
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.110 / 5.10.28 to Update Linux Kernel to v5.4.111 / 5.10.29.
Apr 10 2021
Apr 10 2021
c-po changed the status of T3328: Bgp not possible to delete bgp route-map from Open to In progress.
@dtoux could you provide us with a mocked up output what you would like to see?
c-po moved T3454: dhclient reject option from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
c-po moved T2108: Use minisign/signify instead of GPG for release signing from Open to Backlog on the VyOS 1.4 Sagitta board.
frr-reload output: 184 % Cannot have local-as same as BGP AS number
c-po changed the status of T3460: bgp, Configuration FRR failed while commiting code from Open to In progress.
c-po renamed T1711: BGP - migrate from tagNode to node (remove ASN from tagNode) from Bgp set local-AS number one time to BGP - migrate from tagNode to node (remove ASN from tagNode).
Apr 9 2021
Apr 9 2021
scj643 added a comment to T3376: Setting ipv6 address autoconf causes all interfaces besides the target to lose their IP.
This issue seems to have gone away or I haven't noticed it recently.
carl.byington added a comment to T3376: Setting ipv6 address autoconf causes all interfaces besides the target to lose their IP.
I cannot reproduce this on VyOS 1.4-rolling-202104062128. Instead, on that version, ipv6 address autoconf commits, but the interface never picks up a v6 address.
Apr 8 2021
Apr 8 2021
c-po changed the status of T3456: firewall: rules that should be deleted seem to be still in use from Unknown Status to Resolved.
c-po moved T3456: firewall: rules that should be deleted seem to be still in use from Backlog to Finished on the VyOS 1.2 Crux (VyOS 1.2.8) board.
c-po changed the status of T3463: Prevent IPv4 Route exchange with IPv6 neighbors from Open to In progress.
Looks like that is actually working.
Oops, I did not see that. Thanks.
I modified bgp.frr.tmpl, but systemctl restart vyos-configd did not seem to do anything. Rebooting the router produces the correct config:
c-po updated the task description for T3464: OSPF: route-map names containing a hypen are not "found".
@linuxludo thanks for the heads-up - should be fixed in the next bugfix version of 5.10 then which I regularely update VyOS to. See T3318
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.109 / 5.10.27 to Update Linux Kernel to v5.4.110 / 5.10.28.
We probably should move the following statement https://github.com/vyos/vyos-1x/blob/current/data/templates/frr/bgp.frr.tmpl#L362-L364
Just for your information.
The patch was added to kernel 5.4, 5.10 and 5.11.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/
c-po moved T3464: OSPF: route-map names containing a hypen are not "found" from Open to In Progress on the VyOS 1.4 Sagitta board.
c-po changed the status of T3464: OSPF: route-map names containing a hypen are not "found" from Open to In progress.
c-po updated the task description for T3464: OSPF: route-map names containing a hypen are not "found".
If you add neighbor/commit and after that commit adding "set protocols bgp parameters default no-ipv4-unicast" it can not be accepted. Because neighbor was added before this command.
Re-create neighbor and commit. And check again.
When on VyOS 1.4 please use the show bgp ipv6 command as exposed by FRR. The show ip bgp command is only kept as not all options from show ip bgp are exposed in FRR under the show bgp ipv4 tree.
Apr 7 2021
Apr 7 2021
Unknown Object (User) created T3461: OpenConnect Server redundancy check.
You can't/don't need to set local-as for neighbor [ if neighbor local as == your global asn ]
Can you send a code error?
Apr 6 2021
Apr 6 2021
Apr 5 2021
Apr 5 2021
c-po moved T3456: firewall: rules that should be deleted seem to be still in use from Needs Triage to Backlog on the VyOS 1.2 Crux (VyOS 1.2.8) board.
c-po moved T3456: firewall: rules that should be deleted seem to be still in use from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3456: firewall: rules that should be deleted seem to be still in use from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po edited projects for T3456: firewall: rules that should be deleted seem to be still in use, added: VyOS 1.2 Crux (VyOS 1.2.8); removed VyOS 1.2 Crux.
c-po changed the status of T3418: BGP: system wide known interface can not be used as neighbor from In progress to Needs testing.
I wonder if this used to work in the past?
Viacheslav changed the status of T1894: FRR config not loaded after daemons segfault or restart, a subtask of T3217: Save FRR configuration on each commit, from Open to Needs testing.
Viacheslav changed the status of T1894: FRR config not loaded after daemons segfault or restart from Open to Needs testing.
Turns out this is not a VyOS limitation but is a Linux Kernel/iproute2 limitation.
Viacheslav added a project to T1894: FRR config not loaded after daemons segfault or restart: VyOS 1.4 Sagitta.
c-po changed the status of T3456: firewall: rules that should be deleted seem to be still in use from Resolved to Unknown Status.
Restricted Repository Identity closed T3456: firewall: rules that should be deleted seem to be still in use as Resolved by committing Restricted Diffusion Commit.
This bug also persists in VyOS 1.2.7
Apr 4 2021
Apr 4 2021
Viacheslav added a comment to T3456: firewall: rules that should be deleted seem to be still in use.
The same with "policy" /usr/libexec/vyos/tests/config/dialup-router-medium-vpn
Viacheslav added a project to T1097: Make firewall groups work everywhere that's appropropriate: VyOS 1.4 Sagitta.
Viacheslav added a parent task for T3286: Switch the firewall from iptables to nftables: T2199: Rewrite firewall in new XML/Python style.
Viacheslav added a parent task for T1292: Issues while deleting all rules from a firewall: T2199: Rewrite firewall in new XML/Python style.
Viacheslav added a comment to T3456: firewall: rules that should be deleted seem to be still in use.
To reproduce it add firewall and attach it to interface
Usually on delete, the firewall should be detached from the interface first as the logic should go from the highest priority to the lowest one.
Viacheslav added a comment to T3456: firewall: rules that should be deleted seem to be still in use.
It is a priority for configurations
When the system load, the firewall should have configuration, and after configuration is applied to the interface.
So I think we can't delete it in one commit, it tried to delete the firewall before detaching the firewall from the interface.
It seems fixed for rolling release 1.4 because soft has been moved to FRR7.5.1
Of course it is not fixed for rolling release 1.3 (and as I understand won't be) due to FRR7.3.1
Apr 3 2021
Apr 3 2021
c-po updated the task description for T3456: firewall: rules that should be deleted seem to be still in use.
We can do some workaround for that level,
It seems that "call" doesn't react to env.
'VYATTA_EDIT_LEVEL': '/system/login'
Apr 2 2021
Apr 2 2021
c-po renamed T3455: system users can not be added in "edit" from edit mode breaks adding system users to system users can not be added in "edit".
Viacheslav changed the status of T3217: Save FRR configuration on each commit from Open to Needs testing.
This can be reproduced with the following config on 1.4
Apr 1 2021
Apr 1 2021
c-po moved T1080: L2tpv3 config delete on reboot/startup from Open to In Progress on the VyOS 1.4 Sagitta board.