Spike
2017-09-20 14:06:40 UTC
Hi,
the docs say:
-G,
--dhcp-host=[<hwaddr>][,id:<client_id>|*][,set:<tag>][,<ipaddr>][,<hostname>][,<lease_time>][,ignore]
however as far as I can tell setting a tag works also if I put it after the
ipddr. Is this expected? I would actually prefer that for consistency in
parsing the config since most stanzas don't have tags set.
Can I just do that or will it cause trouble that I'm not foreseeing?
I'd like the order to be the following:
mac,ip,hostname,tags
This seems to match the most common scenario for setting a static lease,
but maybe that's just my case. This will help parsing the file since I can
set an expectation on number of arguments, ie if it's 2 args it's mac and
ip, 3 it has a hostname and 4 a tag set. Otherwise code needs to get more
complicated to try and parse with regexps the field trying to understand if
it's a tag or an ip or what.
thanks,
Spike
the docs say:
-G,
--dhcp-host=[<hwaddr>][,id:<client_id>|*][,set:<tag>][,<ipaddr>][,<hostname>][,<lease_time>][,ignore]
however as far as I can tell setting a tag works also if I put it after the
ipddr. Is this expected? I would actually prefer that for consistency in
parsing the config since most stanzas don't have tags set.
Can I just do that or will it cause trouble that I'm not foreseeing?
I'd like the order to be the following:
mac,ip,hostname,tags
This seems to match the most common scenario for setting a static lease,
but maybe that's just my case. This will help parsing the file since I can
set an expectation on number of arguments, ie if it's 2 args it's mac and
ip, 3 it has a hostname and 4 a tag set. Otherwise code needs to get more
complicated to try and parse with regexps the field trying to understand if
it's a tag or an ip or what.
thanks,
Spike