Developers

@bwenig Did you setup the DHCP yourself or is this the DHCP FOG put up for you when you ran the FOG installer?

@mwilcox Just a quick hint on this from my side. As far as I see you have two physical network interfaces and FOG running in VirtualBox, right? Don’t confuse VirtualBox’s NAT setting with the NAT George proposed to enable in the FOG Server!! I reckon you need to set both VirtualBox network interfaces to Bridge Mode so they act as much physical interfaces as possible. Then look into the NAT stuff in the FOG Linux OS…

@bwenig Sure, FOG can image UEFI machines since many years!

The difference is you need to provide another iPXE binary for UEFI machines within your DHCP server configuration.

What kind of DHCP (and version) do you use?

@rogalskij From the log we see that the client keeps receiving Middleware::Response Invalid host. This means the MAC is somehow already known to FOG so it doesn’t wanna register this “new” machine through the client.

Probably best to take a look at the database directly. Take a look at the SQL queries in this topic: https://forums.fogproject.org/topic/12078/i-don-t-see-some-hosts

@3mu Thanks for the update. I will take a look at this when I have more time.

I’ve seen this request but not quite sure how to move forward.

Please understand, Access controls, with this iteration of FOG Server, are coded after the fact.

What do I mean by this?

FOG didn’t really have any real security controls in place. You, indeed, needed to be logged in to do actions of course, but there weren’t any utilities in place for “modifying” access.

For a period of time, there was a thing called “mobile” user which basically just allowed a user to use a mobile interface. This interface was coded along side the FOG system, and was a cumbersome tool to maintain. So when we moved to a responsive design, I removed that “mobile” gui as the new GUI is also mobile accessible.

The Access control plugin is a huge leap toward getting a tool available to limit access based on rules/roles etc…, but it’s not a perfect system as it relies on the User existing in the database first.

I’m sure we could work to add a utility to enable a “default” role association but right now it doesn’t exist.

@3mu said in FOGSnapinReplicator.service failing on fresh install:

Install FOG with no router, DNS server = the FOG server IP (with no DNS server running)

Thanks for the details. Though I still need to clarify this point. Maybe I am able to figure out the root cause of this and even prevent from it in our setup.

So when you say DNS server, do you mean the FOG installer option/question that is asking for DNS server or just standard Linux DNS server setup though /etc/resolv.conf?

@icescout27 As I said, it used to be fog but now fogproject is used. You are not meant to play with this. As well you shall not use this account to login to your FOG server.

Please run ls -alR /media/fog/External ; mount and post output here.

After changing the username field to fogproject in both the .fogsettings file and Default Storage node I am still receiving the same error as specified in the original post.

That is impossible. At least you should see the username changed in the error output. Saying you get the same error message is not of much help because you might overlook something important. Please take another picture of the new error screen and post here.

@zyzhang @george1421 Nice we seem to have finally figured it out!

@Oleg60 Beside forcing an error like George said there are other ways to get to the shell. Either you edit /tftpboot/default.ipxe and make the first two lines read like this:

#!ipxe
shell

The rest of the original script can stay as is. If you exit the shell it will execute the rest of the commands. Be aware that all your PXE booting machines will run into the shell no matter what!

The other simple way is to create a new iPXE menu entry (web UI -> FOG Settings) and use the shell command with that. This way you have a new menu entry that you can choose to get to the iPXE shell on PXE boot up.