Linux Client Install Dual Nics

[JasonNaughton]

Hi All,

I’ve been using the fog project for a while (5 years or so). I’ve been heavily relying on it to install various workstations. Today I ran into an issue that I never experienced before. I’ve installed clients with 2 nics without any issues. Normally the pxe boot would simply boot off of whatever nic was connected to the LAN. Today I was installing our standard image that I’ve been using for years, on a Dell Pro Max Slim workstation. Now I’ve installed this type of workstation in the past without any issues, but of course with only one nic. Today the system has 4 nics. Only 1 of the 4 nics is connected to the LAN. The system starts the PXE, and it appears to get it’s IP address and proceeds to the next stage. This time it gets it’s IP address but then scans through the remaining 3 nics… None of them have an IP address configured so they fail. It seems to forgotten that the first nic got the IP address without any issues. When it proceeds to go to the install stage it kacks out as it doesn’t believe it has a valid IP address. If I simply pull the 3 nics out and install the system everything works. Yet I have to re-configure the box with 4 nics in the end. Anyone have a way to tell the fog server, simply continue after getting the first card IP address. (ie stop searching for other nics).

[george1421]

@JasonNaughton Looking at the code the error would indicate that the target computer can’t reach the fog server.

https://github.com/FOGProject/fos/blob/8893d32bfb702dcf7b8f5427ccd6748fac15df17/Buildroot/board/FOG/FOS/rootfs_overlay/etc/init.d/S40network#L64

What I want you to do is to pxe boot the computer into debug mode. Schedule a deployment to this computer but before you hit the schedule task button tick the debug checkbox. Now pxe boot the target computer, you will still get the errors but you will be dropped to the fos linux command prompt.

run this command ip a s that should show if your network interface has an IP address. If not then issue this command.
/sbin/udhcpc -i enp128s31f6 --now where enp128s31f6 is the name I gleaned from your screen shot that appears to have picked up an IP address. See if it gets an IP address now. See if you can ping the fog server’s IP address.

The ‘checker’ script makes this call to verify your fog server is reachable.
curl -Ikfso /dev/null "${web}"/index.php --connect-timeout 5 replace the entire ${web} with the IP address of your fog server. See if that returns a value.

Finally search the system messages to see if there is something related to firmware.
grep -i -e firm /var/log/syslog I think syslog is the right file, if it returns nothing try /var/log/messages One error could be the network adapter needs a specific firmware for the network adapter to communicate. That firmware may need to be added to the linux kernel.