@george1421 Yes, I have the “em1” interface of the FOG server, and the network card of the Dell Computer I am trying to image on the same subnet.

The output of the “ip addr show” command on the FOG server is:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d4:ae:52:af:b5:63 brd ff:ff:ff:ff:ff:ff
    inet 150.155.1.70/20 brd 150.155.15.255 scope global noprefixroute dynamic em1
       valid_lft 704372sec preferred_lft 704372sec
    inet6 fe80::3d39:c85:7bf0:e61e/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: em2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d4:ae:52:af:b5:64 brd ff:ff:ff:ff:ff:ff

@george1421 Wait, you aren’t allowed to have the FOG server on the same subnet as the clients?! This is how we do most everything right now. We plan to subnet our devices later on, but previously with Ghost and other multicast products we just multicast with devices and the server on the same subnet. Is this still possible?

Additionally, the output of the command you specified “sudo ps aux|grep udp-sender” is:

root 13864 0.0 0.0 115300 1480 ? S Aug30 0:00 sh -c /usr/local/sbin/udp-sender --interface em1 --min-receivers 3 --max-wait 1200 --portbase 56590 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/BaseImage/d1p1.img;/usr/local/sbin/udp-sender --interface em1 --min-receivers 3 --max-wait 10 --portbase 56590 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/BaseImage/d1p2.img;
root 14393 0.0 0.0 8688 660 ? S Aug30 0:00 /usr/local/sbin/udp-sender --interface em1 --min-receivers 3 --max-wait 10 --portbase 56590 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/BaseImage/d1p2.img
root 31094 0.0 0.0 112708 992 pts/0 S+ 11:39 0:00 grep --color=auto udp-sender

As you can see, it sees the interface em1, unless I am wrong and em1 isn’t the name of the interface, but that is what it says when I do an “ip addr” command on the server.

@Sebastian-Roth I checked the Apache log you mentioned, but all I see from that day doesn’t make a ton of sense to me:

[Fri Aug 30 15:25:11.052318 2019] [mpm_prefork:notice] [pid 2739] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Aug 30 15:28:26.997884 2019] [core:notice] [pid 2727] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Aug 30 15:28:27.032137 2019] [suexec:notice] [pid 2727] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Aug 30 15:28:27.101535 2019] [lbmethod_heartbeat:notice] [pid 2727] AH02282: No slotmem from mod_heartmonitor
PHP Warning: Module ‘ldap’ already loaded in Unknown on line 0
[Fri Aug 30 15:28:27.268250 2019] [mpm_prefork:notice] [pid 2727] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.2.21 configured – resuming normal operations
[Fri Aug 30 15:28:27.268287 2019] [core:notice] [pid 2727] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’

Does this make sense? Am I looking at something wrong here?

@george1421 Yes, they are both on “vlan 1” for the moment. Both are on the same subnet.

I tried to look but the logs don’t provide all that much information to me. I believe my interface is “em1” and that is what I should be using. I have attached the logs for all to look at to see if anything can be ascertained from them. I read the link you sent but I don’t see anything I should change or do to rectify the issue. I really appreciate all this assistance from everyone.

Attached log files:
multicast.log.udpcast10.txt multicast.log.udpcast9.txt multicast.log.udpcast8.txt multicast.log

I have most things working correctly in FOG. One thing that is still not working properly is multicasting. When I attempt it with a known working image, the computers reboot just fine but then they get to the “partclone” screen and they never start imaging. I noticed in the “multicast” settings that my interface was some odd designation. I tried changing it to either “eth0” or “em1” to match the CentOS server settings but to no avail. Not sure what I am doing wrong. Can anyone assist? My desktop support team would love to image our computer labs with this on campus.

Multicast settings:

UDPCAST INTERFACE eth0

UDPCAST STARTINGPORT 62142

MULTICAST MAX SESSIONS 64

UDPCAST MAXWAIT 20

MULTICAST ADDRESS

MULTICAST PORT OVERRIDE 0

MULTICAST DUPLEX FULL_DUPLEX

MULTICAST RENDEZVOUS

This is the screen it gets stuck on:

@Quazz and @george1421 Thank you both. I appreciate the assistance. I tried ipxe.efi and it worked! I now have my Dell Optiplex models PXE booting using UEFI just the way I was hoping. Only oddities is the screens are a bit smaller, and the PXE boot shortcut is now “esc” instead of my custom shortcut. That is a small first world problem however. Thank you all again this community is fantastic!

I have this configured for my DHCP PXE section. I have omitted the ip addresses in favor of “x” in their place for network security reasons. The DHCP server is a linux server.

subnet x.x.x.x netmask 255.255.240.0 {
authoritative;
option routers x.x.x.x;
option subnet-mask 255.255.240.0;
next-server x.x.x.x;
filename “undionly.kpxe”;

I am currently using “undionly.kpxe” for option 67 as shown above. This works for legacy bios PXE but not UEFI. There are a bunch of files in /tftpboot and am unsure which “efi” file to use for uefi pxe booting.
0

I am attempting to get my Dell Optiplex models to PXE boot to the FOG server with UEFI. If we run legacy BIOS we can get them to PXE boot just as we would like them to, but if we enable PXE with UEFI it fails and then just boots to the hard drive anyway.

I can F12 it and boot it using the legacy BIOS PXE boot, but I would like to get UEFI working as we want to move to that for all our Optiplex models to boot from. I am using 64 bit Kernel 4.19.64 but I suspect I am missing something to get this to work. I really want this because I hear Dell is dropping legacy BIOS entirely very soon in coming models. Any assistance is appreciated. I am a FOG newbie just for context.

As always, the community comes through! Not sure how this got askew, but following these directions I was able to fix the issues. The image pulled correctly and at the end updated the database info. The image is good, I am all set. Thank you again this was awesome!

FTP seems to be failing after my image pull happens. When the image pull gets to the final stage it tries to use FTP or TFTP (not sure which) to update the database. It fails and says the login is incorrect (username “fogproject”). I had trouble originally with fogproject updating the kernel over FTP but got that fixed. Anyone have any thoughts on how to fix this so the image pull can complete successfully? I pushed an image with no troubles.

Error message at the end of the image capture is:

Updating Database…Failed
Error returned: Type 2, File: /var/www/html/fog/lib/fog/ftp.class.php, line: 464, Message: ftp_login(): Login incorrect., Host: [ipaddress], Username: fogproject

Have i messed up something here?

![alt text]

This is exactly what I was looking for. Added the LDAP plugin, then added the ldap php module and modified to the php config. I now have it working. This helped greatly thank you!

Is it possible to join the FOG server to Active Directory so that my tech staff can login to the server using their AD credentials? This would be extremely helpful from an enterprise perspective. Essentially I want the 10 or so admins to use their AD credentials instead of using local FOG credentials. Is this possible and if so how? I can only find information on joining imaging clients to AD after an image.