upd. on vyos-1.4-rolling-202105051111 it's still there eve after reboot
Feed Search
May 13 2021
May 13 2021
c-po changed the status of T3544: DHCP server should validate configuration before applying it from Open to In progress.
acrane1 added a comment to T3527: Sometimes installing of static routes failes.
jack9603301 added a comment to T3532: Not possible to change ethertype after interface creation.
acrane1 added a comment to T3527: Sometimes installing of static routes failes.
Hi. Tried it (IPv4) on vyos-1.4-rolling-202103251004 in eve-ng
It reacts to set protocols static route 0.0.0.0/0 next-hop 195.7.0.102
After reboot it's still there
Screens added. It shows static route
jack9603301 added a comment to T3527: Sometimes installing of static routes failes.
Please use the following op-mode command to check:
c-po moved T3535: Rewrite vyatta-conntrack-sync in new XML and Python flavor from Open to In Progress on the VyOS 1.4 Sagitta board.
c-po moved T3540: Keepalived memory utilisation issue when constantly getting its state in JSON format from Open to Backlog on the VyOS 1.4 Sagitta board.
Viacheslav placed T3536: Unable to list all available routes up for grabs.
c-po changed the status of T3543: Support for setting lacp_rate on LACP bonded interfaces from Unknown Status to Resolved.
c-po moved T3543: Support for setting lacp_rate on LACP bonded interfaces from Backlog to Finished on the VyOS 1.3 Equuleus board.
c-po moved T3543: Support for setting lacp_rate on LACP bonded interfaces from Need Triage to Backlog on the VyOS 1.3 Equuleus board.
c-po moved T3543: Support for setting lacp_rate on LACP bonded interfaces from Backport Candidates to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3543: Support for setting lacp_rate on LACP bonded interfaces from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
c-po added a project to T3543: Support for setting lacp_rate on LACP bonded interfaces: VyOS 1.3 Equuleus.
c-po changed the status of T3543: Support for setting lacp_rate on LACP bonded interfaces from Resolved to Unknown Status.
Viacheslav added a comment to T905: The command show remote-config does not work for remote-platform openvpn.
Also bug for config "vyos" set mode clientset remote-port 12345
vyos@r6-roll# run show remote-config openvpn vtun0 remote-platform vyos NOTE: authentication options are deliberately left out, since we cannot know file paths on a remote system
Viacheslav added a comment to T3430: Cloud-init failing with “Unable to render networking” on VyOS 1.3.
@zsdc Can we close it?
c-po changed the status of T3543: Support for setting lacp_rate on LACP bonded interfaces from Open to In progress.
Viacheslav changed the status of T3540: Keepalived memory utilisation issue when constantly getting its state in JSON format from Open to Needs testing.
Viacheslav added a comment to T3540: Keepalived memory utilisation issue when constantly getting its state in JSON format.
@krox2 The next rolling release will be with keepalived 2.1.5. Can you check?
May 12 2021
May 12 2021
jestabro changed the status of T3542: udev net.rules not installed in image since may 2nd from Open to In progress.
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.117 / 5.10.35 to Update Linux Kernel to v5.4.118 / 5.10.36.
Viacheslav triaged T3532: Not possible to change ethertype after interface creation as Normal priority.
jestabro changed the status of T3302: Make vyos-configd relay stdout from scripts to the user's console from Unknown Status to Resolved.
Viacheslav added a comment to T3539: Typo in RPKI interface definition.
jestabro changed the status of T3426: add support for script arguments to vyos-configd from Resolved to Unknown Status.
jestabro changed the status of T3302: Make vyos-configd relay stdout from scripts to the user's console from Resolved to Unknown Status.
Viacheslav added a comment to T3541: Route Map large community set additive is missing.
set policy route-map ASxxx-CUS-IN6 rule 10 action 'permit' set policy route-map ASxxx-CUS-IN6 rule 10 set large-community '65:23:1 additive'
olofl added a comment to T3536: Unable to list all available routes.
Yes the point of "longer-prefixes" is to find smaller routes within a bigger netmask, so if you're leaving out prefix, it doesn't make sense.
Viacheslav added a comment to T3536: Unable to list all available routes.
May 11 2021
May 11 2021
c-po updated the task description for T3535: Rewrite vyatta-conntrack-sync in new XML and Python flavor.
c-po updated the task description for T3535: Rewrite vyatta-conntrack-sync in new XML and Python flavor.
jack9603301 added a comment to T3534: VLAN cannot be both `allowd-vlan` and `native-vlan`.
OK, it seems that this problem doesn't need any repair and will be closed
runar added a comment to T3534: VLAN cannot be both `allowd-vlan` and `native-vlan`.
I agree with @c-po, no warning is needed inbthis case
c-po edited a custom field on T3535: Rewrite vyatta-conntrack-sync in new XML and Python flavor.
c-po changed the status of T3535: Rewrite vyatta-conntrack-sync in new XML and Python flavor, a subtask of T3355: Remove all remaining legacy Vyatta code, from Open to In progress.
c-po changed the status of T3535: Rewrite vyatta-conntrack-sync in new XML and Python flavor from Open to In progress.
c-po added a comment to T3534: VLAN cannot be both `allowd-vlan` and `native-vlan`.
Why should a warning be printed?
jack9603301 renamed T3534: VLAN cannot be both `allowd-vlan` and `native-vlan` from VLAN cannot be both `allow-vlan` and `native-vlan` to VLAN cannot be both `allowd-vlan` and `native-vlan`.
jack9603301 added a comment to T3534: VLAN cannot be both `allowd-vlan` and `native-vlan`.
jack9603301 added a comment to T3534: VLAN cannot be both `allowd-vlan` and `native-vlan`.
@runar I just checked the current implementation. It seems that the current configuration is replacing "allowed VLAN" with "native VLAN", but there is no warning. I add a warning!
jack9603301 renamed T3534: VLAN cannot be both `allowd-vlan` and `native-vlan` from VLAN can be `allow-vlan` and `native-vlan` at the same time to VLAN cannot be both `allow-vlan` and `native-vlan`.
runar added a comment to T3534: VLAN cannot be both `allowd-vlan` and `native-vlan`.
Please make it so when both are present the native-vlan command is used.. do not throw an exception as this would make configuration much harder, as a eg. allow-vlan 1-4096, native-vlan 50 will be impossible to configure... Splitting up the allow-vlan and redoing it just to change native-vlan is work that the scripts should do in the backend and not have the user do it
jack9603301 changed the status of T3534: VLAN cannot be both `allowd-vlan` and `native-vlan` from Open to In progress.
May 10 2021
May 10 2021
francescocarzaniga added a comment to T3260: MAP-T/MAP-E for CPE and BR.
Here is an old implementation for Vyatta. Moreover Jool does MAP-T, offers a kernel module, and is being implemented into nftables.
linuxludo added a comment to T3374: IPv6 GRE Tunnel issues.
I tested vyos-1.3-rolling-202105011026-amd64.iso and everything is correct
Viacheslav closed T3528: Frr 7.5.1 uses 'seq' for community-lists, a subtask of T3182: Main blocker Task for FRR 7.4/7.5 series update, as Resolved.
May 9 2021
May 9 2021
c-po closed T2175: Rewriting all FRR processes allow for reloading and to XML/Python style, a subtask of T3355: Remove all remaining legacy Vyatta code, as Resolved.
c-po moved T3531: policy: prefix-list and route-map names do not allow underscores in names (FRR does) from Open to Finished on the VyOS 1.4 Sagitta board.
c-po renamed T3531: policy: prefix-list and route-map names do not allow underscores in names (FRR does) from vyos shell prefix-list and route-maps does not allow underscores in names, but vtysh does to policy: prefix-list and route-map names do not allow underscores in names (FRR does).
c-po added a comment to T3531: policy: prefix-list and route-map names do not allow underscores in names (FRR does).
Will take a look later today starting of with VyOS 1.4
c-po changed the status of T3531: policy: prefix-list and route-map names do not allow underscores in names (FRR does) from Open to In progress.
c-po moved T3529: vyos.frr class has no support for multi-line modify_section from Open to Backlog on the VyOS 1.4 Sagitta board.
c-po edited projects for T3479: route-maps containing "aggregator as" can not be deleted, added: VyOS 1.2 Crux (VyOS 1.2.8); removed VyOS 1.2 Crux.
c-po updated the task description for T3530: BGP peer-group can't contain a hyphen.
c-po updated the task description for T3530: BGP peer-group can't contain a hyphen.
May 8 2021
May 8 2021
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.115 / 5.10.33 to Update Linux Kernel to v5.4.117 / 5.10.35.
Viacheslav closed T3517: FRR 7.5 bfd behavior for 1.3, a subtask of T3182: Main blocker Task for FRR 7.4/7.5 series update, as Resolved.
May 7 2021
May 7 2021
Viacheslav updated subscribers of T3341: Wrong behavior of the "reset vpn ipsec-peer XXX tunnel XXX" command.
Which proper format do we need?
For example 2 tunnels:
peer-100.64.0.2-tunnel-0
peer-100.64.0.2-tunnel-1
carl.byington added a comment to T3522: policy based routing not working.
PBR works if we change the static route to: