VyOS 1.3 based on Debian 10 Buster
Details
Details
Description
Today
Today
Yesterday
Yesterday
Fri, Jan 27
Fri, Jan 27
zsdc moved T4954: DNS cannot be configured via Network-Config v1 received from ConfigDrive / Cloud-Init from Need Triage to Backport Candidates on the VyOS 1.4 Sagitta board.
Backport PR https://github.com/vyos/vyos-cloud-init/pull/60
zsdc changed the status of T4954: DNS cannot be configured via Network-Config v1 received from ConfigDrive / Cloud-Init from Open to Backport pending.
Fix for 1.4: https://github.com/vyos/vyos-cloud-init/pull/59
It must be backported to 1.3 now.
Wed, Jan 25
Wed, Jan 25
Sun, Jan 15
Sun, Jan 15
Viacheslav changed the status of T4927: Need to change restart to reload-or-restart in Webproxy module from In progress to Needs testing.
Wed, Jan 11
Wed, Jan 11
a.apostoliuk changed the status of T4927: Need to change restart to reload-or-restart in Webproxy module from Open to In progress.
Tue, Jan 10
Tue, Jan 10
Mon, Jan 9
Mon, Jan 9
Viacheslav changed the status of T4844: Incorrect permissions of the safeguard DB directory from In progress to Needs testing.
Thu, Jan 5
Thu, Jan 5
Viacheslav changed the status of T4895: Tag nodes are overwritten when configured by Cloud-Init from User-Data from Backport pending to Needs testing.
Tue, Jan 3
Tue, Jan 3
zsdc added a comment to T4895: Tag nodes are overwritten when configured by Cloud-Init from User-Data.
Backport PR: https://github.com/vyos/vyos-cloud-init/pull/57
Dec 27 2022
Dec 27 2022
vfreex added a comment to T4896: ospfv3: Fix broken not-advertise option.
Dec 26 2022
Dec 26 2022
zsdc changed the status of T4895: Tag nodes are overwritten when configured by Cloud-Init from User-Data from Open to Backport pending.
For 1.4 resolved in the https://github.com/vyos/vyos-cloud-init/commit/d385e3655e9eed77397136f5e27325a93719332d
Waiting several days for tests before doing a backport.
Dec 25 2022
Dec 25 2022
Dec 13 2022
Dec 13 2022
Viacheslav changed the status of T4874: Add Warning message to Equuleus from In progress to Needs testing.
Dec 10 2022
Dec 10 2022
Dec 9 2022
Dec 9 2022
zsdc changed the status of T4869: A network with `/32` or `/128` mask cannot be removed from a network-group from Open to In progress.
PR with fix is here: https://github.com/vyos/vyatta-cfg-firewall/pull/35
Dec 6 2022
Dec 6 2022
a.apostoliuk changed the status of T4862: webproxy domain-block does not work from Open to In progress.
Dec 1 2022
Dec 1 2022
Nov 30 2022
Nov 30 2022
Nov 28 2022
Nov 28 2022
a.apostoliuk changed the status of T4844: Incorrect permissions of the safeguard DB directory from Open to In progress.
Nov 25 2022
Nov 25 2022
marc_s added a comment to T4776: NVME storage is not detected properly during installation.
pasik added a comment to T4776: NVME storage is not detected properly during installation.
@marc_s Would you be able to open a PR against 1.3 ?
Nov 23 2022
Nov 23 2022
Viacheslav changed the subtype of T4793: Create warning message about disable-route-autoinstall when ipsec vti is used from "Task" to "Feature Request".
Nov 22 2022
Nov 22 2022
Viacheslav changed the status of T4793: Create warning message about disable-route-autoinstall when ipsec vti is used from In progress to Needs testing.
Alfa80 added a comment to T4774: Disallow duplicate pubkey on peers of a wireguard interface.
@trae32566 My apologies for the inconveniences. You are right. The criteria for triggering this action shall be narrowed down further.
It would be necessary to issue the warning if and only if such colliding peers also specify the exact same remote endpoint addresses (with empty endpoints also being accounted as to be the same).
In other words, we need to identify incoming peers and apply the rule only to them, not the outgoing ones which already have specific remote endpoint addresses statically defined.
trae32566 added a comment to T4774: Disallow duplicate pubkey on peers of a wireguard interface.
This breaks a perfectly valid use case which I utilize regularly: using IPv4 + IPv6 peers with the same public key. Why would I want to create multiple keys for the exact same devices going over IPv4 and IPv6? If you want to include a warning, fine, but don't limit functionality based on someone's interpretation of how something will be used. I understand where this came from, but any time you limit functionality, you limit your users. As Donald Knuth once said:
Unix was not designed to stop you from doing stupid things, because that would also stop you from doing clever things.
Nov 17 2022
Nov 17 2022
pasik added a comment to T4776: NVME storage is not detected properly during installation.
@marc_s thanks for testing !
Nov 16 2022
Nov 16 2022
Nov 14 2022
Nov 14 2022
Nov 10 2022
Nov 10 2022
sajiby3k updated the task description for T4811: Webproxy bypassing cli command missing.
Nov 8 2022
Nov 8 2022
marc_s added a comment to T4776: NVME storage is not detected properly during installation.
TLDR; confirmed fixed for 1.3, please backport.
Nov 3 2022
Nov 3 2022
a.apostoliuk changed the status of T4793: Create warning message about disable-route-autoinstall when ipsec vti is used from Open to In progress.