How to name this function?

Pull request: https://github.com/vyos/vyos-1x/pull/562

This was infact only a warning - but for whatever reason nftables is not logging to kernel log :/

@marekm I've reproduced your issue and fixed it for 1.2.7 - Thanks for reporting.

This also relates to https://phabricator.vyos.net/T2829#76815

Fix in PR: https://github.com/vyos/vyos-1x/pull/561

Note: New xl2tpd package does not work with the followings params in options.xl2tpd

crtscts
lock

Behavior in FRR version 7.4

Reproduced the issue in the rolling release VyOS 1.3-rolling-202009300117 and the route-map configuration wiped out after the reboot with the error as mentioned in the problem description and happens only when the bridge address is added for src and not for other interface types.

We found one case when it does work (for both Crux and 1.3), which can lead to further investigation: when the policy is applied to a PPPoE client interface and the class traffic is matched with the command naming the subinterface (the first of the 3 options above).

At this stage, I can't realize the automatic configuration of NDP proxy. On the other hand, although I don't know what additional application scenarios will be in addition to nat66, I hope to give full play to the full potential of NDP proxy, so I don't want to bind it to nat66 artificially.

In T2829#73944, @c-po wrote:

There can not be a config migrator, thus the setting will be changed to "prefer" (default) which will not break any client implementations

Still wondering why ndp-proxy can not be part of the nat66 tree.
When a NAT66 translation is added we know the prefix (src and dst), the in/out-bound interface - so another CLI option (ndp-proxy) could probably be added to not open up an additional service node.

This PR should correct it. Fortunately it appears that that this node was the only place this existed.

@c-po Request merge https://github.com/vyos/vyos-1x/pull/556

In T2943#76739, @runar wrote:

as a workaround you could add this to a post-boot script on the device.

This is disallowed by design by the VyOS team. the reason for this is partly because of the configuration order done by VyOS and how the dns lookup is handled by Wireguard.
Yes, the wg configuration utillity DOES handle DNS lookups, but NO, Wireguard does not handle them. This means that the DNS lookups is done once (and only once) when the wg command is executed on creation of the tunnel and then the resulting ip result is stored in wireguard. this results in the dns lookup will fail after a reboot of the VyOS device because it cant resolve the dns of the endpoint at that point (this is done before routing is enabled on the device)

To reproduce

PR for Rolling https://github.com/vyos/vyos-1x/pull/559

PR for CRUX https://github.com/vyos/vyatta-cfg-system/pull/130

Backported to crux

In T2744#76514, @Viacheslav wrote:

Can we replace igmp-proxy with pimd?

NDP Proxy has been implemented in T2898. For nat66 to work normally, proxy-ndp must be operated in static mode.

Already basically ready to merge

To reproduce this bug

I accidentally found sonarcloud, vyos now uses this system for quality control?

PR for crux https://github.com/vyos/vyos-1x/pull/558

PR https://github.com/vyos/vyos-build/pull/127
Also will be good cherrypick this to crux.