Syslinux - Nov 2013 - syslinux.efi pxeboot across multiple subnets

On Mon, Nov 4, 2013 at 5:13 PM, H. Peter Anvin <hpa at zytor.com>
wrote:
> Please indicate what version of Syslinux you are using, and also a hint
> at your system configuration.
>
> I presume the packet dump was taken on the server.  They indicate the
> client trying to initiate a TFTP transaction but apparently not getting
> the reply.  This *may* be the same bug that ended up in 6.02 but has
> since been fixed.
In the first example, there are three requests for syslinux.efi spaced
~7ms then ~2146 ms apart.  Presumably, the first two is just the
initial request for size/options then the real request.  I'd say the
EFI system either is unable to retrieve syslinux.efi (perhaps not
appropriately receiving the reply packet; perhaps packet loss or
reordering) or doesn't like something about the file.

Was the exact same client (not just a similar client) used with
syslinux.efi and grub.efi across subnets?  Was this the file specified
in the DHCP replies or are you chainloading it?

You'd probably be better off filtering by client IP rather than just
'port 69'.

-- 
-Gene

On Mon, Nov 4, 2013 at 6:26 PM, Gene Cumm <gene.cumm at gmail.com>
wrote:
> On Mon, Nov 4, 2013 at 5:13 PM, H. Peter Anvin <hpa at zytor.com>
wrote:
>> Please indicate what version of Syslinux you are using, and also a hint
>> at your system configuration.
>>
>> I presume the packet dump was taken on the server.  They indicate the
>> client trying to initiate a TFTP transaction but apparently not getting
>> the reply.  This *may* be the same bug that ended up in 6.02 but has
>> since been fixed.
>
> In the first example, there are three requests for syslinux.efi spaced
> ~7ms then ~2146 ms apart.  Presumably, the first two is just the
> initial request for size/options then the real request.  I'd say the
> EFI system either is unable to retrieve syslinux.efi (perhaps not
> appropriately receiving the reply packet; perhaps packet loss or
> reordering) or doesn't like something about the file.
>
> Was the exact same client (not just a similar client) used with
> syslinux.efi and grub.efi across subnets?  Was this the file specified
> in the DHCP replies or are you chainloading it?
>
> You'd probably be better off filtering by client IP rather than just
'port 69'.
I seem to have missed the three requests in the success.

-- 
-Gene

The same client was used for syslinux.efi (both success on same subnet and
failure on different subnet) and grub.efi. The DHCP host block is setup
like:

host testing {
    hardware ethernet {mac} ;
    next-server 10.16.195.178 ;
    filename "rhel64/syslinux.efi" ;
}

I'll pull a tcpdump filtering by the IP tomorrow when I get back to the
systems.


On Mon, Nov 4, 2013 at 6:41 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Mon, Nov 4, 2013 at 6:26 PM, Gene Cumm <gene.cumm at gmail.com>
wrote:
> > On Mon, Nov 4, 2013 at 5:13 PM, H. Peter Anvin <hpa at
zytor.com> wrote:
> >> Please indicate what version of Syslinux you are using, and also a
hint
> >> at your system configuration.
> >>
> >> I presume the packet dump was taken on the server.  They indicate
the
> >> client trying to initiate a TFTP transaction but apparently not
getting
> >> the reply.  This *may* be the same bug that ended up in 6.02 but
has
> >> since been fixed.
> >
> > In the first example, there are three requests for syslinux.efi spaced
> > ~7ms then ~2146 ms apart.  Presumably, the first two is just the
> > initial request for size/options then the real request.  I'd say
the
> > EFI system either is unable to retrieve syslinux.efi (perhaps not
> > appropriately receiving the reply packet; perhaps packet loss or
> > reordering) or doesn't like something about the file.
> >
> > Was the exact same client (not just a similar client) used with
> > syslinux.efi and grub.efi across subnets?  Was this the file specified
> > in the DHCP replies or are you chainloading it?
> >
> > You'd probably be better off filtering by client IP rather than
just
> 'port 69'.
>
> I seem to have missed the three requests in the success.
>
> --
> -Gene
> _______________________________________________
> 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.
>
>