Re: [gPXE] How to modify the code can not get DHCP information on the2nd
Good day sqwbwh,
I'm sorry that it didn't seem to work. I guess that you have to use an
embedded script in gpxe.kkpxe, after all.
#!gpxe
set use-cached 1
dhcp net0
sanboot ${root-path}
I hope this works.
- Shao Miller
___
gPXE mailing list
gPXE@etherboot.org
http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
2010/11/6 sqwbwh sqw...@126.com: Gene Cumm thank you let I see reasons for this situation occurs. Want to solve this problem. How to do that? Forcing your DHCP server to always return option 17 is application specific. http://etherboot.org/wiki/howtos#how_to_use_advanced_dhcp_options http://etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration#original_dhcpd_setup This person forcibly appended 3a and 3b to dhcp-parameter-request-list. This is what you'll need to do. I think it's a single byte in hex so 11 should be your option 17 decimal. -- -Gene At 2010-11-07 02:49:03，Gene Cumm gene.c...@gmail.com wrote: 2010/11/6 sqwbwh sqw...@126.com: Miller, Shao use Embedded script #!gpxe set use-cached 1 GPXE not have access to 017 settings How can either use the set use-cached 1 Also get 017 information? Your native PXE client probably did not request it and/or ignored it when storing the cached DHCP packets. If you do a packet capture (very easy in a hosted VMware environment), I'd guess you probably won't see option 17 in the response from the server. It is possible to configure some DHCP servers to always return certain options. However, when you don't set use-cached 1, the DHCP server is probably sending it because gPXE is probably requesting it. info: Dhcp server set up in the 017 options iscsi: 192.168.0.222:: 3260:: test I set it in an embedded script: #!gpxe set use-cached 1 autoboot please see 0171.jpg -0172.jpg root-path is nothing 0172.jpg is add script : #!gpxe set use-cached 1 config - normal.jpg is no script At 2010-11-05 21:13:33，Miller, Shao shao.mil...@yrdsb.edu.on.ca wrote: From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] on behalf of sqwbwh Sent: Friday, November 05, 2010 09:05 To: GPXE Mailing List Subject: [gPXE] How to modify the code can not get DHCP information on the2nd How to modify the code can not get DHCP information on the 2nd?(GPXE only used to boot the system from ISCSI) Is to remove this step. net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN) [Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0] DHCP (net0 00:0 c: 29:08:11: d5 ) ok net0: 192.168.0.202/255.255.255.0 This can speed up boot speed. Normal GPXE run to start from the boot system tftp process takes about 8 seconds or so If removed from the second time for DHCP information will only need a very quick 2.5 seconds. - You most likely want the 'use-cached' option. It is DHCP gPXE encapsulated option number 178. Or, you can set it in an embedded script: #!gpxe set use-cached 1 autoboot - Shao Miller ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
2010/11/7 sqwbwh sqw...@126.com: Gene Cumm Forcing your DHCP server to always return option 17 is application specific. MSDHCP always return option 17 is application specific What practices can explain it in detail? -2003 http://technet.microsoft.com/en-us/library/cc778368%28WS.10%29.aspx -2008 http://technet.microsoft.com/en-us/library/cc755282.aspx Or find the equivalent page in your preferred language. Unfortunately, I have no idea if it's possible to force MS-DHCP to do this. You could put the option into a gPXE script and embed it into your gPXE binary. -- -Gene At 2010-11-07 19:26:31，Gene Cumm gene.c...@gmail.com wrote: 2010/11/6 sqwbwh sqw...@126.com: Gene Cumm thank you let I see reasons for this situation occurs. Want to solve this problem. How to do that? Forcing your DHCP server to always return option 17 is application specific. http://etherboot.org/wiki/howtos#how_to_use_advanced_dhcp_options http://etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration#original_dhcpd_setup This person forcibly appended 3a and 3b to dhcp-parameter-request-list. This is what you'll need to do. I think it's a single byte in hex so 11 should be your option 17 decimal. -- -Gene At 2010-11-07 02:49:03，Gene Cumm gene.c...@gmail.com wrote: 2010/11/6 sqwbwh sqw...@126.com: Miller, Shao use Embedded script #!gpxe set use-cached 1 GPXE not have access to 017 settings How can either use the set use-cached 1 Also get 017 information? Your native PXE client probably did not request it and/or ignored it when storing the cached DHCP packets. If you do a packet capture (very easy in a hosted VMware environment), I'd guess you probably won't see option 17 in the response from the server. It is possible to configure some DHCP servers to always return certain options. However, when you don't set use-cached 1, the DHCP server is probably sending it because gPXE is probably requesting it. info: Dhcp server set up in the 017 options iscsi: 192.168.0.222:: 3260:: test I set it in an embedded script: #!gpxe set use-cached 1 autoboot please see 0171.jpg -0172.jpg root-path is nothing 0172.jpg is add script : #!gpxe set use-cached 1 config - normal.jpg is no script At 2010-11-05 21:13:33，Miller, Shao shao.mil...@yrdsb.edu.on.ca wrote: From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] on behalf of sqwbwh Sent: Friday, November 05, 2010 09:05 To: GPXE Mailing List Subject: [gPXE] How to modify the code can not get DHCP information on the2nd How to modify the code can not get DHCP information on the 2nd?(GPXE only used to boot the system from ISCSI) Is to remove this step. net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN) [Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0] DHCP (net0 00:0 c: 29:08:11: d5 ) ok net0: 192.168.0.202/255.255.255.0 This can speed up boot speed. Normal GPXE run to start from the boot system tftp process takes about 8 seconds or so If removed from the second time for DHCP information will only need a very quick 2.5 seconds. - You most likely want the 'use-cached' option. It is DHCP gPXE encapsulated option number 178. Or, you can set it in an embedded script: #!gpxe set use-cached 1 autoboot - Shao Miller ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
Miller, Shao MY native language chinese thanks -sqwbwh At 2010-11-08 05:05:40，Miller, Shao shao.mil...@yrdsb.edu.on.ca wrote: Is there anyone willing to help with translation in this thread of discussion? If so, that'd be great. May I please ask what your native language is, sqwbwh? In the meanwhile, I'll try with just key-words... sqwbwh: Filename. DHCP option 67. - ? Please try: netsh dhcp server \\dhcpserver dump my_dhcp.txt Send e-mail with 'my_dhcp.txt' attached. - Shao Miller # == # ·þÎñÆ÷ 192.168.0.200 µÄÅäÖÃÐÅÏ¢ # == # = # Add Classes # = Dhcp Server 192.168.0.200 Add Class ĬÈÏ·ÓɺÍÔ¶³Ì·ÃÎÊÀà±ð Ô¶³Ì·ÃÎÊ¿Í»§¶ËµÄÓû§Àà±ð 525241532e4d6963726f736f6674 0 b Dhcp Server 192.168.0.200 Add Class ĬÈÏ BOOTP µÄÀà±ð BOOTP ¿Í»§¶ËµÄÓû§Àà±ð 424f4f54502e4d6963726f736f6674 0 b Dhcp Server 192.168.0.200 Add Class Microsoft Windows 2000 Ñ¡Ïî Windows 2000 ¿Í»§¶ËµÄ Microsoft ¹©Ó¦ÉÌÌض¨Ñ¡Ïî 4d53465420352e30 1 b Dhcp Server 192.168.0.200 Add Class Microsoft Windows 98 Ñ¡Ïî Windows 98 ¿Í»§¶ËµÄ Microsoft ¹©Ó¦ÉÌÌض¨Ñ¡Ïî 4d534654203938 1 b Dhcp Server 192.168.0.200 Add Class Microsoft Ñ¡Ïî ÊÊÓÃÓÚ Windows 98 ºÍ Windows 2000 ¿Í»§¶ËµÄ Microsoft ¹©Ó¦ÉÌÌض¨Ñ¡Ïî 4d534654 1 b Dhcp Server 192.168.0.200 Add Class gPXE gPXE 67505845 0 b # = # Add Classes ½áÊø # = # = # Add Optiondef # = Dhcp Server 192.168.0.200 Add Optiondef 249 ÎÞÀà±ð¾²Ì¬Â·ÓÉ BINARY 0 comment=Ä¿±ê£¬ÑÚÂëºÍ·ÓÉÆ÷ IP µØÖ·£¬°´ÓÅÏÈ˳ÐòÅÅÁÐ Dhcp Server 192.168.0.200 Add Optiondef 1 ×ÓÍøÑÚÂë IPADDRESS 0 comment=ÒÔÍøÂç×Ö½ÚÅÅÁеÄ×ÓÍøÑÚÂë 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 2 ʱ¼äÆ«ÒÆ DWORD 0 comment=UCT Æ«ÒÆ(ÒÔÃë¼Æ) 0 Dhcp Server 192.168.0.200 Add Optiondef 3 ·ÓÉÆ÷ IPADDRESS 1 comment=°´Ê×Ñ¡ÏîÅÅÐòµÄ·ÓÉÆ÷µØÖ·ÕóÁÐ 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 4 ʱ¼ä·þÎñÆ÷ IPADDRESS 1 comment=°´Ê×Ñ¡ÏîÅÅÐòµÄʱ¼ä·þÎñÆ÷µØÖ·ÕóÁÐ 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 5 Ãû³Æ·þÎñÆ÷ IPADDRESS 1 comment=°´Ê×Ñ¡ÏîÅÅÁеÄÃû³Æ·þÎñÆ÷ÕóÁÐ[IEN 116] 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 6 DNS ·þÎñÆ÷ IPADDRESS 1 comment=°´Ê×Ñ¡ÏîÅÅÐòµÄ DNS ·þÎñÆ÷ÕóÁÐ 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 7 ÈÕÖ¾·þÎñÆ÷ IPADDRESS 1 comment=×ÓÍøÉ쵀 MIT_LCS UDP ÈÕÖ¾·þÎñÆ÷ÕóÁÐ 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 8 Cookie ·þÎñÆ÷ IPADDRESS 1 comment=Cookie ·þÎñÆ÷ÕóÁУ¬RFC 865 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 9 LPR ·þÎñÆ÷ IPADDRESS 1 comment=°´Ê×Ñ¡ÏîÅÅÐòµÄ RFC 1179 ·þÎñÆ÷ÕóÁÐ 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 10 Impress ·þÎñÆ÷ IPADDRESS 1 comment=Imagen Impress ·þÎñÆ÷ÕóÁÐ 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 11 ×ÊÔ´¶¨Î»·þÎñÆ÷ IPADDRESS 1 comment=°´Ê×Ñ¡ÏîÅÅÐòµÄ×ÓÍøÉ쵀 RFC 887 ResLoc ·þÎñÆ÷ÕóÁÐ 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 12 Ö÷»úÃû STRING 0 comment=¿Í»§¶ËµÄÖ÷»úÃû£¬RFC 1035 ×Ö·û¼¯ Dhcp Server 192.168.0.200 Add Optiondef 13 Æô¶¯Îļþ´óС WORD 0 comment=Æô¶¯Ó³ÏñÎļþµÄ´óС(ÒÔ 512 ×Ö½Ú¿éΪµ¥Î») 0 Dhcp Server 192.168.0.200 Add Optiondef 14 ÏÖ³¡×ª´¢Îļþ STRING 0 comment=¹ÊÕÏת´¢ÎļþµÄ·¾¶Ãû Dhcp Server 192.168.0.200 Add Optiondef 15 DNS ÓòÃû STRING 0 comment=¿Í»§¶ËµÄ DNS ÓòÃû½âÎö Dhcp Server 192.168.0.200 Add Optiondef 16 ½»»»·þÎñÆ÷ IPADDRESS 0 comment=¿Í»§¶ËµÄ½»»»·þÎñÆ÷µØÖ· 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 17 ¸ù·¾¶ STRING 0 comment=¿Í»§¶ËµÄ¸ù´ÅÅ̵Ä·¾¶Ãû£¬×Ö·û¼¯ NVT ASCII Dhcp Server 192.168.0.200 Add Optiondef 18 À©Õ¹Â·¾¶ STRING 0 comment=Ñ¡ÏîÀ©Õ¹µÄ tftp Îļþ Dhcp Server 192.168.0.200 Add Optiondef 19 IP ²ãת·¢ BYTE 0 comment=½ûÓÃ/ÆôÓà IP Êý¾Ý°üÔÚ´Ë¿Í»§¶ËµÄת·¢ 0 Dhcp Server 192.168.0.200 Add Optiondef 20 ·Ç±¾µØµÄԴ·ÓÉ BYTE 0 comment=½ûÓÃ/ÆôÓ÷DZ¾µØµÄÊý¾Ý±¨ 0 Dhcp Server 192.168.0.200 Add Optiondef 21 ²ßÂÔɸѡÆ÷ÑÚÂë IPADDRESS 1 comment=ÓÃÓÚɸѡԴ·ÓɵÄÄ¿±ê/ÑÚÂë IP µØÖ·¶Ô 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 22 ×î´ó DG ÖØ×é´óС WORD 0 comment=¿Í»§¶ËÖØ×éµÄÊý¾Ý±¨×î´ó³ß´ç£»×î´ó 576 0 Dhcp Server 192.168.0.200 Add Optiondef 23 ĬÈ쵀 IP ´æÔÚʱ¼ä BYTE 0 comment=¹©¿Í»§¶ËÔÚ´«³öµÄ DG ÉÏʹÓõÄĬÈÏ TTL 0 Dhcp Server 192.168.0.200 Add Optiondef 24 ·¾¶ MTU ÀÏ»¯³¬Ê± DWORD 0 comment=ÔÚÊýÃëÄÚÀÏ»¯Â·¾¶ MTU Öµ½«³¬Ê±£»RFC 1191 0 Dhcp Server 192.168.0.200 Add Optiondef 25 ·¾¶ MTU Í£Öͱí WORD 1 comment=MTU ̽Ë÷´óС£¬°´´óСÅÅÐò£¬ËùÓÐ = 68 0 Dhcp Server 192.168.0.200 Add Optiondef 26 MTU Ñ¡Ïî WORD 0 comment=MTU ̽Ë÷´óС£¬= 68 0 Dhcp Server 192.168.0.200 Add Optiondef 27 ËùÓÐ×ÓÍø¾ùΪ±¾µØ BYTE 0 comment=¿Í»§¶Ë¼ÙÉèËùÓÐ×ÓÍø¾ùΪ±¾µØ 0 Dhcp Server 192.168.0.200 Add Optiondef 28 ¹ã²¥µØÖ· IPADDRESS 0 comment=¹ã²¥µØÖ· 0.0.0.0 Dhcp Server 192.168.0.200 Add Optiondef 29 Ö´ÐÐÑÚÂëËÑË÷ BYTE 0 comment=¿Í»§¶ËӦʹÓà ICMP À´ËÑË÷×ÓÍøÑÚÂë 0 Dhcp Server 192.168.0.200
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
2010/11/6 sqwbwh sqw...@126.com: Miller, Shao use Embedded script #!gpxe set use-cached 1 GPXE not have access to 017 settings How can either use the set use-cached 1 Also get 017 information? Your native PXE client probably did not request it and/or ignored it when storing the cached DHCP packets. If you do a packet capture (very easy in a hosted VMware environment), I'd guess you probably won't see option 17 in the response from the server. It is possible to configure some DHCP servers to always return certain options. However, when you don't set use-cached 1, the DHCP server is probably sending it because gPXE is probably requesting it. info: Dhcp server set up in the 017 options iscsi: 192.168.0.222:: 3260:: test I set it in an embedded script: #!gpxe set use-cached 1 autoboot please see 0171.jpg -0172.jpg root-path is nothing 0172.jpg is add script : #!gpxe set use-cached 1 config - normal.jpg is no script At 2010-11-05 21:13:33，Miller, Shao shao.mil...@yrdsb.edu.on.ca wrote: From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] on behalf of sqwbwh Sent: Friday, November 05, 2010 09:05 To: GPXE Mailing List Subject: [gPXE] How to modify the code can not get DHCP information on the2nd How to modify the code can not get DHCP information on the 2nd?(GPXE only used to boot the system from ISCSI) Is to remove this step. net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN) [Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0] DHCP (net0 00:0 c: 29:08:11: d5 ) ok net0: 192.168.0.202/255.255.255.0 This can speed up boot speed. Normal GPXE run to start from the boot system tftp process takes about 8 seconds or so If removed from the second time for DHCP information will only need a very quick 2.5 seconds. - You most likely want the 'use-cached' option. It is DHCP gPXE encapsulated option number 178. Or, you can set it in an embedded script: #!gpxe set use-cached 1 autoboot - Shao Miller -- -Gene ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
Gene Cumm thank you let I see reasons for this situation occurs. Want to solve this problem. How to do that? -sqwbwh At 2010-11-07 02:49:03，Gene Cumm gene.c...@gmail.com wrote: 2010/11/6 sqwbwh sqw...@126.com: Miller, Shao use Embedded script #!gpxe set use-cached 1 GPXE not have access to 017 settings How can either use the set use-cached 1 Also get 017 information? Your native PXE client probably did not request it and/or ignored it when storing the cached DHCP packets. If you do a packet capture (very easy in a hosted VMware environment), I'd guess you probably won't see option 17 in the response from the server. It is possible to configure some DHCP servers to always return certain options. However, when you don't set use-cached 1, the DHCP server is probably sending it because gPXE is probably requesting it. info: Dhcp server set up in the 017 options iscsi: 192.168.0.222:: 3260:: test I set it in an embedded script: #!gpxe set use-cached 1 autoboot please see 0171.jpg -0172.jpg root-path is nothing 0172.jpg is add script : #!gpxe set use-cached 1 config - normal.jpg is no script At 2010-11-05 21:13:33，Miller, Shao shao.mil...@yrdsb.edu.on.ca wrote: From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] On Behalf Of sqwbwh Sent: Friday, November 05, 2010 09:05 To: GPXE Mailing List Subject: [gPXE] How to modify the code can not get DHCP information on the2nd How to modify the code can not get DHCP information on the 2nd?(GPXE only used to boot the system from ISCSI) Is to remove this step. net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN) [Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0] DHCP (net0 00:0 c: 29:08:11: d5 ) ok net0: 192.168.0.202/255.255.255.0 This can speed up boot speed. Normal GPXE run to start from the boot system tftp process takes about 8 seconds or so If removed from the second time for DHCP information will only need a very quick 2.5 seconds. - You most likely want the 'use-cached' option. It is DHCP gPXE encapsulated option number 178. Or, you can set it in an embedded script: #!gpxe set use-cached 1 autoboot - Shao Miller -- -Gene ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] On Behalf Of sqwbwh Sent: Friday, November 05, 2010 09:05 To: GPXE Mailing List Subject: [gPXE] How to modify the code can not get DHCP information on the2nd How to modify the code can not get DHCP information on the 2nd?(GPXE only used to boot the system from ISCSI) Is to remove this step. net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN) [Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0] DHCP (net0 00:0 c: 29:08:11: d5 ) ok net0: 192.168.0.202/255.255.255.0 This can speed up boot speed. Normal GPXE run to start from the boot system tftp process takes about 8 seconds or so If removed from the second time for DHCP information will only need a very quick 2.5 seconds. - You most likely want the 'use-cached' option. It is DHCP gPXE encapsulated option number 178. Or, you can set it in an embedded script: #!gpxe set use-cached 1 autoboot - Shao Miller ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
yes thankyou Shao Miller Your method is useful ：） -sqwbwh At 2010-11-05 21:13:33，Miller, Shao shao.mil...@yrdsb.edu.on.ca wrote: From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] On Behalf Of sqwbwh Sent: Friday, November 05, 2010 09:05 To: GPXE Mailing List Subject: [gPXE] How to modify the code can not get DHCP information on the2nd How to modify the code can not get DHCP information on the 2nd?(GPXE only used to boot the system from ISCSI) Is to remove this step. net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN) [Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0] DHCP (net0 00:0 c: 29:08:11: d5 ) ok net0: 192.168.0.202/255.255.255.0 This can speed up boot speed. Normal GPXE run to start from the boot system tftp process takes about 8 seconds or so If removed from the second time for DHCP information will only need a very quick 2.5 seconds. - You most likely want the 'use-cached' option. It is DHCP gPXE encapsulated option number 178. Or, you can set it in an embedded script: #!gpxe set use-cached 1 autoboot - Shao Miller ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
sqwbwh wrote: How to modify the code can not get DHCP information on the 2nd?(GPXE only used to boot the system from ISCSI) Is to remove this step. net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN) [Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0] DHCP (net0 00:0 c: 29:08:11: d5 ) ok net0: 192.168.0.202/255.255.255.0 This can speed up boot speed. Normal GPXE run to start from the boot system tftp process takes about 8 seconds or so If removed from the second time for DHCP information will only need a very quick 2.5 seconds. Miller, Shao wrote: You most likely want the 'use-cached' option. It is DHCP gPXE encapsulated option number 178. Or, you can set it in an embedded script: #!gpxe set use-cached 1 autoboot Gene Cumm wrote: What file and version are you using? It sounds as if you're using undionly.kpxe or a .pxe file. undionly.kkpxe will skip this second DHCP request but certain hardware/firmware has issues with this, assuming you trust the stability of your OEM's PXE/UNDI stack. sqwbwh wrote: Shao Miller The method is successful. Thank you sqwbwh wrote: yes thankyou Shao Miller Your method is useful :) Miller, Shao wrote: You're quite welcome, and thanks for including the list on your other reply. :) Have a nice day. - Shao sqwbwh wrote: Shao Miller 1: i use : set it in an embedded script: #!gpxe set use-cached 1 autoboot it's good 2: It is DHCP gPXE encapsulated option number 178 Specifically to ask how to use this method? What can explain it in detail? thank~you I enjoy using the search feature at the gPXE (Etherboot) wiki. Please see: http://etherboot.org/wiki/doku.php?do=searchid=encapsulatedfulltext=Search http://etherboot.org/wiki/msdhcp http://etherboot.org/wiki/dhcpd - Shao Miller ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
sqwbwh wrote: At 2010-11-05 22:39:05，ShaoMillershao.mil...@yrdsb.edu.on.ca wrote: sqwbwh wrote: How to modify the code can not get DHCP information on the 2nd?(GPXE only used to boot the system from ISCSI) Is to remove this step. net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN) [Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0] DHCP (net0 00:0 c: 29:08:11: d5 ) ok net0: 192.168.0.202/255.255.255.0 This can speed up boot speed. Normal GPXE run to start from the boot system tftp process takes about 8 seconds or so If removed from the second time for DHCP information will only need a very quick 2.5 seconds. Miller, Shao wrote: You most likely want the 'use-cached' option. It is DHCP gPXE encapsulated option number 178. Or, you can set it in an embedded script: #!gpxe set use-cached 1 autoboot Gene Cumm wrote: What file and version are you using? It sounds as if you're using undionly.kpxe or a .pxe file. undionly.kkpxe will skip this second DHCP request but certain hardware/firmware has issues with this, assuming you trust the stability of your OEM's PXE/UNDI stack. sqwbwh wrote: Shao Miller The method is successful. Thank you sqwbwh wrote: yes thankyou Shao Miller Your method is useful ：） Miller, Shao wrote: You’re quite welcome, and thanks for including the list on your other reply. :) Have a nice day. - Shao sqwbwh wrote: Shao Miller 1: i use : set it in an embedded script: #!gpxe set use-cached 1 autoboot it's good 2: It is DHCP gPXE encapsulated option number 178 Specifically to ask how to use this method? What can explain it in detail? thank~you I enjoy using the search feature at the gPXE (Etherboot) wiki. Please see: http://etherboot.org/wiki/doku.php?do=searchid=encapsulatedfulltext=Search http://etherboot.org/wiki/msdhcp http://etherboot.org/wiki/dhcpd ShaoMiller Use the search function. Use hyperlinks to provide you with three options for the introduction of 178 not found. 178 keyword search does not find use-cached search did not find the relevant presentation. Hehe. Could you give me the answer it?. English is almost a maze for me I'm afraid that I'm not sure how to explain gPXE encapsulated options any better than they are explained in the wiki. DHCP option 175 should be a string of bytes. Within that byte sequence, there are sub-options. 'use-cached' is sub-option 178. So your DHCP option 175 could look like: 0xB2 0x01 0x01 where, 0xB2 : DHCP gPXE encapsulated option 178. 0x01 : The encapsulated option's value occupies 1 byte. 0x01 : The encapsulated option's value is 1 (true). I do not know which DHCP service you use, so I do not know how you can reconfigure your service to give PXE clients this 'use-cached' option via DHCP. - Shao Miller ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
sqwbwh wrote:
At 2010-11-05 23:13:19，ShaoMillershao.mil...@yrdsb.edu.on.ca wrote:
sqwbwh wrote:
At 2010-11-05 22:39:05，ShaoMillershao.mil...@yrdsb.edu.on.ca
wrote:
sqwbwh wrote:
How to modify the code can not get DHCP information on
the 2nd?(GPXE only used to boot the system from ISCSI)
Is to remove this step.
net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN)
[Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0]
DHCP (net0 00:0 c: 29:08:11: d5 ) ok
net0: 192.168.0.202/255.255.255.0
This can speed up boot speed.
Normal GPXE run to start from the boot system tftp
process takes about 8 seconds or so
If removed from the second time for DHCP information
will only need a very quick 2.5 seconds.
Miller, Shao wrote:
You most likely want the 'use-cached' option. It is DHCP gPXE
encapsulated option number 178. Or, you can set it in an embedded
script:
#!gpxe
set use-cached 1
autoboot
Gene Cumm wrote:
What file and version are you using? It sounds as if
you're using
undionly.kpxe or a .pxe file. undionly.kkpxe will skip
this second
DHCP request but certain hardware/firmware has issues
with this,
assuming you trust the stability of your OEM's PXE/UNDI
stack.
sqwbwh wrote:
Shao Miller
The method is successful.
Thank you
sqwbwh wrote:
yes
thankyou Shao Miller
Your method is useful ：）
Miller, Shao wrote:
You’re quite welcome, and thanks for including the list on
your other reply. :) Have a nice day. - Shao
sqwbwh wrote:
Shao Miller
1:
i use :
set it in an embedded script:
#!gpxe
set use-cached 1
autoboot
it's good
2:
It is DHCP gPXE encapsulated option number 178
Specifically to ask how to use this method?
What can explain it in detail?
thank~you
I enjoy using the search feature at the gPXE (Etherboot)
wiki. Please see:
http://etherboot.org/wiki/doku.php?do=searchid=encapsulatedfulltext=Search
http://etherboot.org/wiki/msdhcp
http://etherboot.org/wiki/dhcpd
ShaoMiller
Use the search function.
Use hyperlinks to provide you with three options for the
introduction of 178 not found.
178 keyword search does not find use-cached search did not find
the relevant presentation.
Hehe. Could you give me the answer it?. English is almost a maze
for me
I'm afraid that I'm not sure how to explain gPXE encapsulated
options any better than they are explained in the wiki. DHCP
option 175 should be a string of bytes. Within that byte sequence,
there are sub-options. 'use-cached' is sub-option 178. So your
DHCP option 175 could look like:
0xB2 0x01 0x01
where,
0xB2 : DHCP gPXE encapsulated option 178.
0x01 : The encapsulated option's value occupies 1 byte.
0x01 : The encapsulated option's value is 1 (true).
I do not know which DHCP service you use, so I do not know how you
can reconfigure your service to give PXE clients this 'use-cached'
option via DHCP.
Shao Miller
dhcp server is msdhcp
Use 1781.jpg and 1782.jpg is set. Enable use-cached did not succeed
Picture shows what can it?
Those screen-shots show a DHCP option 178, not a DHCP gPXE encapsulated
option 178.
You need DHCP option 175. _Inside_ option 175, you need to have gPXE
encapsulated option 178. See:
http://etherboot.org/wiki/msdhcp#setting_up_a_gpxe_encapsulated_options_on_windows_dhcp
It shows exactly how to create the DHCP gPXE encapsulated options. 175
is a _container_. 178 ('use-cached') goes inside that container. Change
to option 175 and you will be fine, since your bytes are exactly as I
explained above: Option 178, 1 byte long, value 1. All gPXE encapsulated
options go inside option 175. 0xB2 means 178.
Please remember to carbon-copy the list using Reply-All.
- Shao Miller
___
gPXE mailing list
gPXE@etherboot.org
http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
sqwbwh wrote:
At 2010-11-05 23:42:16，ShaoMillershao.mil...@yrdsb.edu.on.ca wrote:
sqwbwh wrote:
At 2010-11-05 23:13:19，ShaoMillershao.mil...@yrdsb.edu.on.ca
wrote:
sqwbwh wrote:
At 2010-11-05 22:39:05，ShaoMiller
shao.mil...@yrdsb.edu.on.ca wrote:
sqwbwh wrote:
How to modify the code can not get DHCP information
on the 2nd?(GPXE only used to boot the system from
ISCSI)
Is to remove this step.
net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0 (OPEN)
[Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0]
DHCP (net0 00:0 c: 29:08:11: d5 ) ok
net0: 192.168.0.202/255.255.255.0
This can speed up boot speed.
Normal GPXE run to start from the boot system tftp
process takes about 8 seconds or so
If removed from the second time for DHCP
information will only need a very quick 2.5 seconds.
Miller, Shao wrote:
You most likely want the 'use-cached' option. It is DHCP
gPXE encapsulated option number 178. Or, you can set it in an embedded
script:
#!gpxe
set use-cached 1
autoboot
Gene Cumm wrote:
What file and version are you using? It sounds as if
you're using
undionly.kpxe or a .pxe file. undionly.kkpxe will
skip this second
DHCP request but certain hardware/firmware has
issues with this,
assuming you trust the stability of your OEM's
PXE/UNDI stack.
sqwbwh wrote:
Shao Miller
The method is successful.
Thank you
sqwbwh wrote:
yes
thankyou Shao Miller
Your method is useful ：）
Miller, Shao wrote:
You’re quite welcome, and thanks for including the
list on your other reply. :) Have a nice day. - Shao
sqwbwh wrote:
Shao Miller
1:
i use :
set it in an embedded script:
#!gpxe
set use-cached 1
autoboot
it's good
2:
It is DHCP gPXE encapsulated option number 178
Specifically to ask how to use this method?
What can explain it in detail?
thank~you
I enjoy using the search feature at the gPXE (Etherboot)
wiki. Please see:
http://etherboot.org/wiki/doku.php?do=searchid=encapsulatedfulltext=Search
http://etherboot.org/wiki/msdhcp
http://etherboot.org/wiki/dhcpd
ShaoMiller
Use the search function.
Use hyperlinks to provide you with three options for the
introduction of 178 not found.
178 keyword search does not find use-cached search did not
find the relevant presentation.
Hehe. Could you give me the answer it?. English is almost a
maze for me
I'm afraid that I'm not sure how to explain gPXE encapsulated
options any better than they are explained in the wiki. DHCP
option 175 should be a string of bytes. Within that byte
sequence, there are sub-options. 'use-cached' is sub-option
178. So your DHCP option 175 could look like:
0xB2 0x01 0x01
where,
0xB2 : DHCP gPXE encapsulated option 178.
0x01 : The encapsulated option's value occupies 1 byte.
0x01 : The encapsulated option's value is 1 (true).
I do not know which DHCP service you use, so I do not know
how you can reconfigure your service to give PXE clients this
'use-cached' option via DHCP.
Shao Miller
dhcp server is msdhcp
Use 1781.jpg and 1782.jpg is set. Enable use-cached did not succeed
Picture shows what can it?
Those screen-shots show a DHCP option 178, not a DHCP gPXE
encapsulated option 178.
You need DHCP option 175. _Inside_ option 175, you need to have
gPXE encapsulated option 178. See:
http://etherboot.org/wiki/msdhcp#setting_up_a_gpxe_encapsulated_options_on_windows_dhcp
It shows exactly how to create the DHCP gPXE encapsulated options.
175 is a _container_. 178 ('use-cached') goes inside that
container. Change to option 175 and you will be fine, since your
bytes are exactly as I explained above: Option 178, 1 byte long,
value 1. All gPXE encapsulated options go inside option 175. 0xB2
means 178.
Please remember to carbon-copy the list using Reply-All.
Shao Miller
i do 3.jpg and 4.jpg
but no success
If the screenshots just fine. Like http://etherboot.org/wiki/msdhcp #
setting_up_a_gpxe_encapsulated_options_on_windows_dhcp
The hyperlink is the CHAP user and password to understand
178 still do
Re: [gPXE] How to modify the code can not get DHCP information on the2nd
sqwbwh wrote:
At 2010-11-06 01:27:57，ShaoMillershao.mil...@yrdsb.edu.on.ca wrote:
sqwbwh wrote:
At 2010-11-05 23:42:16，ShaoMillershao.mil...@yrdsb.edu.on.ca
wrote:
sqwbwh wrote:
At 2010-11-05 23:13:19，ShaoMiller
shao.mil...@yrdsb.edu.on.ca wrote:
sqwbwh wrote:
At 2010-11-05 22:39:05，ShaoMiller
shao.mil...@yrdsb.edu.on.ca wrote:
sqwbwh wrote:
How to modify the code can not get DHCP
information on the 2nd?(GPXE only used to boot
the system from ISCSI)
Is to remove this step.
net0: 00:0 c:: 29:08:11:35 on UNDI-PCI02: 01.0
(OPEN)
[Link: up, TX: 0 TXE: 0 TX: 0 rxe: 0]
DHCP (net0 00:0 c: 29:08:11: d5 ) ok
net0: 192.168.0.202/255.255.255.0
This can speed up boot speed.
Normal GPXE run to start from the boot system
tftp process takes about 8 seconds or so
If removed from the second time for DHCP
information will only need a very quick 2.5
seconds.
Miller, Shao wrote:
You most likely want the 'use-cached' option. It is
DHCP gPXE encapsulated option number 178. Or, you can set it in an
embedded script:
#!gpxe
set use-cached 1
autoboot
Gene Cumm wrote:
What file and version are you using? It sounds
as if you're using
undionly.kpxe or a .pxe file. undionly.kkpxe
will skip this second
DHCP request but certain hardware/firmware has
issues with this,
assuming you trust the stability of your OEM's
PXE/UNDI stack.
sqwbwh wrote:
Shao Miller
The method is successful.
Thank you
sqwbwh wrote:
yes
thankyou Shao Miller
Your method is useful ：）
Miller, Shao wrote:
You’re quite welcome, and thanks for including
the list on your other reply. :) Have a nice day.
- Shao
sqwbwh wrote:
Shao Miller
1:
i use :
set it in an embedded script:
#!gpxe
set use-cached 1
autoboot
it's good
2:
It is DHCP gPXE encapsulated option number 178
Specifically to ask how to use this method?
What can explain it in detail?
thank~you
I enjoy using the search feature at the gPXE
(Etherboot) wiki. Please see:
http://etherboot.org/wiki/doku.php?do=searchid=encapsulatedfulltext=Search
http://etherboot.org/wiki/msdhcp
http://etherboot.org/wiki/dhcpd
ShaoMiller
Use the search function.
Use hyperlinks to provide you with three options for
the introduction of 178 not found.
178 keyword search does not find use-cached search did
not find the relevant presentation.
Hehe. Could you give me the answer it?. English is
almost a maze for me
I'm afraid that I'm not sure how to explain gPXE
encapsulated options any better than they are explained
in the wiki. DHCP option 175 should be a string of
bytes. Within that byte sequence, there are sub-options.
'use-cached' is sub-option 178. So your DHCP option 175
could look like:
0xB2 0x01 0x01
where,
0xB2 : DHCP gPXE encapsulated option 178.
0x01 : The encapsulated option's value occupies 1 byte.
0x01 : The encapsulated option's value is 1 (true).
I do not know which DHCP service you use, so I do not
know how you can reconfigure your service to give PXE
clients this 'use-cached' option via DHCP.
Shao Miller
dhcp server is msdhcp
Use 1781.jpg and 1782.jpg is set. Enable use-cached did not
succeed
Picture shows what can it?
Those screen-shots show a DHCP option 178, not a DHCP gPXE
encapsulated option 178.
You need DHCP option 175. _Inside_ option 175, you need to
have gPXE encapsulated option 178. See:
http://etherboot.org/wiki/msdhcp#setting_up_a_gpxe_encapsulated_options_on_windows_dhcp
It shows exactly how to create the DHCP gPXE encapsulated
options. 175 is a _container_. 178 ('use-cached')
