• FOG v1.5.7
    Kernel 4.19.143 TomElliott arm64 (downloaded 1/12/21)
    CentOS 6.9

    I apologize in advance my Linux knowledge is non existent. So please be patient and spell everything out.

    The 840 G7 no longer has a network port. I have to use a USB-C to ethernet adapter. I can boot to the fog menu and deploy an image from previous hardware, but when I create a task to capture the newly created image and boot to network FOG does not recognize it and just takes me to the all white screen that shows the host is not registered, boot from hard disk etc.

    I am able to do a quick registration, and all that shows up in list all hosts is the MAC address of the USB-C to ethernet adapter. I tried to do a capture debug but again like above, FOG does not pick up the hardware and brings me to the white screen listing possible options.

    Thank you for your help.


  • @george1421Nothing changed, reinstalled 1.5.7. Sorry for the delay.

  • Moderator

    @joyboy11111 So what did you install?
    Has your installed version(s) (FOG host server and FOG version) changed?


  • @george1421

    After making all these changes FOG was not operational. I reinstalled FOG just so I could get some machines ready. Now that we are back at square one, do you have any ideas on a direction we can go?


  • @george1421

    rebooted, same results.

  • Moderator

    @joyboy11111 Since you are using Centos 6, that is Sys-V compliant OS so that would be service dhcpd restart or service dhcp restart. Or just reboot your server.

    Almost all modern Linux OS use systemd commands, which is what I gave you previously.


  • @george1421

    The command to restart dhcp did not work, but the information is what you wanted. SO yes eht0 is configured only for FOG, eth1 is configured for internet traffic. Eth1 is rarely up, only for updates.

    c466dda9-094c-407e-935d-cf4d00ec30a5-image.png

  • Moderator

    @joyboy11111 ok so it was dhcpd not dhcp

    So from your top picture you have 4 network adapters but only one is configured. That is OK I just wanted to make sure you didn’t have 2 interfaces active at one time.

    Before you do this net bit, restart the dhcp server with systemct restart dhcpd and then confirm if its running with the ps and netstat commands. If its not running again look at the log file.

    If the above fails or its complaining about an interface to bind to then do the following.

    If you look at the dhcpd file, in there should be a line like

    DHCPDARGS="";
    

    Change it to bind to the dhcp server to only eth0

    DHCPDARGS="eth0";
    

  • @george1421
    only way I would have done anything to sysconfig/dhcp is if you asked.

    3d40cb44-3c5a-4bc0-b68f-017806a79acd-image.png

    Your second command for sysconfig/dhcp was not correct.

    e8b19cd3-0245-4515-9650-8a1f0750158d-image.png

  • Moderator

    @joyboy11111 OK the no subnet error is a bit strange but move that into the subnet 192.168.1.0 section. That is what its complaining about. It should be global at that level, but whatever.

    Now did you fiddle with the configuration in /etc/sysconfig/dhcp? If not I need to see the output of these two commands

    ip a s
    cat /etc/sysconfig/dhcp


  • Moderator

    @joyboy11111 Well I would look at the /var/log directory either messages or syslog in there to see what the dhcp server is compaining about.

    tail -30 /var/log/messages
    or
    tail -30 /var/log/syslog


  • @george1421 Same issue results. When I run your netstat command nothing is returned.

  • Moderator

    @joyboy11111 Lets start with this.

    Connect to the fog server using putty or ssh

    mv /etc/dhcp/dhcpd.conf /etc/dhcp/dhcpd.conf.sav
    vi /etc/dhcp/dhcpd.conf
    i (to insert)
    

    Copy the following code out of your browser and the paste into the vi editor

    option space PXE;
    option PXE.mtftp-ip    code 1 = ip-address;
    option PXE.mtftp-cport code 2 = unsigned integer 16;
    option PXE.mtftp-sport code 3 = unsigned integer 16;
    option PXE.mtftp-tmout code 4 = unsigned integer 8;
    option PXE.mtftp-delay code 5 = unsigned integer 8;
    option arch code 93 = unsigned integer 16; # RFC4578
    
    use-host-decl-names on;
    ddns-update-style interim;
    ignore client-updates;
    next-server 192.168.1.41;
    authoritative;
    
    subnet 192.168.1.0 netmask 255.255.255.0 {
        option subnet-mask 255.255.255.0;
        range dynamic-bootp 192.168.1.50 192.168.1.75;
        default-lease-time 21600;
        max-lease-time 43200;
        option domain-name-servers 192.168.1.4;
        option routers 192.168.1.254;
     
        class "UEFI-32-1" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
        filename "i386-efi/ipxe.efi";
        }
    
        class "UEFI-32-2" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
         filename "i386-efi/ipxe.efi";
        }
    
        class "UEFI-64-1" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
         filename "snponly.efi";
        }
    
        class "UEFI-64-2" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
        filename "snponly.efi";
        }
    
        class "UEFI-64-3" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
         filename "snponly.efi";
        }
    
        class "Legacy" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
        filename "undionly.kkpxe";
        }
    
    }
    

    Write and then Exit vi

    systemctl restart dhcp
    ps aux | grep dhcp
    

    The ps command should show there is the dhcp service running. You can also test with

    netstat -an | grep :67  
    

    That should return with something like

    tcp4     0.0.0.0:67
    

  • @george1421

    I updated the config file to match the wiki, leaving my ip settings. I replaced all the instances of ipxe.efi with snponly. Restarted DHCP and now nothing will pxe boot. It just sits at >>start PXE over IPv4, and times out. I went back into look at the config file and it looks empty, like everything I entered and saved is now gone.

    I am about ready to see if I can start a remote session with you to see if you can straighten this out. Again I apologize for taking so much of your time.

    729acde3-932a-4ead-9417-f1056d748420-image.png

  • Moderator

    @joyboy11111 So the file may have been open with vi or nano when the computer was rebooted or you have the file open in another session on the server. If the swap file was created previously before a reboot you can delete the file. In the same directory as that file there should be a .swp file. You can remove that file so you won’t get that nuances message.


  • @george1421 It does give me a warning about a swap file when I go to view the config.

  • Moderator

    @joyboy11111 Did someone hand edit that file? I find it strange that it doesn’t match the fog supplied configuration file.

    You can remove that static filename stanza line and insert the class definitions from the wiki page. Then reboot the dhcp server.

    The ways its currently configured that dhcp service will only support booting bios based computers via PXE.


  • @george1421

    There is nothing below Filename “undionly.kpxe” just blank. I tried to the search from tom /ipxe.efi, nothing, no results. should I copy and past those lines from the wiki for the rest of the config file?

    fb307ae7-9e6a-412f-9c03-f2ca776d99d8-image.png

  • Moderator

    @joyboy11111 If the FOG installer created the dhcp server configuration it should look similar to this: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Example_1

    If you scroll down in the screen shot you posted you will see this section

        class "UEFI-64-1" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
         filename "ipxe.efi";
        }
    
        class "UEFI-64-2" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
        filename "ipxe.efi";
        }
    
        class "UEFI-64-3" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
         filename "ipxe.efi";
        }
    
    

    so for the uefi-64 entries you want to change filename varialble to snponly.efi

335
Online

8.2k
Users

15.0k
Topics

141.5k
Posts