Merged.

This is not a backport candidate until 'T834: accel-ppp: l2tp implementation' has been backported.

This is not a backport candidate until the 'T989: accel-ppp: IPoE implementation' has been backported.

This is not a backport candidate until the full OpenVPN rewrite is backported.

Parent task not yet listed for backport; discussed with @zsdc for possible inclusion in future.

Actually, upon reflection, the parser error is just too many terms on the line, hitting HandlingError; the rare exception exists, but is misleading, so 'use cases and/or implementation' ...

As expected,
(1) This is a parser error
(2) It is independent of any specific configuration script; it can be reproduced by calling conf.get_config_dict() with uncommitted changes, from any conf_mode script.

Yes, thanks, c-po; the revised settings (above) are consistent with defaults and behaviour for both crux and equuleus.

I will backport this, unless objections ...

For consistency with the relative sizes set by CLI in the conf_mode script (system-ip.py), the default params should be:

The size of an ARP cache entry is 384 bytes (x86-64), so the change will add ~720k -- ~3 MiB, which seems reasonable. I will add the suggested settings to sysctl defaults.

https://github.com/vyos/vyos-1x/compare/current...jestabro:syntax-version?expand=1

Revising this design, following discussion with dmbaturin; implementation in T1962.

Move to 'Needs testing'; repo linked below. Add example of third-party package, and test, before PR.

This appears to be a moving target in at least one sense:
The package lists I now see differ from what is listed in the files above; one notable difference is a missing 'systemd-sysv':

My guess would be missing live-tools in the recommends=false case; live-tools replaces update-initramfs with its version. I'm building to check ...

To avoid confusion, this will only be in the equuleus branch:
https://github.com/vyos/vyos-1x/compare/equuleus...jestabro:T1585?expand=1

Initial version for equuleus here:
https://github.com/jestabro/vyos-1x/tree/T1585

This requirement needs to be applied to 'running_config' as well, in case of (1) editing at the level of an unset node (parse error); (2) reading effective_value(s) in configuration mode (lacking full paths).

Thanks; this is necessary when (1) editing at the level of an unset node; (2) reading effective_value(s) in configuration mode. I will extend the original fix.

@Merijn if you are still willing to test, I can provide build instructions, if you need. I noticed that you had been working with @hagbard recently on your build environment; if you are willing to use docker, I can give you step-by-step instructions to build with these patches.

A version of @hagbard 's fix has been committed as eced4a49c67d2e0e3e131193afe679aee0c5c679; the incorrect behaviour with the edit level has been fixed and referenced in that task (T1846).

A parsimonious fix to this issue has been committed; I will move the status to "In progress" until the related issues mentioned here are sorted through.

The fix suggested in the pull request did not resolve the issue as a consequence of T1847. With that issue resolved, we can consider this merge.

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

This is reported as resolved by Line2 in parent T1801; the related issue mentioned therein is also resolved by the revised fix in T1801.

@Merijn I am consulting with the author of the pull request; I still need to confirm behavior before we can consider merging.

The resolution in T1801 will prevent the error in this case.

The general solution has been merged into vyos-1x.

@Merijn I will build and run a sanity check, and then we can merge into rolling for testing; I'll confirm when done. Thanks again for the offer to test.

The merged fix addressed the problem as it occurs in configuration mode, however, the same issue can occur during the running of migration scripts. A solution to cover all cases has been tested, and is pending.