Since loopback and dummy are fundamentally different in Linux, trying to pretend they are not would be misleading rather than helpful. Unless anything changes in the kernel, we should keep things as is.

@Giggum The main reason for using ipaddrcheck is its speed (it's a compiled binary). Python is way too slow for validators due to the interpreter startup cost, so it's not an option until we completely overhaul the CLI backend. I'll look into the issue.

FRR issue is still open, no progress.

Since ISC DHCP relay agent is abandoned, I wonder if there are any chances of getting it fixed.

I agree with @Apachez: people should be able to disable IPv4 or IPv6 forwarding if they feel like it. For example, a router used exclusively as a looking glass or a load balancer arguably shouldn't forward any packets on L3.

Since the task as worded is no actionable, I'm closing it as invalid. I'm not against using any tools that might help us, but we need to be sure what the task is (e.g., to implement regular scanning, or to fix specific suggestions from a scan...).

No urgency here, so moving out of LTS.

No simple solution, so it should be done and tested in a development release first in any case, not in LTS.

Moving to 1.5 for now. If we are confident about the solution, we can backport it to 1.4 later. New architectures certainly should be introduced in development releases first.

Since it's not really a trivial change, I'm moving this to 1.5 now. If we find a good solution and prove that it's perfectly safe, then we can backport it to 1.4 later.

Seems to work well enough in 1.4.0. If any issues turn up, we'll make separate tasks.

Removing from Sagitta, since we aren't changing any syntax within an LTS release.