I know it's not gPXE but you can try iPXE, it has graphical menu where you can set this values manually (<a href="http://ipxe.org/_detail/screenshots/config_ui.png?id=pics">http://ipxe.org/_detail/screenshots/config_ui.png?id=pics</a>) every time the system start.<br>
<br><br><div class="gmail_quote">2011/5/15 <span dir="ltr"><<a href="mailto:gpxe-request@etherboot.org" target="_blank">gpxe-request@etherboot.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send gPXE mailing list submissions to<br>
<a href="mailto:gpxe@etherboot.org" target="_blank">gpxe@etherboot.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://etherboot.org/mailman/listinfo/gpxe" target="_blank">http://etherboot.org/mailman/listinfo/gpxe</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:gpxe-request@etherboot.org" target="_blank">gpxe-request@etherboot.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:gpxe-owner@etherboot.org" target="_blank">gpxe-owner@etherboot.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of gPXE digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Use gpxe without dhcp to get pxe menu from network<br>
(<a href="mailto:Josh.Mullis@cox.com" target="_blank">Josh.Mullis@cox.com</a>)<br>
2. Re: Use gpxe without dhcp to get pxe menu from network (Gene Cumm)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sat, 14 May 2011 18:24:49 -0400<br>
From: <<a href="mailto:Josh.Mullis@cox.com" target="_blank">Josh.Mullis@cox.com</a>><br>
To: <<a href="mailto:gpxe@etherboot.org" target="_blank">gpxe@etherboot.org</a>><br>
Subject: [gPXE] Use gpxe without dhcp to get pxe menu from network<br>
Message-ID:<br>
<<a href="mailto:6658CB4ADCA0B24AA08CF9623E61A1A0049A6DF0CA@CATL0MS112.corp.cox.com" target="_blank">6658CB4ADCA0B24AA08CF9623E61A1A0049A6DF0CA@CATL0MS112.corp.cox.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hello all,<br>
<br>
I'm probably as newbie as they come so bare with me if I'm missing the obvious...<br>
<br>
<br>
Simply put: My end goal is to have a boot iso that will grab a pxeboot menu from the network.<br>
I already have a tftp/http server serving up the standard pxe menu via "/tftpboot/pxelinux.cfg/default".<br>
<br>
The iso will need to allow a user to input ip information. (dhcp is not allowed on our networks)<br>
Then use that to retrieve the pxe menu.<br>
<br>
<br>
I have ready through the docs, mail archives, how-tos, and general google searches.<br>
Maybe I'm using the wrong terminology in my searches.<br>
<br>
<br>
I have tried generating iso's from the rom-o-matic site (checked all boxes) with an embedded script to no avail.<br>
My embedded scripts looked similar to this with minor alterations trying different combinations...<br>
<br>
=================================<br>
#!gpxe<br>
ifopen net0<br>
set net0/ip 10.1.1.2<br>
set net0/netmask 255.255.255.0<br>
set net0/gateway 10.1.1.1<br>
chain <a href="http://myserver/boot/pxelinux.0" target="_blank">http://myserver/boot/pxelinux.0</a><br>
boot<br>
=================================<br>
<br>
<br>
<br>
Hopefully this is an easy task and I'm just missing something.<br>
Thanks for making it through all that and for any help you guys can provide this newbie. :)<br>
<br>
-Josh<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://etherboot.org/pipermail/gpxe/attachments/20110514/478ad50c/attachment-0001.html" target="_blank">http://etherboot.org/pipermail/gpxe/attachments/20110514/478ad50c/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sat, 14 May 2011 23:21:56 -0400<br>
From: Gene Cumm <<a href="mailto:gene.cumm@gmail.com" target="_blank">gene.cumm@gmail.com</a>><br>
To: <a href="mailto:Josh.Mullis@cox.com" target="_blank">Josh.Mullis@cox.com</a><br>
Cc: <a href="mailto:gpxe@etherboot.org" target="_blank">gpxe@etherboot.org</a><br>
Subject: Re: [gPXE] Use gpxe without dhcp to get pxe menu from network<br>
Message-ID: <<a href="mailto:BANLkTimAOcohhzQC-SWU39M-%2Bycapx6D7w@mail.gmail.com" target="_blank">BANLkTimAOcohhzQC-SWU39M-+ycapx6D7w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
On Sat, May 14, 2011 at 18:24, <<a href="mailto:Josh.Mullis@cox.com" target="_blank">Josh.Mullis@cox.com</a>> wrote:<br>
> Hello all,<br>
><br>
> I?m probably as newbie as they come so bare with me if I?m missing the<br>
> obvious?<br>
><br>
><br>
> Simply put:? My end goal is to have a boot iso that will grab a pxeboot menu<br>
> from the network.<br>
> I already have a tftp/http server serving up the standard pxe menu via<br>
> ?/tftpboot/pxelinux.cfg/default?.<br>
><br>
> The iso will need to allow a user to input ip information. (dhcp is not<br>
> allowed on our networks)<br>
> Then use that to retrieve the pxe menu.<br>
><br>
><br>
> I have ready through the docs, mail archives, how-tos, and general google<br>
> searches.<br>
> Maybe I?m using the wrong terminology in my searches.<br>
><br>
><br>
> I have tried generating iso?s from the rom-o-matic site (checked all boxes)<br>
> with an embedded script to no avail.<br>
> My embedded scripts looked similar to this with minor alterations trying<br>
> different combinations?<br>
><br>
> =================================<br>
> #!gpxe<br>
> ifopen net0<br>
> set net0/ip 10.1.1.2<br>
> set net0/netmask 255.255.255.0<br>
> set net0/gateway 10.1.1.1<br>
> chain <a href="http://myserver/boot/pxelinux.0" target="_blank">http://myserver/boot/pxelinux.0</a><br>
> boot<br>
> =================================<br>
><br>
><br>
><br>
> Hopefully this is an easy task and I?m just missing something.<br>
> Thanks for making it through all that and for any help you guys can provide<br>
> this newbie.?? :)<br>
<br>
Your issue is configuring gPXE to provide sufficient information to<br>
PXELINUX. The error was probably "Unable to locate configuration<br>
file" with the second IP address as "0.0.0.0". You'll need to set<br>
DHCP options 209 and 210 if you wish to avoid TFTP completely. Those<br>
are the search keys you're missing.<br>
<a href="http://etherboot.org/wiki/httpboot?s[]=209#using_pxelinux" target="_blank">http://etherboot.org/wiki/httpboot?s[]=209#using_pxelinux</a><br>
<br>
If you want to have PXELINUX load the configs via TFTP and go the more<br>
classical PXE route, you'll need to set next-server and filename<br>
(either as-is or scoped under net0/ ) but HTTP is definitely more<br>
reliable and most of the time faster.<br>
<br>
There's also a config command that shows a nice TUI (as opposed to the<br>
CLI). 'config net0' would probably be your best choice.<br>
<br>
--<br>
-Gene<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
gPXE mailing list<br>
<a href="mailto:gPXE@etherboot.org" target="_blank">gPXE@etherboot.org</a><br>
<a href="http://etherboot.org/mailman/listinfo/gpxe" target="_blank">http://etherboot.org/mailman/listinfo/gpxe</a><br>
<br>
<br>
End of gPXE Digest, Vol 20, Issue 1<br>
***********************************<br>
</blockquote></div><br>