Sanitize noncanonical IPv4 split routes

Fix IPv4 split-{in,ex}clude routes with misspecified host bits

Some VPN platforms (GlobalProtect, apparently) allow administrators to input such non-canonical IPv4 routes, and some routing configuration utilities (apparently not iproute2) simply do not accept such non-canonical IPv4 routes.

An example of the confusion this can cause: https://lists.infradead.org/pipermail/openconnect-devel/2020-April/005665.html

The robustness principle suggests that the best thing to do here is to fix these routes, but complain about them while we're at it, e.g.:

WARNING: Split include "10.12.34.56/8" has host bits set, replacing with "10.0.0.0/8"

added Not a bug vpnc-script labels

changed the description

added 1 commit

• 36d1b002 - don't modify const route

Compare with previous version

added 36 commits

• 36d1b002...a98de0fc - 34 commits from branch master
• 0745d642 - fix IPv4 split-{in,ex}clude routes with misspecified host bits
• 5e64a160 - don't modify const route

Compare with previous version

added 1 commit

• 00d89cf4 - don't modify const route

Compare with previous version

changed the description

added 2 commits

• 902b592a - O IPv4 network, how can I bork thee? Let me count the ways.
• e9d2da77 - changelog

Compare with previous version

closed

mentioned in commit daa48822

mentioned in commit 3afbdaee