<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: problems configuring option 120</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Hi all,<BR>
<BR>
I have progressed in the option 120 configuration. My dhcpd.conf now is like that:<BR>
<BR>
<BR>
option sip-servers code 120 = { integer 8, ip-address };<BR>
<BR>
subnet 192.168.xx.xx netmask 255.255.255.0 {<BR>
<BR>
option routers 192.168.xx.xx;<BR>
option subnet-mask 255.255.255.0;<BR>
option broadcast-address 192.168.xx.xx;<BR>
option domain-name "xxxxxxxxxx";<BR>
option domain-name-servers 192.168.xx.xx;<BR>
option sip-servers 1 10.1.3.201;<BR>
default-lease-time 3600;<BR>
max-lease-time 86400;<BR>
ddns-update-style none;<BR>
authoritative;<BR>
log-facility local7;<BR>
<BR>
host Alice {<BR>
hardware ethernet xx:xx:xx:xx:xx:xx;<BR>
fixed-address 192.168.xx.xx;<BR>
}<BR>
host Becky {<BR>
hardware ethernet xx:xx:xx:xx:xx:xy;<BR>
fixed-address 192.168.xx.xx;<BR>
}<BR>
}<BR>
<BR>
So, restarting the dhcp server now is successful but when the client asks for the 120 option information, my dhcp server answers like this:<BR>
<BR>
Option: (t=120, l=5) SIP Servers<BR>
Option: (120) SIP Servers<BR>
length: 5<BR>
Value: 0A0103C9<BR>
<BR>
However, the client tries again to ask for the information with another DHCPINFORM although it is in the "Value" field.<BR>
Where is the problem, in my dhcp server configuration or in the client?<BR>
<BR>
Thanks in advance,<BR>
Rebeca Martinez<BR>
<BR>
-----Mensaje original-----<BR>
De: dhcp-users-bounces@lists.isc.org en nombre de David W. Hankins<BR>
Enviado el: lun 07/12/2009 21:28<BR>
Para: Users of ISC DHCP<BR>
Asunto: Re: problems configuring option 120<BR>
<BR>
On Mon, Dec 07, 2009 at 11:13:44AM +0100, "Martínez García, Rebeca" wrote:<BR>
> option sip-servers code 120 = ip-address;<BR>
<BR>
The indentation tells me you put this in your subnet {} clause or<BR>
similar. This is a declaration of the option's format, it has to be<BR>
globally scoped as the warning tries to say;<BR>
<BR>
> /etc/dhcp3/dhcpd.conf line 14: option definitions may not be scoped.<BR>
> option sip-servers code<BR>
> ^<BR>
<BR>
However, the SIP-Servers option declared on code 120 (RFC 3361) shows<BR>
a "conditional format" key on the first octet, so the syntax you have<BR>
declared would not be compatible with RFC 3361.<BR>
<BR>
To make it compatible you'll need an unsigned 8 bit integer ahead of<BR>
the IP address array, and then declare a 1 value for the encoding byte<BR>
to use the IP-address format (0 is FQDN).<BR>
<BR>
These conditional formats are hard to implement...<BR>
<BR>
--<BR>
David W. Hankins BIND 10 needs more DHCP voices.<BR>
Software Engineer There just aren't enough in our heads.<BR>
Internet Systems Consortium, Inc. <A HREF="http://bind10.isc.org/">http://bind10.isc.org/</A><BR>
_______________________________________________<BR>
dhcp-users mailing list<BR>
dhcp-users@lists.isc.org<BR>
<A HREF="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>