The temporary fix is to disable the pre-build tests until this issue is not fixed by vendor.

Changing the base template controlling dhcp6c config generation seems to do the trick.
Folowing basic pppoe example provided on Vyos main website :

// config
interfaces {
    ...
    pppoe pppoe0 {
        ...
        dhcpv6-options {
            pd 0 {
                interface eth0 {
                    address "1"
                    sla-id "0"
                }
                length "56"
            }
            rapid-commit
        }
        ipv6 {
            address {
                autoconf
            }
        }
    }
}

FWIW, it looks like Jool's official documentation site is now https://nicmx.github.io/Jool/en/index.html (not jool.mx anymore).

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

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

https://github.com/vyos/vyos-documentation/pull/1677

@guerralucasdaniel7 Could you please share the topology map with all interfaces and networks included?

In T7761#234119, @Fabse wrote:

aggregation — ipt-netflow allows rewriting IP prefixes and ports. Do we want that?

This feature is crucial for our use case. We are using a custom build for ipt_NETFLOW since 2024 in order to --enable-aggregation for being able to account all flows (sampling rate 1) while keeping flow cardinality manageable. --enable-direction would be great as well.

Looks like a feature

In T7769#234133, @Viacheslav wrote:

What about option priority?

set container name c1 priority 1
set container name c2 priority 2

Do you mean to manipulate the start order of the containers? If so, I don’t think it’d solve the issue. On a suitably fast system, all of the containers would start within a fraction of a second of each other. So it’d be a race condition that would almost always fail.

ip -6 r s ff00::/8
ff00::/8 nhid 19 proto static metric 20 pref medium

nexthop dev tun3 weight 1
nexthop dev tun2 weight 1

Finally VyOS-style static route help:

Both tunnel have multicast enabled:

Manually adding route:
ip -6 r a ff00::/8 dev tun2

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

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

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

What about option priority?

set container name c1 priority 1
set container name c2 priority 2

aggregation — ipt-netflow allows rewriting IP prefixes and ports. Do we want that?

Began working on a fix for the op_mode commands

Everything seems to be working as it should on both 1.4.3 and 1.5Q2 for stream, I recently started running tailscale in a container which creates tailscale0 and while I was expecting to run into issues with this, I did not, but it got me thinking, does the interface even need to exist to be able to add it to the nftables ruleset?

Looks like something in this change may be breaking clearing non-VRF DHCP server leases on a config from an upgraded rolling release.

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

@marvin, I think you can claim it

other task related to integrate this new feature: https://vyos.dev/T7766

more bug related to this task :

https://vyos.dev/T6750

Hi everyone, does anyone know of active work on this Feature Request to expose Jool's SIIT-DC functionality in the VyOS CLI?

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

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

The same issue using the VTI interface. Tested in 1.4.3