Issue description

This is mostly a reminder to follow up on what upstream decides to do.

Since iptables 1.6.2, iptables-restore fails instead of ignoring erroneous arguments, specifically -w5 which kube-proxy has been (erroneously) using instead of -w 5. This causes its firewall rules to fail along with k8s networking in general.

kubernetes/kubernetes#58956

Steps to reproduce

Run eg. the dns.multinode test.