A verify() step will be added to prevent certain configurations when a specific type of driver is used. In this case if the xen driver is used, and MTU is > 1500 and sg is not set, a ConfigError() will be raised.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Feb 19 2021
Feb 19 2021
c-po added a comment to T3342: On xen-netback interfaces must set "scattergather" offload before MTU>1500.
c-po changed the status of T3342: On xen-netback interfaces must set "scattergather" offload before MTU>1500 from Open to In progress.
Feb 18 2021
Feb 18 2021
If this package supports all existing setups and the GRE usecase I see no reason to not replace it. @basalblas PR is happily accepted.
c-po renamed T3238: Update Linux Kernel to v4.19.178 from Update Linux Kernel to v4.19.169 to Update Linux Kernel to v4.19.176.
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.98 / 5.10.16 to Update Linux Kernel to v5.4.99 / 5.10.17.
Feb 17 2021
Feb 17 2021
DHCPd shold be vonsistent for both v4 and v6 - running different daemons is simply bad.
Perfect, thanks
Feb 16 2021
Feb 16 2021
@mathiashedberg could you try and enable RPS set interfaces ethernet eth0 offload rps and see if this does any good on utilisation / drop rate? I had a similar issue with a PPPoE link which behaved super bad under preasure.
c-po closed T3310: BFD: migrate to get_config_dict() and FRR reload, a subtask of T2175: Rewriting all FRR processes allow for reloading and to XML/Python style, as Resolved.
@plett VyOS 1.4 now does an automatic fallback to the 1.3 behavior which used FRR 7.3 until we decide how to handle this, w.g. by adding a new CLI option which is added by a migration script to keep older systems running "as is" when upgrading.
Feb 15 2021
Feb 15 2021
Somehow this was lost in translation in my git repo....
Nackported to 1.3 equuleus
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.
Feb 14 2021
Feb 14 2021
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 Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T2848: bgp-add-path configuration options from Open 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 Open 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
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.
Nice idea - it should be generated by https://github.com/vyos/vyos-build/blob/current/scripts/make-version-file
c-po committed rVYOSONEX1a3118490a85: nat: T3307: fix destination nat generation (authored by varesa).