Problem with custom variable in bootfile-name

[Thomas Novin]

>You should be able to do it this way:
>
>  option X-model code 254 = string;
>
>  if option vendor-class-identifier ~= "OS6450-48" {
>      option X-model "6450-48";
>  }
>  
>  option bootfile-name = concat("instruction/", config-option X-model,
>".alu²);
>
>This is what we're using to hand out subnet specific bootfile-names. In
>our case the config-option is set in each subnet and the option value is
>set in a global class that matches on vendor-class-identifier.
>
>The code points 224 through 254 are "private use". Beware that certain
>systems make use of these, e.g. Windows using code 252 for WPAD related
>configuration.
>
>-- 
>Peter


Thanks! Worked perfectly.

Rgds//Thomas