Using "vendor-encapsulated-options" in dhcpd

[Victor Soriano]

All,

A colleague found a syntax error in my one example dhcpcd.conf. I used:

vendor-encapsulated-options 06:00:01:02:03:04:05:06

when I should have used:

option vendor-encapsulated-options 06:00:01:02:03:04:05:06

However, I tried this and still no luck. Again, any help would be appreciated.

-Vic


On 5/9/07, Victor Soriano <bigblk150 at gmail.com> wrote:
> Hello all,
>
> New to the list, and I searched the archive for the following
> question(s) and didn't find anything, so please don't flame me too
> hard :)
>
> I'm trying to configure dhcpd V3.0pl1 to transmit DHCP option code
> 125, defined as a Vendor-Identifying, Vendor-Specific option as per
> RFC 3925, along with a proprietary buffer. For now, I need this buffer
> to ALWAYS be sent out in the DHCP server's messages, regardless of the
> client.
>
> First, does this option correspond to using the
> "vendor-encapsulated-options" option in dhcpd.conf? If not, how can I
> have the DHCP server send a buffer with this option?
>
> If using "vendor-encapsulated-options" is correct, how should it be
> used in the file? I have tried the following dhcpd.conf as a test and
> never see the server include this option in its messages.
>
> ----------
> ddns-update-style ad-hoc;
>
> subnet 192.168.0.0 netmask 255.255.255.0 {
>         get-lease-hostnames true;
>         authoritative;
>         default-lease-time 86400;
>         max-lease-time 86400;
>
>         option domain-name "hans-eth0";
>         option domain-name-servers 192.168.0.1;
>         option routers 192.168.0.1;
>         option ntp-servers 192.168.0.1;
>         vendor-encapsulated-options 06:00:01:02:03:04:05;
>
>         host hans.hans-eth0 {
>                 fixed-address 192.168.0.1;
>                 hardware ethernet 00:00:d1:ee:41:70;
>         }
>
>         host franz.hans-eth0 {
>                 fixed-address 192.168.0.2;
>                 hardware ethernet 00:07:e9:09:be:fe;
>         }
>
>         host greta.hans-eth0 {
>                 fixed-address 192.168.0.200;
>                 hardware ethernet 04:4b:80:80:80:03;
>         }
>
>         host bertha.hans-eth0 {
>                 fixed-address 192.168.0.201;
>                 hardware ethernet 04:4b:80:80:80:04;
>         }
>
>         pool {
>                 range 192.168.0.100 192.168.0.199;
>         }
> }
> ----------
>
> I also tried defining an option space, using a buffer more like what I
> really need, with no luck:
>
> ----------
> ddns-update-style ad-hoc;
>
> option space TEST;
> option TEST.oid code 1 = text;
> option TEST.sn code 2 = text;
> option TEST.class code 3 = text;
>
> option TEST.oid "112233";
> option TEST.sn "11:22:33:44:55:66";
> option TEST.class "test";
>
> subnet 192.168.0.0 netmask 255.255.255.0 {
>         get-lease-hostnames true;
>         authoritative;
>         default-lease-time 86400;
>         max-lease-time 86400;
>
>         option domain-name "hans-eth0";
>         option domain-name-servers 192.168.0.1;
>         option routers 192.168.0.1;
>         option ntp-servers 192.168.0.1;
>         vendor-option-space TR111;
>
>         host hans.hans-eth0 {
>                 fixed-address 192.168.0.1;
>                 hardware ethernet 00:00:d1:ee:41:70;
>         }
>
>         host franz.hans-eth0 {
>                 fixed-address 192.168.0.2;
>                 hardware ethernet 00:07:e9:09:be:fe;
>         }
>
>         host greta.hans-eth0 {
>                 fixed-address 192.168.0.200;
>                 hardware ethernet 04:4b:80:80:80:03;
>         }
>
>         host bertha.hans-eth0 {
>                 fixed-address 192.168.0.201;
>                 hardware ethernet 04:4b:80:80:80:04;
>         }
>
>         pool {
>                 range 192.168.0.100 192.168.0.199;
>         }
> }
> ----------
>
> Any help on how to get this up and running would be greatly appreciated.
>
> Thanks,
> Victor Soriano
> Sr. Software Engineer
> LSI Corporation
>