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

FOG BIOS And EFI Coexistence

Scheduled Pinned Locked Moved
General
8
51
37.7k
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.
  • W
    Wayne Workman
    last edited by May 4, 2015, 11:48 PM

    I can jump on this one…

    I’ll backup my current config and try this… give me 30 minutes…

    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
    Daily Clean Installation Results:
    https://fogtesting.fogproject.us/
    FOG Reporting:
    https://fog-external-reporting-results.fogproject.us/

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by May 5, 2015, 12:20 AM

      That’d be a negative… for both BIOS and UEFI… used two different machines to test.

      I’ve attached my WORKING ltsp.conf file, and the one I got from here (which I ripped the comments out of, and changed IP, and repaced .kpxe and .efi with .0)

      I also ensured I had the .0 files, too.

      [url=“/_imported_xf_attachments/1/1963_ltsp new.txt?:”]ltsp new.txt[/url][url=“/_imported_xf_attachments/1/1964_ltsp working.txt?:”]ltsp working.txt[/url]

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 0
      • D
        d4rk3
        last edited by May 5, 2015, 1:16 AM

        I use my router’s dnsmasq now, but this is my old working FOG dhcpd.conf that should do the trick.

        Change the IP’s/bootfiles to suite your needs.

        [CODE]# DHCP Server Configuration file.

        see /usr/share/doc/dhcp*/dhcpd.conf.sample

        This file was created by FOG

        use-host-decl-names on;
        ddns-update-style interim;
        ignore client-updates;
        next-server 10.0.0.5;
        option arch code 93 = unsigned integer 16;

        if option arch = 00:07 {
        filename “snp.efi”;
        }else if option arch = 00:06 {
        filename “ipxe.efi”;
        }else {
        filename “undionly.kpxe”;
        }

        subnet 10.0.0.0 netmask 255.255.255.0 {
        option subnet-mask 255.255.255.0;
        range dynamic-bootp 10.0.0.200 10.0.0.254;
        default-lease-time 21600;
        max-lease-time 43200;
        option domain-name-servers 10.0.0.1;
        option routers 10.0.0.1;
        }
        [/CODE]

        1 Reply Last reply Reply Quote 0
        • D
          d4rk3
          last edited by May 5, 2015, 1:28 AM

          [quote=“Wayne Workman, post: 46763, member: 28155”]That’d be a negative… for both BIOS and UEFI… used two different machines to test.

          I’ve attached my WORKING ltsp.conf file, and the one I got from here (which I ripped the comments out of, and changed IP, and repaced .kpxe and .efi with .0)

          I also ensured I had the .0 files, too.[/quote]

          Give this a try under [B]tftp-root=/tftpboot[/B] (replace FOG with your FOG server’s hostname):

          [CODE]dhcp-boot=undionly.kpxe,FOG,10.0.0.3
          dhcp-match=set:efi-ia32,option:client-arch,6
          dhcp-boot=tag:efi-ia32,ipxe.efi,FOG,10.0.0.3
          dhcp-match=set:efi-x86_64,option:client-arch,7
          dhcp-boot=tag:efi-x86_64,snp.efi,FOG,10.0.0.3
          dhcp-range=10.0.0.3,proxy,255.255.255.0
          [/CODE]

          1 Reply Last reply Reply Quote 0
          • J
            Junkhacker Developer
            last edited by May 5, 2015, 12:54 PM

            [quote=“Wayne Workman, post: 46755, member: 28155”]Are you using a dongle to Ethernet adapter, or WiFi ?[/quote]

            using the microsoft USB dongle. my legacy machines are working like they always have, uefi machines are loading ipxe.efi

            signature:
            Junkhacker
            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

            1 Reply Last reply Reply Quote 0
            • W
              Wayne Workman
              last edited by May 5, 2015, 3:02 PM

              [quote=“Junkhacker, post: 46782, member: 21583”]using the microsoft USB dongle. my legacy machines are working like they always have, uefi machines are loading ipxe.efi[/quote]

              Do share how you did it.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
              Daily Clean Installation Results:
              https://fogtesting.fogproject.us/
              FOG Reporting:
              https://fog-external-reporting-results.fogproject.us/

              1 Reply Last reply Reply Quote 0
              • N
                need2 Moderator
                last edited by May 5, 2015, 3:16 PM

                [quote=“Junkhacker, post: 46782, member: 21583”]using the microsoft USB dongle. my legacy machines are working like they always have, uefi machines are loading ipxe.efi[/quote]

                Do I need to bribe you?

                1 Reply Last reply Reply Quote 0
                • J
                  Junkhacker Developer
                  last edited by May 5, 2015, 3:36 PM

                  for windows server 2012 DHCP, it was as simple as the link Wayne Workman posted.
                  [url]http://www.syslinux.org/archives/2014-January/021404.html[/url] create vendor class that matches uefi systems ([I][COLOR=#000000]PXEClient:Arch:00007[/COLOR][/I]) and give those that match a different bootfile (in my case, ipxe.efi)

                  signature:
                  Junkhacker
                  We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                  1 Reply Last reply Reply Quote 0
                  • N
                    need2 Moderator
                    last edited by May 5, 2015, 3:52 PM

                    I see… interesting. This may be the direction that things have to go. DnsMasq seems in sufficient for EFI PXE and some older PXE clients. I’m still going to try a few things with it, but otherwise we might just have to make good documentation on the changes to make to a Windows 2012+ DHCP and a Linux DHCP to achieve coexistence. I will work on the Windows 2012 DHCP configs eventually (assuming DnsMasq fails me), but I will need to spin up a new 2012 server and integrate it to our domain first.

                    1 Reply Last reply Reply Quote 0
                    • W
                      Wayne Workman
                      last edited by May 5, 2015, 4:24 PM

                      This is the thread:

                      [url]http://fogproject.org/forum/threads/undionly-kpxe-and-ipxe-efi.12607/[/url]

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                      Daily Clean Installation Results:
                      https://fogtesting.fogproject.us/
                      FOG Reporting:
                      https://fog-external-reporting-results.fogproject.us/

                      1 Reply Last reply Reply Quote 0
                      • D
                        d4rk3
                        last edited by May 5, 2015, 6:15 PM

                        Has anyone tried either of my configs I posted? Both of them properly serve legacy/efi bootfiles.

                        1 Reply Last reply Reply Quote 0
                        • W
                          Wayne Workman
                          last edited by May 5, 2015, 6:22 PM

                          I will tonight. I had other things going on last night when you posted those.

                          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                          Daily Clean Installation Results:
                          https://fogtesting.fogproject.us/
                          FOG Reporting:
                          https://fog-external-reporting-results.fogproject.us/

                          1 Reply Last reply Reply Quote 0
                          • N
                            need2 Moderator
                            last edited by May 5, 2015, 6:41 PM

                            I will see what I can do as well… light staffing here today so I’m a bit busy.

                            1 Reply Last reply Reply Quote 0
                            • D
                              d4rk3
                              last edited by May 6, 2015, 2:30 AM

                              No worries, just wanted to make sure nobody overlooked them.

                              1 Reply Last reply Reply Quote 0
                              • W
                                Wayne Workman
                                last edited by May 7, 2015, 9:29 PM

                                [quote=“d4rk3, post: 46768, member: 23583”]Give this a try under [B]tftp-root=/tftpboot[/B] (replace FOG with your FOG server’s hostname):

                                [CODE]dhcp-boot=undionly.kpxe,FOG,10.0.0.3
                                dhcp-match=set:efi-ia32,option:client-arch,6
                                dhcp-boot=tag:efi-ia32,ipxe.efi,FOG,10.0.0.3
                                dhcp-match=set:efi-x86_64,option:client-arch,7
                                dhcp-boot=tag:efi-x86_64,snp.efi,FOG,10.0.0.3
                                dhcp-range=10.0.0.3,proxy,255.255.255.0
                                [/CODE][/quote]

                                I don’t know what parts you want me to take out, though…

                                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                                Daily Clean Installation Results:
                                https://fogtesting.fogproject.us/
                                FOG Reporting:
                                https://fog-external-reporting-results.fogproject.us/

                                1 Reply Last reply Reply Quote 0
                                • T
                                  Tom Elliott
                                  last edited by May 7, 2015, 9:35 PM

                                  Who’s already got this working?

                                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    d4rk3
                                    last edited by May 7, 2015, 11:04 PM

                                    [quote=“Wayne Workman, post: 47037, member: 28155”]I don’t know what parts you want me to take out, though…[/quote]

                                    None. Just replace [B]FOG[/B] with your FOG server’s hostname and replace [B]10.0.0.3[/B] with your FOG server’s IP.

                                    I goofed on the last line, it should read [I][FONT=Consolas]dhcp-range=[/FONT][/I][B][I][FONT=Consolas]10.0.0.0[/FONT][/I][/B][I][FONT=Consolas],proxy,255.255.255.0[/FONT][/I]

                                    For that, replace [B]10.0.0.0[/B] with your network’s address.

                                    And if you want to change any of the bootfiles to different ones have at it.

                                    1 Reply Last reply Reply Quote 0
                                    • W
                                      Wayne Workman
                                      last edited by May 8, 2015, 2:02 AM

                                      Well, 10.0.0.3 IS my home FOG server’s IP address. It’s a private address, not public, and it’s home so I don’t care about sharing here.

                                      And my network’s address is 10.0.0.0 I set my house up like that for simplicity… it’s easier to type than that dumb 192.168.1 BS that most home DHCP is configured with.

                                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                                      Daily Clean Installation Results:
                                      https://fogtesting.fogproject.us/
                                      FOG Reporting:
                                      https://fog-external-reporting-results.fogproject.us/

                                      1 Reply Last reply Reply Quote 0
                                      • T
                                        Tom Elliott
                                        last edited by May 8, 2015, 3:00 AM

                                        The dhcp-range line, I recommend, being set to your fog server. It will automatically work on the network your fogserver is on. If you’re actually trying to use a range of IP’s for Proxy to hand out then you would have something like:
                                        [code]dhcp-range=10.0.0.0,10.0.0.255,proxy,255.255.255.0[/code]

                                        However this is more than overkill. I think it highly unlikely you will be handing more than the network allowed (253 – e.g. gateway, network, broadcast) of your fog server’s possibilities.

                                        If you know you’ll be hitting more than that at any time, just open the subnet to a higher range. Whatever the IP is set will be the same network the proxy hands out within.

                                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                        1 Reply Last reply Reply Quote 0
                                        • J
                                          Jeroen Brussich
                                          last edited by May 8, 2015, 12:20 PM

                                          [quote=“Junkhacker, post: 46793, member: 21583”]for windows server 2012 DHCP, it was as simple as the link Wayne Workman posted.
                                          [url]http://www.syslinux.org/archives/2014-January/021404.html[/url] create vendor class that matches uefi systems ([I][COLOR=#000000]PXEClient:Arch:00007[/COLOR][/I]) and give those that match a different bootfile (in my case, ipxe.efi)[/quote]

                                          Did you got this up and running?
                                          I created the Vendor Class, created the policy, downloaded ipxe.efi and updated the DHCP server settings in 2012R2

                                          Legacy Boot + undionly.kpxe ~ working
                                          UEFI boot + ipxe.efi ~ [B]not working[/B]

                                          [B]edit:[/B] typo ([I]ipxe.kpxe[/I] should have been[I] ipxe.efi[/I])

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 1 / 3
                                          1 / 3
                                          • First post
                                            18/51
                                            Last post

                                          215

                                          Online

                                          12.1k

                                          Users

                                          17.3k

                                          Topics

                                          155.4k

                                          Posts
                                          Copyright © 2012-2024 FOG Project