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. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
relative tftp path for embedded script, pxelinux.0 behaviour - aka - 2012-07-21, 22:10
RE: relative tftp path for embedded script, pxelinux.0 behaviour - robinsmidsrod - 2012-07-22, 19:03
RE: relative tftp path for embedded script, pxelinux.0 behaviour - aka - 2012-07-22, 21:54
RE: relative tftp path for embedded script, pxelinux.0 behaviour - robinsmidsrod - 2012-07-24, 18:45
RE: relative tftp path for embedded script, pxelinux.0 behaviour - aka - 2012-07-24, 19:33
RE: relative tftp path for embedded script, pxelinux.0 behaviour - robinsmidsrod - 2012-07-25, 15:29
RE: relative tftp path for embedded script, pxelinux.0 behaviour - johnres - 2014-01-01, 16:03
RE: relative tftp path for embedded script, pxelinux.0 behaviour - robinsmidsrod - 2014-01-08 08:27
RE: relative tftp path for embedded script, pxelinux.0 behaviour - highlight86 - 2014-01-09, 08:13
RE: relative tftp path for embedded script, pxelinux.0 behaviour - pojntfx - 2021-05-11, 09:47
|
User(s) browsing this thread: 4 Guest(s)