[Kea-users] PXE boot

Thomas Andersen than at itu.dk
Thu Apr 14 18:44:57 UTC 2016


Thanks Ola,

I appreciate all the help i can get.
I do see that KEA has next-server as config value for the subnet4: "next-server": “192.168.30.80”,
So I guess i only have to figure out the filename part then.

Br,
Thomas




On 14/04/16 20:34, "kea-users-bounces at lists.isc.org on behalf of Ola Thoresen" <kea-users-bounces at lists.isc.org on behalf of ola at nytt.no> wrote:

>Ti get PXE working, you basically just have to send the right Option 67 
>and 68 - the two lines with "next-server" and "filename" in your config.
>The res, I believe, is legacy.
>
>So what you need to do in Kea is to add a class matching the pxeclients 
>and in that class set the correct values for Option 67 and 68.
>
>Unfortunately I don't have the time right now to create the exact config 
>for you, but I hope this will get you one step further.
>
>
>Rgds.
>
>/Ola (T)
>
>
>On 14. april 2016 18:44, Thomas Andersen wrote:
>> Hi Marcin,
>>
>> Thank you for responding.
>> Sadly, my personal experience with PXE/bootp is rather limited.
>> I will read up on what you sent.
>>
>> This is the working PXE config from our old dhcp server.
>>
>> I am unsure how much of this is legacy and is not needed.
>>
>> ----------------------------------------------
>> option space PXE;
>> option PXE.mtftp-ip code 1 = ip-address;
>> option PXE.mtftp-cport code 2 = unsigned integer 16;
>> option PXE.mtftp-sport code 3 = unsigned integer 16;
>> option PXE.mtftp-tmout code 4 = unsigned integer 8;
>> option PXE.mtftp-delay code 5 = unsigned integer 8;
>> option PXE.discovery-control code 6 = unsigned integer 8;
>> option PXE.discovery-mcast-addr code 7 = ip-address;
>> option PXE.boot-server code 8 = { unsigned integer 16,unsigned integer 8,ip-address };
>> option PXE.boot-menu code 9 = { unsigned integer 16,unsigned integer 8,text};
>> option PXE.menu-prompt code 10 = { unsigned integer 8, text };
>>
>> class "pxeclients" {
>> 	match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
>> 	next-server 192.168.30.80; #CAPA installer
>> 	filename "CIPCC.0"; #CAPA # Boot file
>> 	option dhcp-parameter-request-list 60,43,1,15,3,6,44,46,47,31,33,43; #CAPA
>> 	vendor-option-space PXE; #CAPA
>> }
>> -----------------------------------------------
>>
>>
>> I can see from the KEA debug packet log that it do get the packets:
>> 2016-04-14 15:21:38.424 DEBUG [kea-dhcp4.packets/7877] DHCP4_QUERY_DATA [hwtype=1 10:60:4b:49:4d:ad], cid=[no info], tid=0x4b494dad, packet details: local_address=192.168.30.10:67, remote_adress=10.28.4.1:67, msg_type=DHCPDISCOVER (1), transid=0x4b494dad,
>> options:
>>    type=053, len=001: 1 (uint8)
>>    type=055, len=036: 1(uint8) 2(uint8) 3(uint8) 4(uint8) 5(uint8) 6(uint8) 11(uint8) 12(uint8) 13(uint8) 15(uint8) 16(uint8) 17(uint8) 18(uint8) 22(uint8) 23(uint8) 28(uint8) 40(uint8) 41(uint8) 42(uint8) 43(uint8) 50(uint8) 51(uint8) 54(uint8) 58(uint8) 59(uint8) 60(uint8) 66(uint8) 67(uint8) 128(uint8) 129(uint8) 130(uint8) 131(uint8) 132(uint8) 133(uint8) 134(uint8) 135(uint8)
>>    type=057, len=002: 1260 (uint16)
>>    type=060, len=032: "PXEClient:Arch:00000:UNDI:002001" (string)
>>    type=082, len=012:,
>> options:
>>      type=001, len=002: 00:36
>>      type=002, len=006: f0:92:1c:41:0d:00
>>    type=093, len=002: 0(uint16)
>>    type=094, len=003: 1 (uint8) 2 (uint8) 1 (uint8)
>>    type=097, len=017: 0 (uint8) F3EF2B7CB91CE21190538464B900003F (binary)
>>
>>
>>
>>
>>
>> Br,
>> Thomas
>>
>>
>> On 14/04/16 18:31, "Marcin Siodelski" <marcin at isc.org> wrote:
>>
>>> Hi Thomas,
>>>
>>> Thanks for your inquiry. Although, it is not explicitly titled "PXE boot
>>> configuration" the following chapter:
>>> http://git.kea.isc.org/~tester/kea/guide/kea-guide.html#classify of Kea
>>> Administrator's Manual provides a set of information about the use of
>>> (basic) classification in Kea 1.0.0, which was added to address some PXE
>>> boot scenarios.
>>>
>>> If a particular deployment requires some very specific/advanced behavior
>>> we recommend creating a hook application which is loaded and used by the
>>> Kea server to do what is needed. More information about creation of
>>> hooks can be found here:
>>>
>>> http://git.kea.isc.org/~tester/kea/doxygen/df/d46/hooksdgDevelopersGuide.html
>>>
>>> Sorry for only a brief answer to your email. If you have some specific
>>> questions, or can provide some more details about the PXE configuration
>>> you require, please let us know. In particular, if you have isc-dhcp
>>> configuration you were using for PXE boot, that may be useful for us to
>>> understand what you're trying to achieve and how it can be done in Kea.
>>> That would also help us understand where we have deficiencies in our
>>> documentation.
>>>
>>> Please expect any answers not earlier than next week, because many
>>> people travel or have day off on Friday.
>>>
>>> Marcin Siodelski
>>> ISC
>>>
>>> On 13.04.2016 15:19, Thomas Andersen wrote:
>>>> Hi,
>>>> I’ve replaced our old dhcp (isc) server with kea, and completely missed
>>>> all the PXE settings in the old config. :)
>>>> How is it configured in kea? I can’t seem to find it in the documentation.
>>>> Any pointers?
>>>> Br,
>>>> Thomas
>>>> _______________________________________________
>>>> Kea-users mailing list
>>>> Kea-users at lists.isc.org
>>>> https://lists.isc.org/mailman/listinfo/kea-users
>>
>>
>>
>>
>> On 14/04/16 18:31, "Marcin Siodelski" <marcin at isc.org> wrote:
>>
>>> Hi Thomas,
>>>
>>> Thanks for your inquiry. Although, it is not explicitly titled "PXE boot
>>> configuration" the following chapter:
>>> http://git.kea.isc.org/~tester/kea/guide/kea-guide.html#classify of Kea
>>> Administrator's Manual provides a set of information about the use of
>>> (basic) classification in Kea 1.0.0, which was added to address some PXE
>>> boot scenarios.
>>>
>>> If a particular deployment requires some very specific/advanced behavior
>>> we recommend creating a hook application which is loaded and used by the
>>> Kea server to do what is needed. More information about creation of
>>> hooks can be found here:
>>>
>>> http://git.kea.isc.org/~tester/kea/doxygen/df/d46/hooksdgDevelopersGuide.html
>>>
>>> Sorry for only a brief answer to your email. If you have some specific
>>> questions, or can provide some more details about the PXE configuration
>>> you require, please let us know. In particular, if you have isc-dhcp
>>> configuration you were using for PXE boot, that may be useful for us to
>>> understand what you're trying to achieve and how it can be done in Kea.
>>> That would also help us understand where we have deficiencies in our
>>> documentation.
>>>
>>> Please expect any answers not earlier than next week, because many
>>> people travel or have day off on Friday.
>>>
>>> Marcin Siodelski
>>> ISC
>>>
>>> On 13.04.2016 15:19, Thomas Andersen wrote:
>>>> Hi,
>>>>
>>>> I’ve replaced our old dhcp (isc) server with kea, and completely missed
>>>> all the PXE settings in the old config. :)
>>>> How is it configured in kea? I can’t seem to find it in the documentation.
>>>>
>>>> Any pointers?
>>>>
>>>> Br,
>>>> Thomas
>>>>
>>>>
>>>> _______________________________________________
>>>> Kea-users mailing list
>>>> Kea-users at lists.isc.org
>>>> https://lists.isc.org/mailman/listinfo/kea-users
>>>>
>> _______________________________________________
>> Kea-users mailing list
>> Kea-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/kea-users
>
>_______________________________________________
>Kea-users mailing list
>Kea-users at lists.isc.org
>https://lists.isc.org/mailman/listinfo/kea-users


More information about the Kea-users mailing list