PR https://github.com/vyos/vyos-1x/pull/3490

@jestabro It was a report from the user; unfortunately, I do not have more details.

I remember there was an ancient bug where the commit-archive rewrite did not come with a timeout. As routing might not have been converged during boot, that could explain the lock.

Naive attempts to reproduce on 1.3.3 are not successful, yet (Vmware; KVM), but will continue to investigate; any other information is welcome @Viacheslav, should you recall ...

https://github.com/vyos/vyos-1x/pull/3489

@jestabro This was the first of some issues I reported with migration to 1.4.0. The report is (with apologies) a bit vague as much did not work and it took more effort to identify the causes. It turned out to be a combination of things, of which T6131 was only part.

@matthewr Were all issues of this task resolved by the above discussions and the fix for T6131 ?

@jestabro could it be that the validator needs an update to allow special characters in the user/password field?
https://github.com/vyos/vyos-utils/blob/0d57cc9a266fe8d6fc87df5a769f42b4a45c7221/src/url.ml

It seems to work basically

Can you manually edit the node and re-check if it will work for acme

sudo nano -c /opt/vyatta/share/vyatta-cfg/templates/pki/certificate/node.tag/acme/listen-address/node.def

replace:

type: txt
help: Local IPv4 addresses to listen on
val_help: ipv4; IPv4 address to listen for incoming connections
allowed: sh -c "${vyos_completion_dir}/list_local_ips.sh --ipv4"
syntax:expression: exec "${vyos_libexec_dir}/validate-value  --exec \"${vyos_validators_dir}/ipv4-address \"  --value \'$VAR(@)\'"; "Invalid value"

to

type: txt
help: Local IPv4 addresses to listen on
val_help: ipv4; IPv4 address to listen for incoming connections

@Alfa80 this is actually the verbatim output of sudo wg show <interface>. I agree that it would sometimes be more intuitive to see the peers name

@Giggum sure, much appreciated

PR: https://github.com/vyos/vyos-1x/pull/3487

Feature available in 1.3.6 1.4.0-epa3 and 1.5

Using DHCPv6-PD on 1.5 and 1.4-epa3 and confirmed working

I can't test it in 1.3. I've tried to build the latest 1.3 from repository, but it looks like the build process is broken and does not allow contributors to build following the documentation guide any more.
That's sad :(

@jestabro assigning to you but feel free to pass it to another team member

@dmbaturin can you add space check into the upgrade scripts

PR https://github.com/vyos/vyos-1x/pull/3483

set nat cgnat pool external ext-01 external-port-range '40000-60000'
set nat cgnat pool external ext-01 per-user-limit port '5000'
set nat cgnat pool external ext-01 range 192.0.2.1-192.0.2.2
set nat cgnat pool external ext-01 range 192.0.2.11/32

This is a known issue as explained in detail in T4628. You're best choice is to remove the whitespace prior to upgrading. Thanks for reporting this anyways!

Yeah, my bad!