Problem with custom variable in bootfile-name

[Thomas Novin]

>>         if option vendor-class-identifier ~= "OS6450-48" {
>>                 set model = "6450-48";
>>         }
>>
>>         option bootfile-name = concat("instruction/", model, ".alu”);
>>
>
>If I use the variable in a execute-statement, it works having a mix of variables and text. Without using concat. But that does not work in an option.
>
>For example:
>
>                execute ("/usr/local/bin/create_instruction", model);
>
>I have tested skipping concat in bootfile-name but that did not work. But why is it not possible to use a set variable in an option-statement.. if anyone can answer this I’d be thankful!

Above I used ‘set model = “6450-48”’. I have also tried just ‘model = “6450-48”;’ but the same result, the server starts fine but it does not send any bootfile-name. So the concat probably evaluates the variable as empty and because of this the whole concat returns null.

>>One one more strangeness: dhcpd does NOT send the configured domain-name, can that depend on the client, whether it requests it or not?

I fixed this by forcing the option on the client:

        # 1=subnet, 3=router, 12=hostname, 15=domain-name, 66=tftp-server-name, 67=bootfile-name
        option dhcp-parameter-request-list 1,3,12,15,66,67;

Rgds//Thomas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150623/d607a953/attachment.html>