Posts made by cschneider.tech

@cschneider.tech said in Boot From USB:

I’ve got FOG 1.3.0 RC 10 and it’s not working for me either. PXE works flawlessly but for those machines out there that don’t have a NIC, wouldn’t be able to leverage this feature (obviously).

The message says:

Remove disks or other media.
Press any key to restart

Wonder if it’s a UEFI vs Legacy issue

I got it to work… Here’s what I did…

I downloaded the ISO that jbsclm created in this post: https://forums.fogproject.org/topic/6202/boot-from-usb-stick-to-get-fog-menu-for-machines-without-pxe/5 (here is the direct link - https://forums.fogproject.org/uploads/files/1448223533241-ipxe_ask33.zip)

I then created a bootable ISO using Rufus and the dowloaded ISO: https://rufus.akeo.ie/

Once I tried to boot from the USB, it loaded iPXE where I could then enter in the IP of the DHCP and FOG server to establish the connection.

I’ve got FOG 1.3.0 RC 10 and it’s not working for me either. PXE works flawlessly but for those machines out there that don’t have a NIC, wouldn’t be able to leverage this feature (obviously).

The message says:

Remove disks or other media.
Press any key to restart

Wonder if it’s a UEFI vs Legacy issue

@george1421 Everything is golden. Thanks george!

That seemed to do the trick! Don’t know why I didn’t try that…

What does -y do?

Server

• Version: 1.3.0-RC-10
• OS: CentOS 7.2.1511 (Core)

Description

I’m having an issue installing, from scratch, the 1.3.0-RC-10. It fails at php-bcmath… So far everything has been a success all the way up to installing php.

Any ideas? I’m a novice

@george1421 Again, sorry for that! I’m usually one who measures twice and cuts once!

We’re using Gigabyte Brix machines in our environment. The models range but all have Realtek unfortunately.

The DHCP is Windows Server 2012 R2. Also a domain controller, though not Primary. It’s NOT the firewall, as we use a WatchGuard appliance.

I suppose instead of wasting devs time, I can try to disable RSTP or enable PortFast (FastLink) to see if that resolves the issue

@george1421

Sorry George! Turns out I made a typo. Of course that’s confusing! (I’ve made the change in the original post)

The DHCP server is 192.168.13.203
The FOG server is 192.168.13.236
The Gateway (firewall) is 192.168.13.1

I tried to boot once more a little bit ago and took a screenshot. Here it is (only change is the client IP had a different lease):

@george1421 said:

From your screen shot above the PXE boot rom is picking up the IP address [192.68.13.236 ] but its not able to open the file from the tftp (FOG) server.

Your second attempt to tftp is confusing me a bit. What is the address of the fog server? It can’t be [192.68.13.236] because that is what the PXE boot rom picked up from the [192.168.13.203] dhcp server.

This command should be like this
tftp <fog_server_ip> GET undionly.kpxe

If this fails then you have something messed up in the fog server configuration.

192.168.13.236 is in fact the IP of the FOG server. It’s not explicitly reserved in DHCP, however. I wonder why the client IP is 192.68?! I don’t understand why it’s pulling .68 and not .168?!

When I run command tftp <192.168.13.236> GET undionly.kxpe it returns “The system cannot find the file specified”

is it trying to find the file at the root directory? Shouldn’t I be telling the command WHERE the file lives? e.g. - the full path to the ipxe folder

Thanks for your guys’ replies!

Spanning tree is not required but I would like to keep it there as it’s incredibly helpful. I’m using RSTP not STP. Port Fast (Fast Link in Netgear terms) is definitely an option. I can try to enable this on the port that the FOG server is connected to but I think it’s all or nothing.

It really does sound like STP is the culprit here! Getting closerrrr!!!

Hey Guys,

I’m definitely not a linux guru as proven by my countless hours in trying to solve why my clients can’t boot to the FOG server via iPXE.

I’m running CentOS 7 with FOG build 6064. I’ve ensured that my DHCP is configured with Options 66 (IP of Fog server) and 67 (undionly.kpxe). I’ve ensured all passwords (except database) are set to the same thing.

When I boot from the NIC, the following is displayed and then immediately tries to load the OS on the box:

      **Initializing and establishing link…
      CLIENT MAC ADDR: XXXXXXXXXXX GUID XXXXXXXXXX
      CLIENT IP : 192.168.13.36     MASK: 255.255.255.0     DHCP IP: 192.168.13.203
      GATEWAY IP: 192.168.13.1

      PXE-E32: TFTP open timeout
      PXE-M0F: Exiting PXE ROM**

I’ve tried to tftp via windows but it also fails. I know the tftp service is running as well (systemctl status tftp).

     **C:\Users\USERNAME>tftp 192.168.13.236 GET undionly.kpxe.
     Timeout occurred
       Connect request failed**

ANY HELP would be appreciated. I love FOG and would love to use it in this new environment.

Thanks!

EDIT: I do have Spanning Tree Protocol enabled on my switch stack if that matters

@arnaudrigole said:

Hi,

Thanks for your fast response!!!

10.1.18.180 (fog server IP) is defined on option 66
undionly.kpxe is defined on option 67

The reason why those options are not defined directly is not simple…
Orange, our service provider for IP phones, used our DHCP options to load the AASTRA phones firmware by PXE, to simplify the configuration…
Then, these reboot on dedicated voice vlan… (F*CK)… so i’m forced to find a solution to skirt this… Precision : i havent used FOG as DHCP server, did i had to?

When i boot on NIC; thats steps are displayed:
1/ Initializing and establishing link…
2/ CLIENT MAC ADDR: XXXXXXXXXXX GUID XXXXXXXXXX
CLIENT IP : 10.1.19.233 MASK 255.255.0.0
GATEWAY X.X.X.X

3/ PXE-E32: TFTP open timeout
4/ PXE-M0F: Exiting Intel Boot Agent

Selected boot device failed, press any key to reboot…

Did this problem get solved? If so, how? I am having the EXACT same problem even after upgrading to build 6064

@george1421 Great instructions!

I can’t seem to get this to work though When I do this exactly as you have laid it out, this is as far as I get until it tries to boot into the Windows 7 OS I’m trying to capture an image of.

Perhaps it’s an issue with the TFTP server? I have all defaults through the FOG install other than the SQL (MirandaDB) database password.

Any help would be appreciated!