<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Randy McAnally wrote:</tt>
<blockquote type="cite" cite="mid:20091216144152.M26025@fast-serv.com">
<title>Re: [gPXE] Alternative http image location</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">I'm using it now but for some reason I can only
load files (via http uri) from<br>
the TFTP server IP, no other IP works even on the same subnet.</font></tt></p>
</blockquote>
<tt>Before loading PXELINUX from gPXE, you could investigate your gPXE
environment with the Control-B CLI and commands such as 'route'. You
could also test downloading a file from that CLI versus from PXELINUX
to determine if there's a difference there. Similarly, you can try
downloading from a running OS somewhere, to rule out web-server or
firewall configuration error.<br>
<br>
You might also enjoy PXELINUX' DHCP options 209 and 210, where you can
set a default prefix with 210 which PXELINUX will use for relative
paths specified in any config-files. Documentation there is in
syslinux/doc/rfc5071.txt<br>
<br>
Check to be absolutely sure that your PXELINUX is a version
greater-than-or-equal-to 3.70, which is when gPXE-provided HTTP support
was included. The fact that you can download successfully from the
TFTP server only might hint that you are actually downloading via TFTP
due to an older version, perhaps... Worth checking what happens if
TFTP is not running or the files in the TFTP service directory are
removed!<br>
<br>
- Shao Miller</tt>
</body>
</html>