Re: New feature: restrict address/cidr

Yo Achim! On Sat, 10 Jun 2017 10:51:21 +0200 Achim Gratz via devel wrote: > Am 10.06.2017 um 04:59 schrieb Gary E. Miller via devel: > >> Slightly strange example. I'd expect 10.0.0.0 mask 255.0.0.0 == > >> 10.0.0.0/8 or 10.169.0.0 mask 255.255.0.0 == 10.169.0.0/16 > > > > Your expectations

Re: New feature: restrict address/cidr

Am 10.06.2017 um 04:59 schrieb Gary E. Miller via devel: Slightly strange example. I'd expect 10.0.0.0 mask 255.0.0.0 == 10.0.0.0/8 or 10.169.0.0 mask 255.255.0.0 == 10.169.0.0/16 Your expectations are not mine. Got a citation that says your examples are not only correct, but to be insisted o

Re: New feature: restrict address/cidr

Yo Hal! On Fri, 09 Jun 2017 19:40:23 -0700 Hal Murray wrote: > Nice. Thanks. > > > restrict 10.169.0.0 mask 255.0.0.0 > > restrict 10.169.0.0/8 > > Slightly strange example. I'd expect 10.0.0.0 mask 255.0.0.0 == > 10.0.0.0/8 or 10.169.0.0 mask 255.255.0.0 == 10.169.0.0/16 Your expectation

Re: New feature: restrict address/cidr

Nice. Thanks. > restrict 10.169.0.0 mask 255.0.0.0 > restrict 10.169.0.0/8 Slightly strange example. I'd expect 10.0.0.0 mask 255.0.0.0 == 10.0.0.0/8 or 10.169.0.0 mask 255.255.0.0 == 10.169.0.0/16 Should that generate an error message? -- These are my opinions. I hate spam. ___

✘New feature: restrict address/cidr

Yo All! New feature. The restrict command in ntp.conf now supports CIDR notation. Instead of this: restrict 10.169.0.0 mask 255.0.0.0 restrict 2001:470:e34c:2:: mask ::::ff00:: You can now do: restrict 10.169.0.0/8 restrict 2001:470:e34c:2::/72 Documented in '