Poll: All DHCP options in script are usefull? This poll is closed. |
|||
Agree, please build it. | 0 | 0% | |
Not usefull at all. | 1 | 100.00% | |
Total | 1 vote(s) | 100% |
* You voted for this item. | [Show Results] |
DHCP command incomplete
|
2011-12-20, 19:08
Post: #1
|
|||
|
|||
DHCP command incomplete
Hi, i found that ipxe when using dhcp in a script does reject all dhcp-options that are not used by ipxe. My request is that it does not reject them because you can make good use of them in script. Let me give an example:
#!ipxe dhcp isset ${224} && ${224} autoboot This script does not work because option 224 is rejected by ipxe. If it would not be rejected it would do: 1 a dhcp request 2 when option 224 would contain a valid command it would execute this command. 3 when there is nothing in option 224 it would autoboot. You can test my idea by replacing ${224} with ${initiator-iqn} and put something usefull in your dhcp server sanboot string option like "chain http://myserver/boot.php". Only thing is we don't want to use ${initiator-iqn} for this but some user defined options (224 to 254). So my idea is when you do a dhcp request make sure ALL (0-255) the dhcp-options you get from the dhcp server are available in script. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
DHCP command incomplete - lstraath - 2011-12-20 19:08
RE: DHCP command incomplete - mcb30 - 2011-12-20, 20:25
RE: DHCP command incomplete - lstraath - 2011-12-21, 07:33
|
User(s) browsing this thread: 1 Guest(s)