Nackported to 1.3 equuleus
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Feb 15 2021
Feb 15 2021
Unknown Object (User) claimed T3312: SolarFlare NICs support.
Unknown Object (User) changed the status of T3312: SolarFlare NICs support from Open to In progress.
Yes, I very much like this, and is what I am imaging with 3., above.
With this new information I see little to none reason to keep the key_mangling() workaround. If we manage to transform all nodes into "proper" syntax we can one day drop it.
PR https://github.com/vyos/vyatta-cfg-firewall/pull/20 is still pending to clean up the following log entry:
@c-po this is an excellent idea, and a useful reference for the bracket notation; this will need a bit of design of how best to slice the problem:
- keeping key_mangling but excluding on tag nodes
- removing key_mangling completely
- removing on a case by case basis with the existing argument to get_config_dict()
XML for policy access|access6|prefix|prefix6|community list
Unknown Object (User) created T3312: SolarFlare NICs support.
trae32566 updated the task description for T3311: BGP Error: Remote AS must be set for neighbor or peer-group.
trae32566 updated the task description for T3311: BGP Error: Remote AS must be set for neighbor or peer-group.
Feb 14 2021
Feb 14 2021
In the new xml/py rewrite, do they disapear if you rerun the bgp configurator script? Eg. Can we execute frr-reload twice as a workaround?
This actually feels like an FRR bug as this still occurs with the new XML/Python rewrite
c-po closed T2848: bgp-add-path configuration options, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Resolved.
c-po moved T2844: BGP conf_mode errors disable-send-community from Need Triage to Finished on the VyOS 1.4 Sagitta board.
c-po moved T2848: bgp-add-path configuration options from Need Triage to Finished on the VyOS 1.4 Sagitta board.
c-po reopened T2848: bgp-add-path configuration options, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as In progress.
c-po closed T2848: bgp-add-path configuration options, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Invalid.
This is fixed in 1.4 as proper input validation happens.
c-po added a project to T1941: Config mismatch with FRR on misconfiguration of V6 peer: VyOS 1.4 Sagitta.
c-po added a project to T2315: Ability to have right address-family for BGP peers.: VyOS 1.4 Sagitta.
c-po edited projects for T2848: bgp-add-path configuration options, added: VyOS 1.4 Sagitta; removed VyOS 1.3 Equuleus.
Currently this requires BFD support to be added to frr-reload
Implemented/fixed for VyOS 1.4
c-po moved T2845: BGP conf_mode unable to delete configuration with peer-group from Need Triage to Finished on the VyOS 1.4 Sagitta board.
Issue no longer persists in VyOS 1.4. Tested using: 1.4-rolling-20210214
c-po added a project to T2845: BGP conf_mode unable to delete configuration with peer-group: VyOS 1.4 Sagitta.
c-po closed T3308: BGP: add gracefull shutdown support, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Resolved.
c-po closed T1875: Add the ability to use network address as BGP neighbor (bgp listen range), a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Resolved.
c-po closed T1875: Add the ability to use network address as BGP neighbor (bgp listen range) as Resolved.
Please re-test with latest current rolling release. Reverted back for FRR 7.5 and that bug should have been fixed in there.
Feb 13 2021
Feb 13 2021
zsdc changed the status of T3309: dhclient started by Cloud-init stays alive forever from Open to Needs testing.
c-po closed T2387: Create XML scheme for [conf_mode] BGP , a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Resolved.
c-po closed T2174: Rewrite protocol BGP to new XML/Python style, a subtask of T2175: Rewriting all FRR processes allow for reloading and to XML/Python style, as Resolved.
c-po closed T1315: Allow BGP to use address-family l2vpn evpn, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Resolved.
c-po changed the status of T1315: Allow BGP to use address-family l2vpn evpn, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, from Open to Needs testing.
c-po changed the status of T1315: Allow BGP to use address-family l2vpn evpn from Open to Needs testing.
c-po changed the status of T3308: BGP: add gracefull shutdown support, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, from Open to In progress.
I am suggesting switching to https://github.com/vyos/vyos-vm-images for everything, except ISO images. This will solve the problem automatically. It is already able to create images for QEMU, VMware, Hyper-V, GCE, AWS, OpenStack, Oracle, Packet, and more not mentioned in the https://github.com/vyos/vyos-build. The only what I have not tried yet is Azure.
Setting Ethernet interfaces addresses, routes, and name servers are supported in both versions now. Advanced features like bonding, bridges, VLANs could be added later on-demand.
Nice idea - it should be generated by https://github.com/vyos/vyos-build/blob/current/scripts/make-version-file
This was resolved via dhclient hooks - there is a protection mechanism now, which allows deleting only routes with tag 210 that set by hooks to all DHCP routes.
zsdc closed T723: Add support for first boot or installation time saved config modification as Resolved.
zsdc closed T2309: Wrong host-name value breaks the whole configuration in images with Cloud-init as Resolved.
The config module without this problem is available in the crux, should be released in the 1.2.7 version.
zsdc closed T2703: VMWare OVA won't deploy an ed25519 key, a subtask of T2726: Allow to use all supported SSH key types in Cloud-init, as Resolved.
The config module backported to the crux, should be available with 1.2.7 release.
zsdc moved T2310: vyos-cloud-init use global config to configure pass and ssh login from In Progress to Finished on the VyOS 1.2 Crux (VyOS 1.2.7) board.
Backported to the crux branch, should be released with 1.2.7.
Feb 12 2021
Feb 12 2021
Unknown Object (User) triaged T3307: address prefix destination NAT fails to render nftables rules / commit as Normal priority.
Unknown Object (User) changed the status of T3307: address prefix destination NAT fails to render nftables rules / commit from Open to Needs testing.
varesa added a comment to T3307: address prefix destination NAT fails to render nftables rules / commit.
Created PR: https://github.com/vyos/vyos-1x/pull/731
varesa added a comment to T3307: address prefix destination NAT fails to render nftables rules / commit.
Tested with:
varesa added a comment to T3307: address prefix destination NAT fails to render nftables rules / commit.
Possible fix, pending testing: https://github.com/varesa/vyos-1x/commit/4a0504a96cf0f3078e964ed201f196fb55172e00
c-po changed the status of T3182: Main blocker Task for FRR 7.4/7.5 series update from Open to In progress.
I *think* that there was a fix that happened on a task somewhere by someone in the underlying operating system that happened to fix this problem, but I for the life of me don't know what/where it would be. I'll have to ask around on it as I think there was changes on it 100% certain. The reason is is because I *saw* this problem too on a very old install too but it went away very quickly and I made no changes to fix it.
Viacheslav changed the subtype of T3304: No way to use ipv4 address as next-hop in route-map from "Feature Request" to "Bug".
Viacheslav closed T3301: Wrong format and valueHelp for policy as-path-list regex, a subtask of T2425: Rewrite all policy zebra filters to XML/Python style, as Resolved.
@c-po I would say that it would be better whether to report the problem upstream
I have updated from an older version.