<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>Hello<br>
<br>
As others have pointed out, classes must only be defined
globally. Defining them within subnets or networks is not
supported and it can have odd effects on statement
execution/option values. The configuration parser currently does
not complain when you do this but it probably should. We will
very likely add at least a warning if not an error for this.<br>
<br>
Regards,<br>
<br>
Thomas Markwalder,<br>
</tt><tt><tt>ISC Software Engineering</tt><br>
</tt><br>
<div class="moz-cite-prefix">On 1/25/19 11:29 AM, perl-list wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1855684348.2443421.1548433755955.JavaMail.zimbra@network1.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div style="font-family: Andale Mono; font-size: 10pt; color:
#000000">
<div style="font-family: Andale Mono; font-size: 10pt; color:
#000000">Class should be global, I believe. That is my
understanding anyway. You shouldn't have them inside of a
subnet {} or shared-network {} statement. The limiting occurs
with the match if statement. That is my understanding
anyways.<br>
<br>
<hr id="zwchr" data-marker="__DIVIDER__">
<div data-marker="__HEADERS__">
<blockquote style="border-left:2px solid
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From:
</b>"Gaikwad Yogesh" <a class="moz-txt-link-rfc2396E" href="mailto:Yogesh.Gaikwad@tieto.com"><Yogesh.Gaikwad@tieto.com></a><br>
<b>To: </b>"Users of ISC DHCP"
<a class="moz-txt-link-rfc2396E" href="mailto:dhcp-users@lists.isc.org"><dhcp-users@lists.isc.org></a><br>
<b>Sent: </b>Friday, January 25, 2019 9:43:48 AM<br>
<b>Subject: </b>RE: Linux DHCP sending wrong parameters
in offer packet<br>
</blockquote>
</div>
<div data-marker="__QUOTED_TEXT__">
<blockquote style="border-left:2px solid
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">Hi
Glenn,<br>
<br>
I followed Cisco documentation on below link to configure
the option 43 for Cisco AP's:<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/97066-dhcp-option-43-00.html">https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/97066-dhcp-option-43-00.html</a><br>
<br>
<br>
There are two parts to this config, one is in the global
config, and other part sits inside the subnet.<br>
<br>
Below lines are in the global configuration<br>
<br>
# CISCO OPTION 43<br>
option space Cisco_LWAPP_AP;<br>
option Cisco_LWAPP_AP.server-address code 241 = array of
ip-address;<br>
<br>
<br>
And then below is the subnet configuration<br>
<br>
subnet 10.56.20.0 netmask 255.255.255.0 {<br>
option routers 10.56.20.1;<br>
option subnet-mask 255.255.255.0;<br>
option broadcast-address 10.56.20.255;<br>
default-lease-time 43200;<br>
<br>
class "Cisco AP c3800" {<br>
<br>
match if option vendor-class-identifier = "Cisco AP
c3800";<br>
option vendor-class-identifier "Cisco AP c3800";<br>
vendor-option-space Cisco_LWAPP_AP;<br>
option Cisco_LWAPP_AP.server-address 10.140.1.1; }<br>
<br>
pool {<br>
failover peer "te-failover";<br>
deny dynamic bootp clients;<br>
range 10.56.20.10 10.56.20.250;<br>
}<br>
}<br>
<br>
<br>
<br>
We have several such subnets configured which have this
'class "Cisco AP c3800"' configuration inside the subnets,
the above mentioned subnet sits at the end of the
dhcpd.conf file.<br>
<br>
I understood your concern to have it configured globally,
but then what if I want to have a different
'Cisco_LWAPP_AP.server-address' for different subnets?<br>
<br>
<br>
<br>
Best regards,<br>
<br>
Yogesh Gaikwad, Technical Architect - TECA Network<br>
<br>
Tieto Corporation, TSM<br>
<br>
-----Original Message-----<br>
From: dhcp-users [<a class="moz-txt-link-freetext" href="mailto:dhcp-users-bounces@lists.isc.org">mailto:dhcp-users-bounces@lists.isc.org</a>]
On Behalf Of Glenn Satchell<br>
Sent: Friday, January 25, 2019 7:45 PM<br>
To: Users of ISC DHCP <a class="moz-txt-link-rfc2396E" href="mailto:dhcp-users@lists.isc.org"><dhcp-users@lists.isc.org></a><br>
Subject: Re: Linux DHCP sending wrong parameters in offer
packet<br>
<br>
Hi Yogesh,<br>
<br>
Without seeing hyour config file I can guess that the
option 43 setting should be set in the global
configuration rather than inside one of your subnets.
Setting it inside the subnet causes inheritance of those
subnet values.<br>
<br>
To confirm, could you please post your dhcpd.conf? If it
is is very large perhaps you might post the relevant
parts.<br>
<br>
regards,<br>
-glenn<br>
--<br>
Glenn Satchell <a class="moz-txt-link-freetext" href="mailto:glenn.satchell@uniq.com.au">mailto:glenn.satchell@uniq.com.au</a> |
Today is the past<br>
Uniq Advances Pty Ltd <a class="moz-txt-link-freetext" href="http://www.uniq.com.au">http://www.uniq.com.au</a> |
that people in<br>
Mobile 0409 458 580 |
the future will<br>
Member IT Professionals Association <a class="moz-txt-link-abbreviated" href="http://www.itpa.org.au">www.itpa.org.au</a> |
dream about.<br>
<br>
On Fri, January 25, 2019 11:41 pm, Gaikwad Yogesh wrote:<br>
> Hi,<br>
><br>
><br>
> There is issue that linux DHCP is sending wrong
parameters while <br>
> sending offer packet for Cisco AP's in one of our
office locations.<br>
><br>
> I have taken packet captures on the DHCP server side.<br>
><br>
><br>
> As you can see in below packet capture there is DHCP
DISCOVER message <br>
> from Cisco AP requesting for IP and other parameters.<br>
><br>
> Then in DHCP offer packet, it offers IP from correct
subnet, but with <br>
> wrong router IP, subnet mask and broadcast address.<br>
><br>
> Basically, my observation is that it is giving wrong
parameters in <br>
> offer from the topmost subnet (as linux works from
top to bottom <br>
> approach) that has cisco option 43 configured. If I
remove the Cisco <br>
> option 43 from that subnet then it provides
parameters from next <br>
> subnet which has the Cisco option 43 in it.<br>
><br>
> The correct subnet from which I am expecting that the
AP should get <br>
> all its parameters is configured at the end of the
DHCP conf file.<br>
><br>
><br>
> DHCP DISCOVER PACKET<br>
><br>
><br>
> [<a class="moz-txt-link-freetext" href="cid:image001.png@01D4B4D9.6F320900">cid:image001.png@01D4B4D9.6F320900</a>]<br>
><br>
><br>
><br>
> DHCP OFFER PACKET<br>
><br>
><br>
> [<a class="moz-txt-link-freetext" href="cid:image002.png@01D4B4D9.6F320900">cid:image002.png@01D4B4D9.6F320900</a>]<br>
><br>
><br>
><br>
><br>
><br>
> Best regards,<br>
><br>
><br>
> Yogesh Gaikwad, Technical Architect - TECA Network<br>
><br>
><br>
> Tieto Corporation, TSM<br>
><br>
><br>
> email
<a class="moz-txt-link-abbreviated" href="mailto:Yogesh.Gaikwad@tieto.com">Yogesh.Gaikwad@tieto.com</a><a class="moz-txt-link-rfc2396E" href="mailto:Yogesh.Gaikwad@tieto.com"><mailto:Yogesh.Gaikwad@tieto.com></a>,
<br>
> direct<br>
> +91 (0)2067303120<br>
> Wing 1, Cluster D, EON Free Zone, MIDC Kharadi
Knowledge Park, Pune - <br>
> 411 014, India<br>
><br>
><br>
>
[Tieto_logo_for_email_signature_127x50]<a class="moz-txt-link-rfc2396E" href="http://www.tieto.com/"><http://www.tieto.com/></a><br>
><br>
><br>
> Please note: The information contained in this
message may be legally <br>
> privileged, confidential and protected from
disclosure. If you <br>
> received this in error, please notify the sender
immediately and <br>
> delete the message from your computer. Thank you.<br>
><br>
> _______________________________________________<br>
> dhcp-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a> <br>
> <a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
><br>
><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a></blockquote>
</div>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
dhcp-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
</pre>
</blockquote>
<br>
</body>
</html>