similar to: pxelinux properly configured cannot find "default" configuration file

Hi! As documented: http://www.syslinux.org/wiki/index.php/PXELINUX When pxelinux "boots" it is looking for this: /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd /mybootdir/pxelinux.cfg/C000025B /mybootdir/pxelinux.cfg/C000025 /mybootdir/pxelinux.cfg/C00002 /mybootdir/pxelinux.cfg/C0000 /mybootdir/pxelinux.cfg/C000

Hi Everyone. is there a need to have on searching the configuration file the request for the "odd ip addresses" ? Let me explain: from /doc/pxelinux.txt : ... Next, it will search for the config file using its own IP address in upper case hexadecimal, e.g. 192.0.2.91 -> C000025B (you can use the included progam "gethostip" to compute the hexadecimal IP address for

Hi! We use Windows tftp-servers (so I dont think switching now would be an alternative). But I can try to suggest it. More specific, vendor id of the mac address, is what I want to be able to "choose" (if match) which bootmenu to display. Like all broadcom NICs we have would boot the undionly.kpxe "menu!! (I am having some trouble with broadcom (PCI fiber) and iPXE :) And the

I intend to release SYSLINUX 3.73-pre7 as SYSLINUX 3.73 as soon as possible. Please let me know if there are any outstanding bugs with 3.73-pre7 that either haven't been reported or I have forgotten about... it's been a while. -hpa

Hi This is what I like to be able to do. 1. Computer boot on LAN, using PXELinux. 2. If the computer is booting for the first time it sends MAC adr, RAM, size of harddrive and name of videocard to a shared folder on a computer, maybe a server, that is attached to the network. 3. If this is not the first time it scan for a new task, could be a new ghostimage or an unattended installation of a

On 2014/4/23 ?? 12:54, Ady wrote: > Is this about not liking the need for (sub)directories (depending on > firmware)? Or is it about functionality? > > If I understood correctly the prior email threads, the (real) problem > was in trying to maintain the searching for: > > pxelinux.cfg/01-88-99-aa-bb-cc-dd > pxelinux.cfg/C000025B > pxelinux.cfg/C000025 >

Dear all, I'd like to have a DHCP/PXE server for different arch of clients, i.e. BIOS, EFI32, and EFI64 clients. As described here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 What Daniel has proposed (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10) should work, i.e. Using a file called pxelinux.cfg/bios containing the following 2 lines:

Currently, the TFTP configuration file discovery process will request a set of files based on the UUID, MAC address, lease IP address and eventually fall back to "default": /mybootdir/pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd /mybootdir/pxelinux.cfg/C000025B [...] /mybootdir/pxelinux.cfg/C /mybootdir/pxelinux.cfg/default

On 2014/4/23 ?? 09:55, Gene Cumm wrote: > The resulting config would require suffix-less module references, i.e. > "UI menu" or "COM32 ls". > > Additionally, I documented the basics of my test system here: > > http://www.syslinux.org/archives/2014-February/021740.html > > Bear in mind, by "URL-like file locations", I mean that if we have >

> > > On 2014/4/23 12:54, Ady wrote: > > Is this about not liking the need for (sub)directories (depending on > > firmware)? Or is it about functionality? > > > > If I understood correctly the prior email threads, the (real) problem > > was in trying to maintain the searching for: > > > > pxelinux.cfg/01-88-99-aa-bb-cc-dd > >

Hi, Is it possible for pxelinux.0 to use the mac address of the machine in addition to IP address and its derivatives from the tftp server? Thanks, -- rajeev _________________________________________________________________ Check out Election 2004 for up-to-date election news, plus voter tools and more! http://special.msn.com/msn/election2004.armx

Hi All, I've been trying to understand how to use pxechn.c32 to chain a local pxelinux menu item to a remote server which has it's own pxelinux hierarchy served via TFTP and HTTP. We have no control over DHCP next-server and filename fields so I wanted to exploit the "prefix" -p option that pxechn.c32 accepts. I spent a long time hitting my head against a brick wall until I

> > On 2014/4/23 09:55, Gene Cumm wrote: > > The resulting config would require suffix-less module references, i.e. > > "UI menu" or "COM32 ls". > > > > Additionally, I documented the basics of my test system here: > > > > http://www.syslinux.org/archives/2014-February/021740.html > > > > Bear in mind, by "URL-like

> Dear all, > I'd like to have a DHCP/PXE server for different arch of clients, i.e. > BIOS, EFI32, and EFI64 clients. > As described here: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > What Daniel has proposed > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10) should > work, i.e. Using a file called pxelinux.cfg/bios containing the >

On 09/26/2013 01:44 AM, Jeffrey Hutzelman wrote: > Yes; you can configure your DHCP server to hand out different values for > the pxelinux.configfile option to specific clients, matching on MAC > address or a variety of other conditions. Of course, this means that > the config file for that machine will need to know what firmware to > expect and thus what path to set. Hi Jeffrey,

> There might be an alternative (and possibly others too): let the user > select the appropriate firmware from within pxelinux.cfg/default. > > So, keep using the same method you used in previous versions, instead > of selecting the Syslinux cfg / firmware from the DHCP snippet that > Daniel posted. > > If you actually get to pxelinux.cfg/default (as you probably used

> > On 09/20/2013 02:34 AM, Ady wrote: > >> There might be an alternative (and possibly others too): let the user > >> select the appropriate firmware from within pxelinux.cfg/default. > >> > >> So, keep using the same method you used in previous versions, instead > >> of selecting the Syslinux cfg / firmware from the DHCP snippet that >

> Check if the first character matches the character to replace, rather > than skipping it and starting with the second. > > Signed-off-by: Josh Triplett <josh at joshtriplett.org> > --- > > I'm assuming, based on a look at the callers, that this is not > intentional, and that it just happened that none of the callers happened > to ever need to replace the

On 04/23/2014 05:27 PM, Ady wrote: > OK then, so let's review the situation a little more accurately. > > _ Goal: to be able to keep searching for: > > pxelinux.cfg/01-88-99-aa-bb-cc-dd > pxelinux.cfg/C000025B > pxelinux.cfg/C000025 > pxelinux.cfg/C00002 > pxelinux.cfg/C0000 > pxelinux.cfg/C000 > pxelinux.cfg/C00 > pxelinux.cfg/C0 > pxelinux.cfg/C >

On Mon, Apr 03, 2023 at 12:52:41PM -0400, Rob Roschewsk via Syslinux wrote: > Hi All, > > I have a situation where I want to netboot and ONLY use pxelinux.cfg/default. > > It seems to take FOREVER for pxelinux to try all of the config file > file options before falling through to default .... trying each > possible combination multiple times ... increasing the wait time >