range6 low-addr high-addr

[Shane Kerr]

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

Yes, alpha 2 will have this fix. Should be out sometime next week.

John Jason Brzozowski (CISSP, RHCT) wrote:
> Got it, thanks Shane.  The former is what I have been using.  This fix will
> be available in the next release right?
> 
> John
> 
> 
> On 6/14/07 6:11 AM, "Shane Kerr" <Shane_Kerr at isc.org> wrote:
> 
> John,
> 
> The fix just makes the current syntax work. It *did* work in certain
> circumstances, but not all. Now it should work either as:
> 
> range6 1:2:3:4::/63;                   # CIDR-style works
> range6 1:2:3:6:: 1:2:3:6:7:8:9:ffff;   # start/end also works
> 
> John Jason Brzozowski (CISSP, RHCT) wrote:
>>>> Shane can you elaborate on what the fix will look like?
>>>>
>>>>
>>>> On 6/12/07 2:56 AM, "Shane Kerr" <Shane_Kerr at isc.org> wrote:
>>>>
>>>> Suprasad,
>>>>
>>>> Suprasad Mutalik Desai wrote:
>>>>>>>         can anyone tell me how the address is assigned to the client
>>>>>>> as range6 low-addr high-addr gives a parse error in dhcp-4.0.0a1
>>>>>>> version  and i am using range6 high-addr/prefix (w.r.t dhcpd.conf.5).
>>>> Thanks for the bug report. There was a mistake in the way I used the token
>>>> parsing code, and one of my colleagues discovered it recently. We have a fix
>>>> waiting for 4.0.0a2, which should be released soon. Apologies for any
>>>> problems
>>>> this caused!
>>

> ===============================================
> John Jason Brzozowski (CISSP, RHCT)
> jjmb at jjmb.com
> (p) 484-994-6787
> (f) 610-616-4535
> ===============================================




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGcR+6MsfZxBO4kbQRAuZEAJ9v7io3+AQpFpMKusa0MeXwaMdfzQCgnfij
7n8RLbCKr7NdyZMyVnEtudY=
=YMeP
-----END PGP SIGNATURE-----