In my case, the container is created and running using IPv4 only. The network it is in has a defined prefix for IPv4 and IPv6. Then, the only thing I try to do is add an IPv6 address to the container. The network it is connected to already has the IPv6 prefix defined. That is when it dies.

The mentioned file that missing is located upstream in https://github.com/miniupnp/miniupnp/tree/miniupnpd_2_3_1/miniupnpd/netfilter_nft/scripts
and the upstream configuration options that we think are missing to match vyos chains is https://github.com/miniupnp/miniupnp/blob/miniupnpd_2_3_1/miniupnpd/miniupnpd.conf#L77

Could you point out some documentation/examples on which scripts are missing?
It seems it has never been tested since @jack9603301 implemented it in task T3420. It seems he also didn't test it.

Adding a new container with both addresses and networks in one commit works fine.

set container name alp01 image 'alpine'
set container name alp01 network NET01 address '10.0.0.12'
set container name alp01 network NET01 address '2001:db8::12'
set container network NET01 prefix '10.0.0.0/24'
set container network NET01 prefix '2001:db8::/64'

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

/config/dhcp4.leases ownership seem to change when migrating to latest 1.5-rolling-202312171632

set service dhcp-server dynamic-dns-update
set service dhcp-server hostfile-update
set service dhcp-server shared-network-name LAN authoritative
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 default-router '192.168.1.1'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 domain-name 'home'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 name-server '192.168.1.1'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 range 0 start '192.168.1.120'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 range 0 stop '192.168.1.230'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 static-mapping ...
...

I also notice that ddclient has a similar problem.

ddclient[1710]: FAILED:   Unable to obtain information for 'pppoe0' -- missing ip or ifconfig command

This might be a problem that's specific to me. I don't know why every systemd start too early.

Indeed, the dhcp server wasn't working so I assume that kea doesn't start, my bad, it did start, but it failed to start, after failing for 5 attempts.

In T3316#167384, @sdev wrote:

In T3316#167382, @indrajitr wrote:

• with set service dhcp-server hostfile-update the file /etc/hosts doesn't get update with any entry from dhcp at all

Thanks, will investigate this.

@sdev, this will require adjusting on-dhcp-event.sh. I have a hacky local version that writes to /etc/hosts that partially works -- the $domain part is not picked up (which I suspect could be related to how kea-dhcp4.conf is generating the FQDN).

Do you want me to raise a draft PR for you to review?

By all means, thank you!

In T3316#167382, @indrajitr wrote:

• with set service dhcp-server hostfile-update the file /etc/hosts doesn't get update with any entry from dhcp at all

Thanks, will investigate this.

@sdev, this will require adjusting on-dhcp-event.sh. I have a hacky local version that writes to /etc/hosts that partially works -- the $domain part is not picked up (which I suspect could be related to how kea-dhcp4.conf is generating the FQDN).

Do you want me to raise a draft PR for you to review?

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

• with set service dhcp-server hostfile-update the file /etc/hosts doesn't get update with any entry from dhcp at all

Thanks, will investigate this.

@Zen3515

• dhcp server doesn't start automatically after reboot, and due to the next problem, I'm forced to use set service dhcp-server disable then delete service dhcp-server disable after each boot

Could not reproduce this:

Welcome to VyOS - vyos ttyS0
...
vyos@vyos:~$ ps aux | grep kea
_kea        1818  1.6  0.9  67384 20324 ?        Ssl  00:14   0:00 /usr/sbin/kea-dhcp4 -c /run/kea/kea-dhcp4.conf

Yes, if I remove the container, and then as root create the container using the exact same podman command that VyOS had used, but just add the --ip6 definition, then the container is created and responds on that ip.

Is it possible with native podman commands?

Try to delete MAC before cloning in /config/config.boot

Hello, I'd like to provide my quick feedback after testing the version 1.5-rolling-202312130023

Potentially relevant bug on debian's bug tracker

This has happened a few more times since last report.

some improvements were added in this task , enable or disable the http security headers in the openconnect configuration :

Upgraded to vyos-1.5-rolling-202312130023-amd64, and confirmed that it is encrypting.

This also breaks the dhcp service once duplicate ip address configured for two mac-address, tested in version: 1.5-rolling-202312110024

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

@jamcole It will be available in the next rolling release.
Could you re-check it after 2023-12-14?

PR for 1.5: https://github.com/vyos/vyos-build/pull/469

should be fixed by https://github.com/vyos/vyos-1x/pull/2634

PR to allow more pub keys to be easily added.

Rebase and move out of draft after dependency, PR https://github.com/vyos/vyos-1x/pull/2624 (T5821), is merged.