From 990ce652a04d6cacbd39aa02f3e28c14f0ab4baa Mon Sep 17 00:00:00 2001 From: Tomek Mrugalski Date: Wed, 6 Jul 2016 12:03:00 +0200 Subject: [PATCH] [4518] One reservation example updated. --- doc/guide/dhcp4-srv.xml | 32 ++++++++++++++++++-------------- 1 file changed, 18 insertions(+), 14 deletions(-) diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index 6578e4487b..d869021a17 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -2705,21 +2705,25 @@ It is merely echoed by the server Vendor specific options can be reserved in a similar manner: -"reservations": [ { - "hw-address": "aa:bb:cc:dd:ee:ff", - "ip-address": "10.0.0.7", - "option-data": [ - { - "name": "vivso-suboptions", - "data": "4491" - }, - { - "name": "tftp-servers", - "space": "vendor-4491", - "data": "10.1.1.202,10.1.1.203" - } ] -} ] + "subnet4": [ { + "reservations": [ + { + "hw-address": "aa:bb:cc:dd:ee:ff", + "ip-address": "10.0.0.7", + "option-data": [ + { + "name": "vivso-suboptions", + "data": "4491" + }, + { + "name": "tftp-servers", + "space": "vendor-4491", + "data": "10.1.1.202,10.1.1.203" + } ] + } ] + } ] +} Options defined on host level have the highest priority. In other words, -- 2.47.2