<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Ok, I guess this is what I should had comunicated to the
manufacturer right from the start. Laurent, thanks a lot for your
answers and time.<br>
<br>
Best regards,<br>
<font color="#888888">-- <br>
Dima Fadeyev<br>
<br>
</font>
<blockquote
cite="mid:CAAKncqxfoL1R5fzpFNaK7zb4oob-w7amkEkePF5FEgaSCCT1NA@mail.gmail.com"
type="cite">Hello,
<div><br>
</div>
<div> As it is mentioned in the draft from the link you gave,
RFC2131 states that client identifier *MUST NOT* be returned by
dhcp server, so here is the answer to your question.</div>
<div><br>
</div>
<div>
I don't think the behavior proposed from this draft (that cid
*MUST* be included) has already been implemented in ISC DHCP
(draft dated 16/08/2011).</div>
<div><br>
</div>
<div>regards,</div>
<div>laurent</div>
<div><br>
<div class="gmail_quote">
2011/11/25 Dima Fadeyev <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:dima@scancom.es">dima@scancom.es</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#FFFFFF" text="#000000">
<div class="im"> <br>
<blockquote type="cite">Tested and I have same result
(even asking the client to claim it).
<div><br>
</div>
<div>I think, from my knowledge, that cid (opt 61) is
only valuable for dhcp server (why the client asks
the server for things it already knows). Do you have
specials needs for doing this ?</div>
</blockquote>
</div>
I'm testing the GPON OLT/ONTs from one asian manufacturer.
The manufacturer is saying that the ONT (CPE equipment)
monitors the 61 option in dhcpoffers to tell if the
dhcpoffer is destinated to this particular ont or to some
other device.<br>
<br>
In other words, the ONT would send a dhcpdiscover with a
unique option 61 and monitor for a dhcpoffer which would
have the same value set in this option. Once such a
dhcpoffer is seen, the ONT would accept the IP and other
relevant data set in dhcpoffer.<br>
<br>
The manufacturer have given me this reference <a
moz-do-not-send="true"
href="http://tools.ietf.org/html/draft-ietf-dhc-client-id-01"
target="_blank">http://tools.ietf.org/html/draft-ietf-dhc-client-id-01</a><br>
saying that in part three it is stated that the client
identifier must be included in dhcpoffer if it is included
in dhcpdiscover by client. They've also given me the name
of dhcp server they are using (and which is inserting the
option 61 in dhcpdiscover): N2X (Agilent Test Machine),
which I've never heard of before.
<div>
<div class="h5"><span style="color:#1f497d" lang="EN-US"><br>
</span>
<blockquote type="cite">
<div><br>
</div>
<div>One possible way could be to send back value
via a private option (range 224-254) :</div>
<div><br>
</div>
<div>option cid-sent-back code 224 = string;</div>
<div>option cid-sent-back = option
dhcp-client-identifier;</div>
<div>option
dhcp-parameter-request-list 1,3,6,12,15,26,28,42,224;</div>
<div><br>
</div>
<div>regards,</div>
<div>laurent</div>
<div><br>
<br>
<div class="gmail_quote">2011/11/24 Dima Fadeyev <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:dima@scancom.es"
target="_blank">dima@scancom.es</a>></span><br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Thanks
for your reply, <br>
<br>
I've included this line into my dhcpd.conf:<br>
option dhcp-parameter-request-list
1,3,6,12,15,26,28,42,61;<br>
<br>
As you can see, option 61 is included.
However I still can't make dhcp server
include the option 61 into dhcpoffer. This
is how my dhcpdiscover and dhcpoffer packets
look like right now:<br>
<br>
On 11/23/2011 08:21 PM, Laurent PROUFF
wrote:<br>
TIME: 16:00:11.283846<br>
IP: > (00:d0:cb:cf:d0:ab) >
(Broadcast)<br>
OP: 1 (BOOTPREQUEST)<br>
HTYPE: 1 (Ethernet)<br>
HLEN: 6<br>
HOPS: 0<br>
XID: 64217936<br>
SECS: 0<br>
FLAGS: 0<br>
CIADDR: 0.0.0.0<br>
YIADDR: 0.0.0.0<br>
SIADDR: 0.0.0.0<br>
GIADDR: 0.0.0.0<br>
CHADDR:
00:d0:cb:cf:d0:ab:00:00:00:00:00:00:00:00:00:00<br>
SNAME: .<br>
FNAME: .<br>
OPTION: 53 ( 1) DHCP message type
1 (DHCPDISCOVER)<br>
OPTION: 61 ( 7) Client-identifier
01:00:d0:cb:cf:d0:ab<br>
OPTION: 60 ( 11) Vendor class identifier
udhcp 1.9.2<br>
OPTION: 57 ( 2) Maximum DHCP message size
576<br>
OPTION: 55 ( 8) Parameter Request
List 1 (Subnet mask)<br>
3 (Routers)<br>
6 (DNS server)<br>
12 (Host name)<br>
15 (Domainname)<br>
26 (Interface MTU)<br>
28 (Broadcast address)<br>
42 (NTP servers)<br>
<br>
---------------------------------------------------------------------------<br>
TIME: 16:00:11.284036<br>
IP: > (00:22:4d:38:37:27) >
(00:d0:cb:cf:d0:ab)<br>
OP: 2 (BOOTPREPLY)<br>
HTYPE: 1 (Ethernet)<br>
HLEN: 6<br>
HOPS: 0<br>
XID: 64217936<br>
SECS: 0<br>
FLAGS: 0<br>
CIADDR: 0.0.0.0<br>
YIADDR: 10.0.0.154<br>
SIADDR: 0.0.0.0<br>
GIADDR: 0.0.0.0<br>
CHADDR:
00:d0:cb:cf:d0:ab:00:00:00:00:00:00:00:00:00:00<br>
SNAME: .<br>
FNAME: .<br>
OPTION: 53 ( 1) DHCP message type
2 (DHCPOFFER)<br>
OPTION: 54 ( 4) Server identifier
10.0.0.32<br>
OPTION: 51 ( 4) IP address leasetime
340600 (3d22h36m40s)<br>
OPTION: 1 ( 4) Subnet mask
255.255.255.0<br>
OPTION: 3 ( 4) Routers
10.0.0.2<br>
OPTION: 6 ( 8) DNS server
10.0.0.2,8.8.8.8<br>
OPTION: 12 ( 7) Host name
foobar2<br>
OPTION: 15 ( 11) Domainname
<a moz-do-not-send="true"
href="http://example.com" target="_blank">example.com</a><br>
OPTION: 26 ( 2) Interface MTU
1500<br>
OPTION: 28 ( 4) Broadcast address
10.0.0.255<br>
OPTION: 42 ( 4) NTP servers
10.0.0.32<br>
<br>
Best regards,<br>
<font color="#888888"> Dima Fadeyev</font>
<div>
<div><br>
<blockquote type="cite">hello,
<div><br>
</div>
<div> maybe it can help.... (from man
dhcp-options)</div>
<div><br>
</div>
<div><span
style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><dt>
<b style="font-weight:bold">option
dhcp-<span
style="background-color:rgb(255,204,204)">parameter</span>-request-<span
style="background-color:rgb(255,204,204)">list</span></b> <i
style="font-style:italic">uint16</i> [<b
style="font-weight:bold">,</b> <i
style="font-style:italic">uint16</i>...
]<b style="font-weight:bold">;</b></dt>
<dt>This option, when sent by the
client, specifies which options
the client wishes the server to
return. Normally, in the <span
style="background-color:rgb(255,204,204)">ISC</span> DHCP
client, this is done using the <i
style="font-style:italic">request</i> statement.
If this option is not specified
by the client, the DHCP server
will normally return every
option that is valid in scope
and that fits into the reply.
When this option is specified on
the server, the server returns
the specified options. This can
be used to force a client to
take options that it hasn't
requested, and it can also be
used to tailor the response of
the DHCP server for clients that
may need a more limited set of
options than those the server
would normally return.</dt>
<dt><br>
</dt>
<dt>regards,</dt>
<dt>laurent</dt>
</span></div>
<div><br>
<div class="gmail_quote">2011/11/23
Dima Fadeyev <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:dima@scancom.es"
target="_blank">dima@scancom.es</a>></span><br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex"> Hello
everyone,<br>
<br>
I have a quick question. Is it
possible to make ISC dhcpd
server insert the option 61
(client id) in DHCPOFFER, in
case if it is present in
DHCPDISCOVER?<br>
The ISC dhcpd version we are
using is dhcp-4.1.1
(dhcp-4.1.1-12.P1.el6_0.4.x86_64
CentOS rpm).<br>
<br>
Thanks in advance<br>
<font color="#888888"> <br>
-- <br>
Dima Fadeyev<br>
<br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:dhcp-users@lists.isc.org"
target="_blank">dhcp-users@lists.isc.org</a><br>
<a moz-do-not-send="true"
href="https://lists.isc.org/mailman/listinfo/dhcp-users"
target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</font></blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
dhcp-users mailing list
<a moz-do-not-send="true" href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a>
<a moz-do-not-send="true" href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a></pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:dhcp-users@lists.isc.org"
target="_blank">dhcp-users@lists.isc.org</a><br>
<a moz-do-not-send="true"
href="https://lists.isc.org/mailman/listinfo/dhcp-users"
target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
dhcp-users mailing list
<a moz-do-not-send="true" href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a>
<a moz-do-not-send="true" href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a></pre>
</blockquote>
<br>
<br>
</div>
</div>
<font color="#888888">
<pre cols="72">--
Dima Fadeyev
Departamento de Ingeniería de Scancom S.L.</pre>
</font></div>
<br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a moz-do-not-send="true"
href="https://lists.isc.org/mailman/listinfo/dhcp-users"
target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
<br>
<pre class="moz-signature" cols="72">--
Dima Fadeyev
Departamento de Ingeniería de Scancom S.L.</pre>
</body>
</html>