Re: [gPXE] Pushing GPXE script to HTTP server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It worked well for what I wanted if I do single boot, however I couldn't get the multi-boot menu to work. Well done getting single boot working. So my gpxe.conf looks like this: #!gpxe chain vesamenu.c32 multibootmenu.conf The station tries to switch graphics mode for a second and reboots. I guess that's because (vesa)menu.c32 of Syslinux couldn't find multibootmenu.conf (or whatever file it was supposed to read as its argument). I placed multibootmenu.conf and (vesa)menu.c32 in the same directory as gpxe.conf (which is hard-coded to the ROM). Perhaps (vesa)menu.c32 suffers the same filename limitations as the rest of Syslinux. Syslinux is limited to filenames in the 8.3 format. This explains not finding the configuration file. I have seen this in other areas where I've used Syslinux and have formed the habit of using only 8.3 filenames when Syslinux is involved in any way. I am using vesamenu.c32 from Syslinux 4.01 as well. I wonder if there are tricks to make (vesa)menu.c32 to be able to read multibootmenu.conf. I used vesamenu.c32 from syslinux 4.01. What happens when you change multibootmenu.conf to mbmenu.cfg and update the gPXE script accordingly? - -- David Joshua Geary UNE Linux User Group: li...@une.edu.au http://lugune.dyndns.org I don't care what software you use so long as we only exchange files in open data formats Open-Document http://en.wikipedia.org/wiki/Open_Document Ogg http://en.wikipedia.org/wiki/Ogg PDF http://en.wikipedia.org/wiki/Pdf - -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.9 (GNU/Linux) mQGiBEl4bFQRBADDxqFXQ0Rv69sZ5xxK2WYXASHVe68Qf0LT0ag0/kEb4t3WWi9K R5FKOhHrp1Fnt+S+NF4157l3bTJ1aFMEc2WM97qS37u0OXr+9XzMyWQyH3NLKHgm QitKPasVM2UJaateFfr2XijQIfKQURkE03rKsEADm75qPeb5yhYKGuGQ9wCg5LFJ 5c67ZiJ/zPcS9pgKbUDMG4sD/A5URvxutCgbVIHr34nZu5OnF3BkCbdilMHATVCn y2Y6w2bkjozSL4ieWTOqRSfiZaEBxgYXKMKVZWpGSiz9nB8Tn0Ddf8poK//nRAeo qV+JG1vnkfoxQR0HXCbzyxxNtRELWZVUGgWLrUEBB6XaDC5SQzhCoeT5LTT9jOQg uA/eBACJ0yQFdTgcnT3G5ZmMYzYU3t9WFsBEB4uLFdZn/WLRr2LU0e2ZS5fAz5y0 eCcxNiw8Yn35qKiu6ulY3LcHkBwEL+wJVCrd05MWKxYx7hpW6jMP/SqoTvAhr3a5 GlSMQ+K+YmcGrKktVF47ntCCGfmonDeGOajRz8ggorJ4iHK2/7Q4RGF2aWQgR2Vh cnkgKFVORSBFbWFpbCBTaWduaW5nIEtleSkgPGRnZWFyeTJAdW5lLmVkdS5hdT6I YAQTEQIAIAUCSXhsVAIbIwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEM3mPvoV hbOMprgAoKsPQkn6odlg9M/E+AJlKaoKkJ5rAJ4yDL5MJoRKIAwSPz4/pRpHr93+ +LkCDQRJeGxUEAgAj0/cTlN3FldkGMBx5/emUGQ+jtXqgRHB8GqNlCWVBphUcS0h SzJZDMro8f4evKfqBqOknqU7fkGVh2FhWC/R+fmDcwWDwv1te9Yn/qeAbYh4sLNo 26cfxBfInaCueTa/XdCzobfH5jtaXfEyFzSoKVgrggoCN4BDtc86TAgY0MZuSbN3 vVMacl3MkfT+PfAEVviU3xSf3wS4KilY5Zpl5bHVLTms4dlm+N0bKIbGW+3N1WzE 6OLEHTbOhZDHVPYbUEryOg+LtKgejPAIaWg4Z+aH82+LNco5GDCDkqRlwQlnE3AE +u/rZAA2K+J6rW9MRLu/NxZp1ThRxZ56uF7GgwADBQgAji487rXw0Taldcr7bnRf eNEDQIGxUMRhlHl0Rtj3Tuk4TvwcorwNr89e5C2wYLhEl83squK961CbTpctsBI/ Id2r2f0H/bmTEG9RLNAjgZPaImT8YfrskEqnyaPAfHTP3gKUU5yWdTDsnnmRgvmN HTQlAl8IZ+eSYqlplsPy9Qtvlk+APMxcpD/8gAO7r/A5KrxX9HqyFWTJpAhGSY3g 7eg5OeNPi75Z3H7JViVqceUXIFUTFSVvKKYQm2XNOwl4+XmpcZ3FP+naKzXQmR8n gVub4CNWXH/tCm04vU0FdEsvPk2mWNHorjflhzxbRHRqvbMDk3NGpSRo22WAvrQm MohJBBgRAgAJBQJJeGxUAhsMAAoJEM3mPvoVhbOMk0YAoJNPJ93Ug3gytihlaXXY HAx+tdTkAKDVJrQz70o+3rcmJFC+e0iFqvbXlg== =Wur/ - -END PGP PUBLIC KEY BLOCK- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzT9i0ACgkQzeY++hWFs4xRawCgifbJK0goc7K3d70b1OrcsNJ/ 6UUAoKZOTzLrVcvYPOjh3zclRUoOoKiU =+BqQ -END PGP SIGNATURE- ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] Pushing GPXE script to HTTP server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Apologies, I am actually using Syslinux 3.63. Sorry for any confusion. - -- David Joshua Geary UNE Linux User Group: li...@une.edu.au http://lugune.dyndns.org I don't care what software you use so long as we only exchange files in open data formats Open-Document http://en.wikipedia.org/wiki/Open_Document Ogg http://en.wikipedia.org/wiki/Ogg PDF http://en.wikipedia.org/wiki/Pdf - -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.9 (GNU/Linux) mQGiBEl4bFQRBADDxqFXQ0Rv69sZ5xxK2WYXASHVe68Qf0LT0ag0/kEb4t3WWi9K R5FKOhHrp1Fnt+S+NF4157l3bTJ1aFMEc2WM97qS37u0OXr+9XzMyWQyH3NLKHgm QitKPasVM2UJaateFfr2XijQIfKQURkE03rKsEADm75qPeb5yhYKGuGQ9wCg5LFJ 5c67ZiJ/zPcS9pgKbUDMG4sD/A5URvxutCgbVIHr34nZu5OnF3BkCbdilMHATVCn y2Y6w2bkjozSL4ieWTOqRSfiZaEBxgYXKMKVZWpGSiz9nB8Tn0Ddf8poK//nRAeo qV+JG1vnkfoxQR0HXCbzyxxNtRELWZVUGgWLrUEBB6XaDC5SQzhCoeT5LTT9jOQg uA/eBACJ0yQFdTgcnT3G5ZmMYzYU3t9WFsBEB4uLFdZn/WLRr2LU0e2ZS5fAz5y0 eCcxNiw8Yn35qKiu6ulY3LcHkBwEL+wJVCrd05MWKxYx7hpW6jMP/SqoTvAhr3a5 GlSMQ+K+YmcGrKktVF47ntCCGfmonDeGOajRz8ggorJ4iHK2/7Q4RGF2aWQgR2Vh cnkgKFVORSBFbWFpbCBTaWduaW5nIEtleSkgPGRnZWFyeTJAdW5lLmVkdS5hdT6I YAQTEQIAIAUCSXhsVAIbIwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEM3mPvoV hbOMprgAoKsPQkn6odlg9M/E+AJlKaoKkJ5rAJ4yDL5MJoRKIAwSPz4/pRpHr93+ +LkCDQRJeGxUEAgAj0/cTlN3FldkGMBx5/emUGQ+jtXqgRHB8GqNlCWVBphUcS0h SzJZDMro8f4evKfqBqOknqU7fkGVh2FhWC/R+fmDcwWDwv1te9Yn/qeAbYh4sLNo 26cfxBfInaCueTa/XdCzobfH5jtaXfEyFzSoKVgrggoCN4BDtc86TAgY0MZuSbN3 vVMacl3MkfT+PfAEVviU3xSf3wS4KilY5Zpl5bHVLTms4dlm+N0bKIbGW+3N1WzE 6OLEHTbOhZDHVPYbUEryOg+LtKgejPAIaWg4Z+aH82+LNco5GDCDkqRlwQlnE3AE +u/rZAA2K+J6rW9MRLu/NxZp1ThRxZ56uF7GgwADBQgAji487rXw0Taldcr7bnRf eNEDQIGxUMRhlHl0Rtj3Tuk4TvwcorwNr89e5C2wYLhEl83squK961CbTpctsBI/ Id2r2f0H/bmTEG9RLNAjgZPaImT8YfrskEqnyaPAfHTP3gKUU5yWdTDsnnmRgvmN HTQlAl8IZ+eSYqlplsPy9Qtvlk+APMxcpD/8gAO7r/A5KrxX9HqyFWTJpAhGSY3g 7eg5OeNPi75Z3H7JViVqceUXIFUTFSVvKKYQm2XNOwl4+XmpcZ3FP+naKzXQmR8n gVub4CNWXH/tCm04vU0FdEsvPk2mWNHorjflhzxbRHRqvbMDk3NGpSRo22WAvrQm MohJBBgRAgAJBQJJeGxUAhsMAAoJEM3mPvoVhbOMk0YAoJNPJ93Ug3gytihlaXXY HAx+tdTkAKDVJrQz70o+3rcmJFC+e0iFqvbXlg== =Wur/ - -END PGP PUBLIC KEY BLOCK- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzT9toACgkQzeY++hWFs4y2eACgvKekhZ5Ai8yI6HnfTEynWSL4 wh0An0/oLDmV6jyRpCcrh1F4jZapwIsv =Nuzo -END PGP SIGNATURE- ___ 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 the 2nd
2010/11/5 sqwbwh sqw...@126.com: 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. 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. -- -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
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')
