Backported to crux branch
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Sep 30 2021
Sep 30 2021
c-po changed the status of T3877: VRRP always enabled rfc3768-compatibility even when not specified from Open to Needs testing.
c-po updated the task description for T3877: VRRP always enabled rfc3768-compatibility even when not specified.
c-po moved T3874: D-Link Ethernet Interface not working. from Open to Finished on the VyOS 1.4 Sagitta board.
Sep 27 2021
Sep 27 2021
c-po moved T3858: Deleting OSPFv3 process yields: Unknown command: no router-id from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3858: Deleting OSPFv3 process yields: Unknown command: no router-id from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.9) board.
c-po closed T3863: nat66: commit fails/hangs on non existing interface, a subtask of T3853: nat66 rules gets deleted on reboot in 1.4-rolling-202109240217, as Resolved.
c-po committed rVYOSONEXc6d0227d96e4: openvpn: T690: Fix template for gateway and metric (authored by Viacheslav).
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.143 / 5.10.61 to Update Linux Kernel to v5.4.149 / 5.10.69.
Sep 26 2021
Sep 26 2021
c-po moved T3867: vxlan: multicast group address is not validated from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3867: vxlan: multicast group address is not validated from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3867: vxlan: multicast group address is not validated from Need Triage to 1.3.0-epa1 on the VyOS 1.3 Equuleus board.
c-po changed the status of T3867: vxlan: multicast group address is not validated from Open to In progress.
Related to T3863 and could also be a XML priority issue as NAT66 has a higher priority then e.g. the tunnel interface
c-po changed Is it a breaking change? from none to compatible on T3860: Error on pppoe, tunnel and wireguard interfaces for IPv6 EUI64 addresses.
c-po moved T3845: Add "show bgp nexthop" command from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3814: wireguard: commit error showing incorrect peer name from the configured name from Need Triage to 1.3.0-epa1 on the VyOS 1.3 Equuleus board.
c-po moved T3845: Add "show bgp nexthop" command from Need Triage to 1.3.0-epa1 on the VyOS 1.3 Equuleus board.
c-po moved T3841: dhcp-server: add ping-check option to CLI from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3847: keepalived/vrrp: migrate to get_config_dict() - cleanup from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3856: op command: " generate tech-support archive file" option is not working from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3860: Error on pppoe, tunnel and wireguard interfaces for IPv6 EUI64 addresses from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3860: Error on pppoe, tunnel and wireguard interfaces for IPv6 EUI64 addresses from Need Triage to 1.3.0-epa1 on the VyOS 1.3 Equuleus board.
c-po closed T3860: Error on pppoe, tunnel and wireguard interfaces for IPv6 EUI64 addresses as Resolved.
c-po changed the status of T3860: Error on pppoe, tunnel and wireguard interfaces for IPv6 EUI64 addresses from Open to In progress.
c-po updated the task description for T3860: Error on pppoe, tunnel and wireguard interfaces for IPv6 EUI64 addresses.
c-po moved T3859: Add "log-adjacency-changes" to ospfv3 process from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3859: Add "log-adjacency-changes" to ospfv3 process from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3859: Add "log-adjacency-changes" to ospfv3 process from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.9) board.
c-po moved T3857: reboot: send wall message to all users for information from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3857: reboot: send wall message to all users for information from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3857: reboot: send wall message to all users for information from Need Triage to 1.3.0-epa1 on the VyOS 1.3 Equuleus board.
c-po renamed T3862: "reboot at" command together with date does not work / weird error message on wrong input from "reboot at" command together with date does not work / weird error message to "reboot at" command together with date does not work / weird error message on wrong input.
c-po renamed T3862: "reboot at" command together with date does not work / weird error message on wrong input from "reboot at" command together with date does not work to "reboot at" command together with date does not work / weird error message.
c-po changed the status of T3861: PKI: changing certificates, keys, crls does not "regenerate" the on-disk certificates from Open to Confirmed.
c-po updated the task description for T3860: Error on pppoe, tunnel and wireguard interfaces for IPv6 EUI64 addresses.
c-po triaged T3860: Error on pppoe, tunnel and wireguard interfaces for IPv6 EUI64 addresses as Urgent! priority.
Sep 25 2021
Sep 25 2021
c-po added a comment to T3856: op command: " generate tech-support archive file" option is not working.
The command mentions that the file is saved to: /opt/vyatta/etc/config/support/file.vyos.tech-support-archive.2021-09-25-150643.tgz thus ls from the home directory will not reveal a file.
c-po changed Is it a breaking change? from validation to compatible on T3657: BGP neighbors ipv6 not able to establish with IPv6 link-local addresses.
c-po closed T3657: BGP neighbors ipv6 not able to establish with IPv6 link-local addresses as Resolved.
c-po added a comment to T3657: BGP neighbors ipv6 not able to establish with IPv6 link-local addresses.
The next rolling will also have support for the set protocols bgp neighbor fe80::202 interface source-interface 'eth1' CLI command
c-po added a comment to T3657: BGP neighbors ipv6 not able to establish with IPv6 link-local addresses.
Actually the VyOS syntax is a bit different - you do not need to establish a "relationship" with a link-local address - multiple links could indeed share the same link local address causing conflicts and non-uniqueness in the config.
Nat implementation for 1.3 has been reverted back to iptables - closing this.