• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Existing iPXE-Environment -- no chaining possible to fogserver?

    Scheduled Pinned Locked Moved
    General Problems
    1
    1
    206
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Systembetreuer
      last edited by

      Hello friends of FOG!

      I have a functioning iPXE-Environment. Via http (Tiny PXE Server) I can chain to a WDS for deploying windows images. I also can boot into various linux systems.

      Now I have a fogserver, but I just can’t manage to customize my UEFI-iPXE menu or my legacy-iPXE menu to access the FOGSERVER. And if I do, then the FOG menu is displayed, but when I select an entry, I am thrown back into the menu. I’ve wasted a few days on this and can’t find anything on the net that works.

      I just need an entry that takes me to the Fogserver:

      :fog
      set net0/next-server FOG-SERVER-IP
      set filename undionly.kkpxe (boot.php ?, undionly.kpxe ?)
      chain tftp://${next-server}/${filename}

      What I also do: The undionly is loaded, but then a DHCP request is made and the response refers again and again to my iPXE server instead of to the FOGSERVER.

      I always get the entry tftp://iPXE-Server-IP/default.ipxe (although I have never specified this anywhere), and this default.ipxe cannot be processed, regardless of whether it is in the specified location or not.

      Please help.

      1 Reply Last reply Reply Quote 0
      • 1 / 1
      • First post
        Last post

      138

      Online

      12.0k

      Users

      17.3k

      Topics

      155.2k

      Posts
      Copyright © 2012-2024 FOG Project