This probably should have gone to the list.<br><br><div class="gmail_quote">On Fri, Mar 4, 2011 at 11:01 AM, <a href="mailto:richardvoigt@gmail.com">richardvoigt@gmail.com</a> <span dir="ltr"><<a href="mailto:richardvoigt@gmail.com">richardvoigt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Simon's latest version is 2.57, you want at least 2.53, a snippet from the changelog:<div><br></div><div><span style="font-family:'Times New Roman';font-size:medium"><pre style="word-wrap:break-word;white-space:pre-wrap">
version 2.53
Rationalised the DHCP tag system. Every configuration item
which can set a tag does so by adding "set:<tag>" and
every configuration item which is conditional on a tag is
made so by "tag:<tag>". The NOT operator changes to '!',
which is a bit more intuitive too. Dhcp-host directives
can set more than one tag now. The old '#' NOT,
"net:" prefix and no-prefixes are still honoured, so
no existing config file needs to be changed, but
the documentation and new-style config files should be
much less confusing.
</pre><div><br></div></span><div><div></div><div class="h5"><br><div class="gmail_quote">On Fri, Mar 4, 2011 at 10:58 AM, Michael P. McDonnell <span dir="ltr"><<a href="mailto:bzaks1424@gmail.com" target="_blank">bzaks1424@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm on version 2.45 - it was the default with SLES. I'll see if I can find something closer to 2.5.x, is there a "minimum" just in case I find an RPM.<br><br>By the way - thank you so much, you guys have been insanely helpful.<div>
<div></div><div><br>
<br><div class="gmail_quote">On Fri, Mar 4, 2011 at 10:55, <a href="mailto:richardvoigt@gmail.com" target="_blank">richardvoigt@gmail.com</a> <span dir="ltr"><<a href="mailto:richardvoigt@gmail.com" target="_blank">richardvoigt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">The behavior you're seeing exactly matches the old description, when "tag:" wasn't a keyword.<div>
<br></div><div><span style="font-family:arial,sans-serif;font-size:13px"><dt>
<b style="font-weight:bold">-F, --dhcp-range=[[net:]network-id,]<start-addr>,<end-addr>[[,<netmask>],<broadcast>][,<default lease time>]</b></dt><dd>Enable the DHCP server. Addresses will be given out from the range <start-addr> to <end-addr> and from statically defined addresses given in <b style="font-weight:bold">dhcp-host</b> options. If the lease time is given, then leases will be given for that length of time. The lease time is in seconds, or minutes (eg 45m) or hours (eg 1h) or the literal "infinite". The minimum lease time is two minutres. This option may be repeated, with different addresses, to enable DHCP service to more than one network. For directly connected networks (ie, networks on which the machine running dnsmasq has an interface) the netmask is optional. It is, however, required for networks which receive DHCP service via a relay agent. The broadcast address is always optional. On some broken systems, dnsmasq can listen on only one interface when using DHCP, and the name of that interface must be given using the <b style="font-weight:bold">interface</b> option. This limitation currently affects OpenBSD before version 4.0. 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. When it is prefixed with 'net:' then its meaning changes from setting a tag to matching it. Only one tag may be set, but more than one tag may be matched. The end address may be replaced by the keyword <b style="font-weight:bold">static</b> which tells dnsmasq to enable DHCP for the network specified, but not to dynamically allocate IP addresses. Only hosts which have static addresses given via <b style="font-weight:bold">dhcp-host</b> or from /etc/ethers will be served.</dd>
<dd><br></dd><dd><br></dd></span><div><br></div><div>In this case, "tag:custom" is seen as the network-id being set, and no tags are being matched.</div><div><br></div><div>You should probably upgrade to a newer version.</div>
<div><div></div><div>
<br><div class="gmail_quote">On Fri, Mar 4, 2011 at 10:51 AM, <a href="mailto:richardvoigt@gmail.com" target="_blank">richardvoigt@gmail.com</a> <span dir="ltr"><<a href="mailto:richardvoigt@gmail.com" target="_blank">richardvoigt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div>It looks like the dhcp-range is setting a tag instead of matching it.</div><div><br></div>
<div><br></div><div>If you took out "tag:custom," from the dhcp-range and restart dnsmasq, would the query still show "tags: tag:custom"</div>
<div><br></div><div>Wait a second. I don't think the tags line is supposed to contain "tag:". What version are you running?</div></blockquote><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div><div><div><br></div><div><br></div><div><div class="gmail_quote">On Fri, Mar 4, 2011 at 10:45 AM, Michael P. McDonnell <span dir="ltr"><<a href="mailto:bzaks1424@gmail.com" target="_blank">bzaks1424@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">I understand this isn't EXACTLY the scenario I need to fix for - but I kind of want to learn what I'm doing wrong as well. (This will help me learn more about dhcp in general)<br>
<br>Here's my dnsmasq.conf:<br>
###DNSMASQ CONF<br>no-resolv<br>no-poll<br>dhcp-vendorclass=set:custom,"Magic Server"<br>dhcp-range=tag:custom,10.230.240.50,10.230.240.150,12h<br>dhcp-range=10.230.240.151,10.230.240.254,12h<br>dhcp-script=/root/bin/doit<br>
log-queries<br>log-dhcp<br>#####END<br><br>Here's my <i>*</i>current* dhclient.conf<br>###DHCLIENT CONF<br>send dhcp-lease-time 3600;<br>send vendor-class-identifier "sample";<br>#send vendor-class-identifier "Magic Server";<br>
request subnet-mask, broadcast-address, routers,<br> interface-mtu, host-name, domain-name,<br> domain-name-servers, nis-domain, nis-servers,<br> nds-context, nds-servers, nds-tree-name,<br> netbios-name-servers, netbios-dd-server,<br>
netbios-node-type, netbios-scope, ntp-servers;<br>require subnet-mask;<br>timeout 60;<br>retry 60;<br>reboot 10;<br>select-timeout 5;<br>initial-interval 2;<br>#####END<br><br>Here's what I found as the output:<br>
Mar 4 10:33:54 pxeserv dnsmasq[18619]: Available DHCP range: 10.230.240.50 -- 10.230.240.150<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: Available DHCP range: 10.230.240.151 -- 10.230.240.254<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: Vendor class: sample<br>
Mar 4 10:33:54 pxeserv dnsmasq[18619]: DHCPREQUEST(eth0) 10.230.240.54 00:50:56:b9:00:05<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: DHCPACK(eth0) 10.230.240.54 00:50:56:b9:00:05<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: requested options: 1:netmask, 28:broadcast, 3:router, 26:mtu,<br>
Mar 4 10:33:54 pxeserv dnsmasq[18619]: requested options: 12:hostname, 15:domain-name, 6:dns-server,<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: requested options: 40:nis-domain, 41:nis-server, 87, 85, 86,<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: requested options: 44:netbios-ns, 45:netbios-dd, 46:netbios-nodetype,<br>
Mar 4 10:33:54 pxeserv dnsmasq[18619]: requested options: 47:netbios-scope, 42:ntp-server<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: tags: tag:custom<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 1 option: 53:message-type 05<br>
Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 4 option: 54:server-identifier 0a:e6:f0:64<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 4 option: 51:lease-time 00:00:0e:10<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 4 option: 58:T1 00:00:07:08<br>
Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 4 option: 59:T2 00:00:0c:4e<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 4 option: 1:netmask ff:ff:ff:00<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 4 option: 28:broadcast 0a:e6:f0:ff<br>
Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 4 option: 3:router 0a:e6:f0:64<br>Mar 4 10:33:54 pxeserv dnsmasq[18619]: sent size: 4 option: 6:dns-server 0a:e6:f0:64<div><div></div><div><br><br><br>
<div class="gmail_quote">On Fri, Mar 4, 2011 at 10:19, <a href="mailto:richardvoigt@gmail.com" target="_blank">richardvoigt@gmail.com</a> <span dir="ltr"><<a href="mailto:richardvoigt@gmail.com" target="_blank">richardvoigt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">Does dnsmasq have dhcp logging enabled? Can you paste the few lines associated with giving the client an address from the wrong block?<div>
<div></div><div><br><br><div class="gmail_quote">On Fri, Mar 4, 2011 at 10:15 AM, Michael P. McDonnell <span dir="ltr"><<a href="mailto:bzaks1424@gmail.com" target="_blank">bzaks1424@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">I'm was just doing a dhclient eth0 on the client. So I guess that would make sense not killing the lease all together...<br>
<br>so I tried doing a dhclient -r eth0, then doing a dhclient eth0. No luck :-/<div><div></div><div><br><br><div class="gmail_quote">
On Fri, Mar 4, 2011 at 10:12, <a href="mailto:richardvoigt@gmail.com" target="_blank">richardvoigt@gmail.com</a> <span dir="ltr"><<a href="mailto:richardvoigt@gmail.com" target="_blank">richardvoigt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
Are you releasing the lease after changing the client configuration, or renewing an existing lease?<br><br><div class="gmail_quote"><div><div></div><div>On Thu, Mar 3, 2011 at 11:31 PM, Michael P. McDonnell <span dir="ltr"><<a href="mailto:bzaks1424@gmail.com" target="_blank">bzaks1424@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div><div></div><div>So I'd like to use vendor class identifer to create two different ranges in dnsmasq, and I'm not entire sure how to go about that.<br>
<br>dhcp-vendorclass=set:custom,"Sample Vendor Class"<br>dhcp-range=tag:custom,192.168.0.50,192.168.0.150,12h<br>
dhcp-range=192.168.0.151,192.168.0.254,12h<br><br>However - if I take a single client and flip the vendor-class-identifier on or off in the dhclient.conf, I don't get a different IP. <br>Am I doing something wrong? Should I be looking to do something differently in my config?<br>
<br>Also - would it be possible for me to exactly specify to only run dhcp-script for a specific lease? (so only the dhcp leases tagged with "custom" ? ) Or do I need to just put that logic in the script that the dhcp-script is calling?<br>
<br>Thanks for your help in advance!<br>
<br></div></div>_______________________________________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
<a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" target="_blank">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><br>
<br></blockquote></div><br>
</blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br>