Syslinux - Nov 2010 - pxelinux 4.03 taking forever to find ..../pxelinux.cfg/default

Hi,
Is there anything that controls the speed with which pxelinux.0 (4.03)
enumerates the files in .../pxelinux.cfg before it reaches the
.../pxelinux.cfg/default file ?

       pxelinux.cfg/01-00-50-56-ba-48-0e
       pxelinux.cfg/AC12B2D9
       pxelinux.cfg/AC12B2D
       pxelinux.cfg/AC12B2
       pxelinux.cfg/AC12B
       pxelinux.cfg/AC12
       pxelinux.cfg/AC1
       pxelinux.cfg/AC
       pxelinux.cfg/A
       pxelinux.cfg/default

It's taking several minutes before moving on to the next file... any
thoughts on why this would be ?

Cheers,

Doug

On Tue, Nov 16, 2010 at 06:08, Doug Scoular <dscoular at gmail.com>
wrote:
> Hi,
> Is there anything that controls the speed with which pxelinux.0 (4.03)
> enumerates the files in .../pxelinux.cfg before it reaches the
> .../pxelinux.cfg/default file ?
>
> ? ? ? pxelinux.cfg/01-00-50-56-ba-48-0e
> ? ? ? pxelinux.cfg/AC12B2D9
> ? ? ? pxelinux.cfg/AC12B2D
> ? ? ? pxelinux.cfg/AC12B2
> ? ? ? pxelinux.cfg/AC12B
> ? ? ? pxelinux.cfg/AC12
> ? ? ? pxelinux.cfg/AC1
> ? ? ? pxelinux.cfg/AC
> ? ? ? pxelinux.cfg/A
> ? ? ? pxelinux.cfg/default
>
> It's taking several minutes before moving on to the next file... any
> thoughts on why this would be ?
Probably timeouts.  If your TFTPD is not returning a file not found
(OpCode: Error Code (5); Error Code: File not found (1)), that could
cause PXELINUX to wait for the TFTP timeout before attempting the next
file.  I think the default TFTP timeout in PXELINUX is 60 seconds.
Try a packet capture and watch the interactions of your TFTPD and
PXELINUX client.  You should see a client read request followed by a
daemon file not found.

For me, I normally see these possible config file names overwriting
the previous (making it quieter from a user perspective) and normally
all of them are attempted in under 1 second (about 0.05 seconds for a
test I just ran).  Do you actually see all 10 lines like you have
mentioned above?

-- 
-Gene

On Tue, 16 Nov 2010, Doug Scoular wrote:
> Hi,
> Is there anything that controls the speed with which pxelinux.0 (4.03)
> enumerates the files in .../pxelinux.cfg before it reaches the
> .../pxelinux.cfg/default file ?
>
>       pxelinux.cfg/01-00-50-56-ba-48-0e
>       pxelinux.cfg/AC12B2D9
>       pxelinux.cfg/AC12B2D
>       pxelinux.cfg/AC12B2
>       pxelinux.cfg/AC12B
>       pxelinux.cfg/AC12
>       pxelinux.cfg/AC1
>       pxelinux.cfg/AC
>       pxelinux.cfg/A
>       pxelinux.cfg/default
>
> It's taking several minutes before moving on to the next file... any
> thoughts on why this would be ?
I have no thoughts on why this would happen, but a workaround would be
to specify the configuration file with the pxelinux.configfile option.
pxelinux will go directly to the specified config file without trying
the 9 other possibilities. I wonder how many installations are really
able to overload IP address ranges with configuration information.

See:

   http://syslinux.zytor.com/wiki/index.php/PXELINUX
   http://syslinux.zytor.com/archives/2010-November/015586.html

for help setting a configuration file.

Daniel Feenberg
>
> Cheers,
>
> Doug
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>