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

Related to the list provided in https://vyos.dev/T5706 ?

It is more of a question for Jool.
Or you can use a range of required ports that aren't used by the system

I've tinkered with this a bit , but a problem I have is that I need multiple ip addresses on the outgoing interface(s). I understand that Jool takes all ports, so It's needed for everything to work properly.
On my own WAN interface, this is not a problem, I can just assign another ip from my ISP.

Removing 1.3 backport as it's not trivial. Implementation depends on python3-pyhump (not available and must be self build) and also on vyos.opmode framework which does not exist for 1.3 equuleus

Thank you for the report.

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2716

Fixed via podman update - upstream bug

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2704

@c-po apologies for the delay, missed this over the holidays.

Fix for 1.5 which will be backported
https://github.com/vyos/vyos-1x/pull/2703

This is actually caused by a missing priority value from ddclient. This is an ancient bug indeed.

Package added to 1.4

I haven't been able to test beyond 1.5-rolling-202312130023 due to T5863. I'll test it again once I'm able to update to the latest rolling. Thanks!

@trae32566 Are you experiencing this with the latest rolling version? 1.5-rolling-202312130023 was released mere hours before the fix was pushed. See also: T5774

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2699

Upstream error appears to be resolved in 4.7.2+ds1-2

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2698

completed

Yeah I'm having this issue as well:

trae@cr01a-vyos# commit
Archiving config...
  sftp://stor01a-rh9.int.trae32566.org/int/cr01a-vyos FAILED!

I'll leave this here T4541

Instead of "TEST-NET-X" and "TEST-IP-X" it could use "REPLACED-NET-X" and "REPLACED-IP-X" or such (where X defines the unique item thats being replaced).

In T3316#168877, @workingagain wrote:

after manual ownership change dhcp4.leases so the server can start causes this error:

ERROR [kea-dhcp4.dhcpsrv/4006.140169685592512] DHCPSRV_MEMFILE_LFC_LEASE_FILE_RENAME_FAIL failed to rename the current lease file /config/dhcp4.leases to /config/dhcp4.leases.1, reason: Permission denied

after manual ownership change dhcp4.leases so the server can start causes this error: