restrict: Ignore CIDR in restrict address

Gary E. Miller gem at
Fri Jun 9 18:40:40 UTC 2017

Yo Hal!

On Thu, 08 Jun 2017 21:12:03 -0700
Hal Murray <hmurray at> wrote:

> commit 1f40056d7d1190b1732ad3f4b6db8f15f24334b6
>     One small step to accepting CIDR notation.
> That seems like a bug to me.  It does something different from what
> most users would expect.

Really?  Right now the documentation, and expectation, is that
CIDR is not allowed on restrict.  It makes no change to documented
or normal behavior.  So the expectation is : Don't do it.

When I get it working, certainly by next week, I'll add documentation.

UNtil then, pretend it does not exist.

> At a minimum, changes like that deserve a warning to devel.

Consider this fair warninging that I am adding CIDR to the restrict
statement.  No changes to working/existing configurations have been done
or will be done.  Just an extention that needs a bit more work.

> If you aren't planning to implement the rest of the fix soon, I think
> you should add an error message.

I am working on the rest of the implementation right now, but not
gonna rush it.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the devel mailing list