mirror of
https://github.com/pi-hole/dnsmasq.git
synced 2025-12-19 10:18:25 +00:00
manpage: clarify tags: semantics for --dhcp-host
Mention that several tags can be specified and instruct the user that some other match must still be provided for the directive to have any effect.
This commit is contained in:
committed by
Simon Kelley
parent
d9995a1add
commit
ef2f8d70d2
@@ -1037,7 +1037,7 @@ is also included, as described in RFC-3775 section 7.3.
|
|||||||
tells dnsmasq to advertise the prefix without the on-link (aka L) bit set.
|
tells dnsmasq to advertise the prefix without the on-link (aka L) bit set.
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B \-G, --dhcp-host=[<hwaddr>][,id:<client_id>|*][,set:<tag>][tag:<tag>][,<ipaddr>][,<hostname>][,<lease_time>][,ignore]
|
.B \-G, --dhcp-host=[<hwaddr>][,id:<client_id>|*][,set:<tag>][,tag:<tag>][,<ipaddr>][,<hostname>][,<lease_time>][,ignore]
|
||||||
Specify per host parameters for the DHCP server. This allows a machine
|
Specify per host parameters for the DHCP server. This allows a machine
|
||||||
with a particular hardware address to be always allocated the same
|
with a particular hardware address to be always allocated the same
|
||||||
hostname, IP address and lease time. A hostname specified like this
|
hostname, IP address and lease time. A hostname specified like this
|
||||||
@@ -1136,7 +1136,10 @@ ignore requests from unknown machines using
|
|||||||
If the host matches only a \fB--dhcp-host\fP directive which cannot
|
If the host matches only a \fB--dhcp-host\fP directive which cannot
|
||||||
be used because it specifies an address on different subnet, the tag "known-othernet" is set.
|
be used because it specifies an address on different subnet, the tag "known-othernet" is set.
|
||||||
|
|
||||||
The tag:<tag> construct filters which dhcp-host directives are used. Tagged directives are used in preference to untagged ones.
|
The tag:<tag> construct filters which dhcp-host directives are used; more than
|
||||||
|
one can be provided, in this case the request must match all of them. Tagged
|
||||||
|
directives are used in preference to untagged ones. Note that one of <hwaddr>,
|
||||||
|
<client_id> or <hostname> still needs to be specified (can be a wildcard).
|
||||||
|
|
||||||
Ethernet addresses (but not client-ids) may have
|
Ethernet addresses (but not client-ids) may have
|
||||||
wildcard bytes, so for example
|
wildcard bytes, so for example
|
||||||
|
|||||||
Reference in New Issue
Block a user