This expected behavior due to change from ntpd to chrony
@rob needs to update documentation for 1.4 to reflect changes

Awesome. Good luck.

yes, @aidan-gibson, there are no plans to entertain shit-talkers with a single task and no contributions

you are not from community @simplysoft
it's time to depart you from here

thanks for your effort in any case @florin
"A journey of a thousand miles begins with a single step"

Implementation never worked

Created a poll for maintainers on this topic, and we will go with the decision made.

In T5835#187936, @simplysoft wrote:

Yes, that is exactly the point. Glad you did not suggest to remove the NAT capability of vyos because it could be used to bypass security or is not appropriate for an "enterprise"

In T5835#187933, @simplysoft wrote:

A firewall is doing exactly this all the time when using NAT, autonomously opening ports via call from internal networks (aka internal originated traffic) to allow responses to reach the originator. Enterprises might have some strict outbound rules. For UPnP is exactly the same, an enterprise would have strict rules which services are allowed to open ports.

Not if it's not configured to do so.

I fail to comprehend how a firewall that autonomously opens ports via calls from internal networks is appropriate for an enterprise.
Indeed there are some use cases but this functionality can be used by malicious code and allow bypass security configuration that is enforced otherwise

Does it work now?

No doubt that there are other use cases.
since 1.2 LTS, we received zero requests from customers about adding UPnP, hence, don't see any value in it

@aidan-gibson It's never worked, and demand is slim to none
main use case is games typically, which is not in priority for us

Why just no sign repositories?