Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
relative tftp path for embedded script, pxelinux.0 behaviour
2014-01-08, 08:27
Post: #8
RE: relative tftp path for embedded script, pxelinux.0 behaviour
I think I know what the actual problem is. The vendor PXE implementation is loading undionly.kpxe from somewhere on the TFTP server, but iPXE, when loaded like this, does not know where it was loaded from because the information is not available, or it is just not resolved. The filename should still be available in the cached dhcp response, but my guess is that the "current directory" is not set to this folder during initial load, as iPXE does when it chainloads a script.

I'm not sure if this is a feature or a bug. You should report it on the mailing-list regardless.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: relative tftp path for embedded script, pxelinux.0 behaviour - robinsmidsrod - 2014-01-08 08:27



User(s) browsing this thread: 3 Guest(s)