Posts made by foguser

@george1421
i dont know how much more time i will invest in this.
I maybe just try to build a mini-network to be able to use fog.

I really dont care too much if its all automatic. I also saw the article on how to change the bios/uefi file for machines.
As i saw so far i only have to use uefi-machines, so it wouldn’t matter.

As it came out today, option 11 isnt needed anymore. I used the ip for option 66 and ipxe.efi for 67.
I installed wireshark on the notebook and made a test with ipconfig /release and /renew.
The notebook received the correct ip, filename and destination server with the dhcp offer.
When i bootet it again, it did not care again and just downloaded the citrix nbp-file.
Is there some sort of cache involved on the dhcp-server or client that i maybe have to flush/configure?
The citrix-environment is really the main focus in our company. We have well over 100 clients using this daily and i’m not the caretaker for this service. So my goal is to get it working with changing as little as possible on the citrix service.

I opened up all ports on the fog server, to make sure nothing is blocked, but i was again only seeing dhcp requests and discoveries. Not to my surprise because the client does, as mentioned above, never try to boot from there.
Something special about that was, that for each dhcp-request on port 67/68 (dont know exactly anymore) a ‘destination unreachable port unreachable’ answer was generated. i dont know why or where this should come from, as i have opened all input traffic.
Im not at work right now and i’ll see if i get the time to provide something too look at. Maybe i just have time in the evening (like now) to add some more detail.
Another question: We have a kind of test-environment based on a seperate vlan.
Does a vlan matter if all traffic is handled on the same one? generally is a vlan a problem?
I can ping the fog-server from the notebook / other clients, so the connectivity is there.

I try to answer to both of you, so here we go.

We have a set of clients provided with the service of the pxe citrix server. Notebooks are not part of this (locally installed, no need for pxe-boot until now). I plan to configure them on the dhcp once and leave the options as they are, no switching after that. So every device just needs one service, fog or citrix.
The Citrix server provides the client with a streamed image. The dhcp Option 11 is set for this and have been a few years untill i installed fog some days ago.
The options 11, 66 and 67 are configured on the scope of the client network to use the citrix pxe. No individual options until fog.
The main Problem i still have is, the Notebook boots and gets the address and file of the citrix server.
He gets the correct ip and the option 11 as configured (i tested “not configured” but set which ends either in an error that there is no option 11-> streaming aborted and i tried the ipadress of the fog-server, that he will try to connect to for a few seconds only to boot and do it again)
I tried:
option 11: empty(but set) and fog-ip
option 66: ip of the fog-server and a-record -> servername resolved by dns to the address
option 67: undionly.kpxe just to test, ipxe.efi (notebook uses uefi)
All configured directly on the dhcp-reservation. Do i need the Policy/vendor class?
I thought the individual configurations on a reservation are prioritized in every case of configuration.
The DHCP-Server is Windows Server 2012 R2.
In a recent wireshark capture on the fog server i saw some dhcp-requests and discover due to the dhcp-relay configured on the router but nothing other than that between the network/hosts.
I keep trying to figure out why the DHCP-options arent used to boot. I think thats the first and maybe only problem i have to solve.

Hello

I’ll try to include as much Information as possible without getting too long.
I’m on a Project right now to install FOG in an existing infrastructure.
The Idea is to Image fat clients from the client network and deploy them onto other devices.

There are 3 Networks involved:
172.16.8.0/24 - DHCP/DNS-Server(Windows Server), citrix pxe Server
The Citrix Environment needs to stay.
172.16.21.0/24 - VMs such as the FOG-server (hosted on VMware ESXi)
172.16.28.0/23 - Clients booting from the citrix Server and fat clients like Notebooks.

I have installed FOG on an Ubuntu 18.04.2 Server.
I did not know how to configure my existing dhcp on fog because it is in a different subnet.
The Clients receive the correct ip from the DHCP-reservations.
Here is a short summary of the Installation:
Option 2 - Debian based
reinstalled apache… files (y)
Normal Installation
didnt Change ip in use (correct)
didn’t Change interface (n)
no router address configured (n)
dhcp does not handle dns (n)
no dhcp on fog (n)
language support (y)
accept, mysql Password…
I’m able to Access the web interface and tried to add my test-Client manually (just the Name and MAC) so fog would recognize a dhcp-request for it, but without luck.

The fog Server uses cntlm to authenticate to the Proxyserver.
I had to download the binaries for the fog installation manually but didn’t have any other Problems.
We added a dhcp-relay on the router for the fog-server. All other Servers (dhcp and citrix pxe) are allready configured.

The DHCP-Options are configured to use the citrix pxe by Default (all reservations have Options 11, 66, 67 set for that by default)
I can manually configure Option 66 and 67 for the Clients to use fog.
I replicated the scope to all other DCs and checked it, but the Client did not care at all.
He kept booting and finding the citrix server-ip and file.

I tried george1412’s instructions in his post:
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
and captured the traffic.

I will try to capture some traffic with Wireshark tomorrow, so i can check on outgoing traffic.

Finally my Questions are
Did i do anything wrong in the Installation of fog?
Have i forgotten/overlooked a configuration to get this to work?
Is it even possible to get this to work?

Im not at work right now but i can add more details if needed.
Any help is much appreciated, thank you in advance.