On Sun, Jul 11, 2021 at 07:13:32PM +0200, john doe wrote: > On 7/11/2021 11:06 AM, Paul Gear via Dnsmasq-discuss wrote: > > On 10/7/21 9:52 pm, Geert Stappers via Dnsmasq-discuss wrote: > > > Snippet dnsmasq manual page > > > > > > --dhcp-range=[tag:<tag>[,tag:<tag>],][set:<tag>,]<start-addr>[,<end-addr>|<mode>][,<netmask>[,<broadcast>]][,<lease > > > time>] > > > > > > So > > > > > > dhcp-range=203.0.113.0, 255.255.255.248, 1d > > > should be something like > > > } } } dhcp-range=203.0.113.0, 203.0.113.7,255.255.255.248, 1d > > > > > > > > > Back to > > > > > From (1): > > > > > > > > > > " this dhcp-range MUST include the netmask." > > > > > > > > > > Unless I'm missing something, I don't see a subnet mask being > > > > > specified. > > > > > > > > > > > > > > > (1) https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html > > > > > > > > If so, the > > > --dhcp-range=[tag:<tag>[,tag:<tag>],][set:<tag>,]<start-addr>[,<end-addr>|<mode>][,<netmask>[,<broadcast>]][,<lease > > > time>] > > > should be > > > --dhcp-range=[tag:<tag>[,tag:<tag>],][set:<tag>,]<start-addr>[,<end-addr>|<mode>],<netmask>[,<broadcast>][,<lease > > > time>] > > > or even > > > --dhcp-range=[tag:<tag>[,tag:<tag>],][set:<tag>,]<start-addr>,<end-addr>|<mode>,<netmask>[,<broadcast>][,<lease > > > time>] > > > > Hi John & Geert, > > > > So bottom line is that end-addr is not optional when netmask is > > specified, even though a literal reading of the current man page > > suggests that it is. I'll try to get a documentation patch together(is > > here the right place to post it?) when I'm done. > > > > I can see where you got confused, an explanation on how to interpret the > '[],|' would go a long way. > > Patch submition via e-mail looks to be the prefered way for accepting > contributions (The maintainer (Simon Kelley) might say otherwise though). There is now https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q3/015403.html which has a patch against the manual page. It proposes this line
--dhcp-range=[tag:<tag>[,tag:<tag>],][set:<tag>,]<start-addr>[,<end-addr>|<mode>[,<netmask>[,<broadcast>]]][,<lease time>] The <start-addr>[,<end-addr>|<mode>][,<netmask>[,<broadcast>]] became <start-addr>[,<end-addr>|<mode>[,<netmask>[,<broadcast>]]] a ] has been moved. This should indicate that when adding a netmask there should already be end-address or the mode. It expresses > > So bottom line is that end-addr is not optional when netmask is > > specified, even though a literal reading of the current man page > > suggests that it is. Time will tell if the patch gets included in the upcoming release. Groeten Geert Stappers -- Silence is hard to parse _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
