Syslinux - Mar 2010 - any way to get pxelinux to grab its config file from another host?

I'm using gpxe to chain to pxelinux on a different host than gpxe was
loaded from.  The chain command looks like this

    chain tftp://other-host/pxelinux.0

Unfortunately, pxelinux is ignoring other-host and going back to the
original host to look for its files.  Is there any way to alter this
behavior?

Thanks,
Mike

Oops.  Just realized that a lot has happened since Ubuntu's latest
syslinux (== 3.63).

I'm hoping to cut a Gordian knot at my site--hope 3.85 will do it...



On Fri, Mar 12, 2010 at 11:34 AM, Mike Coleman <tutufan at gmail.com>
wrote:
> I'm using gpxe to chain to pxelinux on a different host than gpxe was
> loaded from. ?The chain command looks like this
>
> ? ?chain tftp://other-host/pxelinux.0
>
> Unfortunately, pxelinux is ignoring other-host and going back to the
> original host to look for its files. ?Is there any way to alter this
> behavior?
>
> Thanks,
> Mike
>

Mike Coleman wrote:
>
> I'm using gpxe to chain to pxelinux on a different host than gpxe was
> loaded from.  The chain command looks like this
>
>     chain tftp://other-host/pxelinux.0
>
> Unfortunately, pxelinux is ignoring other-host and going back to the
> original host to look for its files.  Is there any way to alter this
> behavior?...
>
See syslinux/doc/rfc5071.txt to learn about DHCP options 209 and 210.

gPXE> set 210:string tftp://other-host/
gPXE> chain ${210}pxelinux.0

You can also specify DHCP option 210 in the DHCP service, itself.

- Shao Miller