https://bugs.passt.top/show_bug.cgi?id=83, that is, without explicit interface, address, or routes settings, if pasta(1) finds multiple interfaces with non-default routes for a given IP version, and no default route, it fails to start claiming a mismatch in the netlink sequence of messages used to query the kernel for routes.

Single fix for a potential issue with newer kernels where pasta(1) would terminate right away because of a mismatch in the expected netlink sequence. We don't know exactly how to reproduce the issue, see https://github.com/containers/podman/issues/22052#issuecomment-2004344989 and following, but I think the fix is critical enough as to warrant a new version.

Most notable fixes: - with --dns-forward, don't touch source IP address of DNS responses if the container/guest contacted the resolver directly (without using the address given as --dns-forward) - pasta(1) was hanging on upcoming kernel version 6.9