Hello,
I think that the dnsmasq.8 manpage for the version 2.20 is not quite accurate
about the "--dhcp-range" option. What do you think about the attached patch?
--
Martin
--- dnsmasq.8.orig 2005-01-22 16:03:27.000000000 +0100
+++ dnsmasq.8 2005-03-21 16:12:40.000000000 +0100
@@ -319,7 +319,7 @@
identical queries without forwarding them again. This flag disables
negative caching.
.TP
-.B \-F,
--dhcp-range=[network-id,]<start-addr>,<end-addr>[[,<netmask>],<broadcast>][,<default
lease time>]
+.B \-F,
--dhcp-range=[[net:]network-id,]<start-addr>,<end-addr>[,<netmask>[,<broadcast>]][,<default
lease time>]
Enable the DHCP server. Addresses will be given out from the range
<start-addr> to <end-addr> and from statically defined addresses given
in
@@ -339,8 +339,9 @@
option. This limitation currently affects OpenBSD. It is always
allowed to have more than one dhcp-range in a single subnet. The optional
network-id is a alphanumeric label which marks this network so that
-dhcp options may be specified on a per-network basis. The end address
-may be replaced by the keyword
+dhcp options may be specified on a per-network basis. When it is prefixed
+with 'net:' then its meaning changes from setting a tag to matching it.
+The end address may be replaced by the keyword
.B static
which tells dnsmasq to enable DHCP for the network specified, but not
to dynamically allocate IP addresses. Only hosts which have static
