Does Linux DHCP server support OPTION 122?

Hello

I'm now studying PacketCable.

The PacketCable VoIP Client Configuration DHCP option contains configuration
information for MTA devices, which is sent by the DHCP server to the MTA
device. This option consists of a series of sub-options that contain
different types of data and configuration for the MTA device. In March 2003,
RFC 3495 standardized this DHCP option as 122.

Please take a look at the following links.
http://www.networksorcery.com/enp/pr...tp/options.htm
http://www.networksorcery.com/enp/rfc/rfc3495.txt

However, I didn't know how to add this option in the dhcpd.conf after I
reading the following document.
http://leaf.sourceforge.net/devel/jn...p-options.html

Does anybody know a solution?

Thanks

Hans

Are there anybody know how to support bootp OPTION 122 in the DHCP server of
Linux?

Hans

"Hans Ren" <renht@lucent.com> wrote in message
news:c21gua$e34@netnews.proxy.lucent.com...
> Hello
>
> I'm now studying PacketCable.
>
> The PacketCable VoIP Client Configuration DHCP option contains
configuration
> information for MTA devices, which is sent by the DHCP server to the MTA
> device. This option consists of a series of sub-options that contain
> different types of data and configuration for the MTA device. In March
2003,
> RFC 3495 standardized this DHCP option as 122.
>
> Please take a look at the following links.
> http://www.networksorcery.com/enp/pr...tp/options.htm
> http://www.networksorcery.com/enp/rfc/rfc3495.txt
>
> However, I didn't know how to add this option in the dhcpd.conf after I
> reading the following document.
> http://leaf.sourceforge.net/devel/jn...p-options.html
>
> Does anybody know a solution?
>
> Thanks
>
> Hans
>
>

[Followups set to COLN]

In comp.os.linux.networking Hans Ren <renht@lucent.com> wrote:
> Are there anybody know how to support bootp OPTION 122 in the DHCP server of
> Linux?

Certainly, its quite easy once you've seen it the first time. IIRC, you
will require DHCPv3 if you're using the standard ISC software. Here is
an example. It's not the option you want, its taken from my terminal
server at work that uses Etherboot.

option etherboot-magic code 128 = string;
option nic-settings code 129 = text;
option menu-options code 160 = text;
option menu-entry-1 code 192 = text;
option menu-entry-2 code 193 = text;
option menu-entry-3 code 194 = text;
option menu-entry-4 code 195 = text;
option menu-entry-5 code 196 = text;
option wpad code 252 = string;

subnet 192.168.1.0 netmask 255.255.255.0 {
option wpad "http://medussa.localdomain/wpad.dat";

...
}

subnet 192.168.3.0 netmask 255.255.255.0 {
...

group {
filename "/tftpboot/lts/vmlinuz-2.4.9-ltsp-5";
next-server medussa.xterms;
use-host-decl-names on;
option root-path "192.168.3.1:/opt/ltsp/i386";
option log-servers 192.168.3.1;

option etherboot-magic e4:45:74:68:00:00;

option menu-options "timeout=30";
option menu-entry-1 "X-Terminal:::-:::";
option menu-entry-2 "First Hard Disk:::/dev/hda:::";
option menu-entry-3 "Install Slackware Linux 8.1:::slack81inst.nb:::";
option menu-entry-5 "System Imager:::systemimager.nb:::";
}



>
> Hans
>
> "Hans Ren" <renht@lucent.com> wrote in message
> news:c21gua$e34@netnews.proxy.lucent.com...
>> Hello
>>
>> I'm now studying PacketCable.
>>
>> The PacketCable VoIP Client Configuration DHCP option contains
> configuration
>> information for MTA devices, which is sent by the DHCP server to the MTA
>> device. This option consists of a series of sub-options that contain
>> different types of data and configuration for the MTA device. In March
> 2003,
>> RFC 3495 standardized this DHCP option as 122.
>>
>> Please take a look at the following links.
>> http://www.networksorcery.com/enp/pr...tp/options.htm
>> http://www.networksorcery.com/enp/rfc/rfc3495.txt
>>
>> However, I didn't know how to add this option in the dhcpd.conf after I
>> reading the following document.
>> http://leaf.sourceforge.net/devel/jn...p-options.html
>>
>> Does anybody know a solution?
>>
>> Thanks
>>
>> Hans
>>
>>
>
>

--
Cameron Kerr
cameron.kerr@paradise.net.nz : http://nzgeeks.org/cameron/
Empowered by Perl!

Cameron

Thank you very much for your help.

It seems that OPTION 122 can be supported by adding one line in dhcpd.conf.
"option CableLabs-Client-Configuration code 122 = string;"

But how to add suboptions under OPTION 122?
For example, if I want to add suboption 1, shall I add
"option CableLabs-Client-Configuration.Primary-DHCP-Server code 1 =
ip-address;"
and it will be quoted by "option
CableLabs-Client-Configuration.Primary-DHCP-Server"?

Or it can be just quoted by "option CableLabs-Client-Configuration.1"?

I'll do a test when I got a Linux Machine.

Hans


"Cameron Kerr" <cameron.kerr@paradise.net.nz> wrote in message
news:4046afc4@news.maxnet.co.nz...
[Followups set to COLN]


Certainly, its quite easy once you've seen it the first time. IIRC, you
will require DHCPv3 if you're using the standard ISC software. Here is
an example. It's not the option you want, its taken from my terminal
server at work that uses Etherboot.

option etherboot-magic code 128 = string;
option nic-settings code 129 = text;
option menu-options code 160 = text;
option menu-entry-1 code 192 = text;
option menu-entry-2 code 193 = text;
option menu-entry-3 code 194 = text;
option menu-entry-4 code 195 = text;
option menu-entry-5 code 196 = text;
option wpad code 252 = string;

subnet 192.168.1.0 netmask 255.255.255.0 {
option wpad "http://medussa.localdomain/wpad.dat";

...
}

subnet 192.168.3.0 netmask 255.255.255.0 {
...

group {
filename "/tftpboot/lts/vmlinuz-2.4.9-ltsp-5";
next-server medussa.xterms;
use-host-decl-names on;
option root-path "192.168.3.1:/opt/ltsp/i386";
option log-servers 192.168.3.1;

option etherboot-magic e4:45:74:68:00:00;

option menu-options "timeout=30";
option menu-entry-1 "X-Terminal:::-:::";
option menu-entry-2 "First Hard Disk:::/dev/hda:::";
option menu-entry-3 "Install Slackware Linux 8.1:::slack81inst.nb:::";
option menu-entry-5 "System Imager:::systemimager.nb:::";
}