Re: grepcidr 2.99

["John Levine" <johnl () iecc com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <6DFDC9F9-EE28-4263-8E5B-EB751B35B2B4 () dataix net> you write:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi John,
>
> Great contribution. Thanks
>
> Might I make a suggestion? with the following command it gives Invalid CIDR. In
> my usage it would seem logically convenient to throw any quad octet at it and
> have it translate to the proper CIDR range that isn’t reported as invalid since
> it does this anyway. For instance 127.0.0.1/8 would just become 127.0.0.0/8.

Already does that with the -s for sloppy flag.

> Find it here:
>
> http://www.taugh.com/grepcidr-2/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlV38XsACgkQkEiFRdeC/kVMHQCfcy7D6fIrhIozpm2rwQ3C10g5
EOYAoKgARRkgkBy/+BRbMSKWd+fWWuaP
=9isH
-----END PGP SIGNATURE-----