Posts made by michaeloberg

@george1421

Here is the screenshot from the BIOS:

@george1421

I apologize, I have way to many things going on right now. 6c:02:e0:86:07:45 is the MAC of the machine in the BIOS:

3c:18:a0:cb:3f:b7 is the MAC of the HP Dongle - Part # 855474

3c:18:a0:cb:3f:b7 shown in the following 2 captures (the first Windows ipconfig, the second Deepin) are of the HP Dongle, not the system address:

Again I am so sorry about the confusion.

So recap, IP in iPXE is correct, IP in FOG is recognizing the Dongle MAC. I did change my 067 Bootfile Name in DHCP to snponly.efi and it PXE boots, but FOG still reports the Dongle MAC.

Michael

@george1421
I am not sure why iPXE is showing 6c:02:e0:86:07:45 (I initially thought this was the SYSTEM MAC, it is not).

The MAC that FOG is reporting, 3c:18:a0:cb:3f:b7 is the Dongle MAC.

The BIOS is set for “MAC Addressing Passthrough - System MAC”

The MAC Address of the system is 3c:18:a0:cb:3f:b7

Here is a screenshot of the windows cmd ipconfig /all:

@george1421 @Sebastian-Roth

I updated iPXE and I have the same results, the MAC address recognized by FOG is the Dongle MAC, not the System MAC.

Here is a screen shot before the iPXE update, note the (g4bd0) hex number:

Here is a screenshot after the iPXE update to verify the current date using ls -la /tftpboot/*.efi

Here is a screenshot after I updated iPXE, note the (g98625) hex number:

And finally here is what it looks like when I boot to FOG and choose “Client System Information (Compatibility)” then choose option 6 - Display MAC Address (displays the Dongle MAC):

Hopefully this is enough information to get us through to the next step, I appreciate the help.

Michael

@sebastian-roth
In Windows, the computer shows the correct (System MAC) not the Dongle MAC.

Deepin (full version 20.3) also shows the correct (System MAC) not the Dongle MAC.

Also when PXE booting, before it enters FOG, it does show the system MAC correctly. I opened a ticket with HP and these are some of the troubleshooting steps they had me do to isolate the problem to FOG and not the BIOS/Windows and in this case a GUI version of Linux (Deepin).

First, thank you to everyone for your continued support and efforts for those of us running FOG.

I have 515 HP Probooks that will not register with FOG correctly. IPXE is showing the correct MAC of the computer, but FOG is showing the MAC of the USB Type-C Dongle.

Here is what I can tell you:
Brand new installation of Debian 10 with FOG 1.5.9 and the latest Kernel 5.10.71

I set this box up as a new server and purposely did not migrate my Database over as I had over 100 images and thousands of clients. I wanted to clean this up and now is a great time as I have all new hardware. Last week we were able to get my Dell 7420 laptops passing the MAC through the docking stations by updating to the latest Kernel, however this did not fix the HP Laptops. The HP Laptops are using a dongle - Part # 855474-003

In researching on my own, I found a known issue with these dongle from HP’s website. I found a flash utility that updates the dongle and tried this on multiple ones with no avail.
https://support.hp.com/us-en/document/c07022776

Thanks in advance,

Mike

@sebastian-roth Correct, expect this time I am not importing the DB from my old fog server, new server, new images, new everything. I will open a new topic specific to the HP Probook 430 MAC Address Passthrough issues.

Thanks Sebastian for your help, I appreciate every you do for the FOG Community.

Mike

@sebastian-roth said in New FOG Server doesn't recognize System MAC Address:

@michaeloberg I was wrong again. The output looks fine. So something went wrong when you updated the kernel. Did you update 32 bit (bzImage32) and 64 bit (bzImage)?

If updating through the web UI doesn’t work you can still do it manually (as root

cd /var/www/html/fog/service/ipxe
mv bzImage bzImage.orig
mv bzImage32 bzImage32.orig
wget https://fogproject.org/kernels/bzImage
wget https://fogproject.org/kernels/bzImage32
chown www-data:www-data bzImage*
file bzImage*

Post the output of the very last command here, just to make sure.

root@SVR-FOG:/var/www/html/fog/service/ipxe# file bzImage*
bzImage: Linux kernel x86 boot executable bzImage, version 5.10.71 (sebas tian@Tollana) #1 SMP Sat Oct 9 01:18:49 CDT 2021, RO-rootFS, swap_dev 0x8, Norma l VGA
bzImage32: Linux kernel x86 boot executable bzImage, version 5.10.71 (sebas tian@Tollana) #1 SMP Sat Oct 9 01:13:46 CDT 2021, RO-rootFS, swap_dev 0x8, Norma l VGA
bzImage32.orig: empty
bzImage.orig: Linux kernel x86 boot executable bzImage, version 4.19.145 (seba stian@Tollana) #1 SMP Sun Sep 13 05:35:01 CDT 2020, RO-rootFS, swap_dev 0x8, Nor mal VGA

It looks like this resolved our issues with the Dell 4720 units, the HP 430 Probooks still however show the USB Type - C MAC and not the system MAC, we are getting closer!

@sebastian-roth said in New FOG Server doesn't recognize System MAC Address:

ls -al /var/www /var/www/html

/var/www:
total 20
drwxr-xr-x  4 root     root     4096 Nov 24 11:18 .
drwxr-xr-x 12 root     root     4096 Nov 24 11:17 ..
drwxr-xr-x 10 www-data www-data 4096 Nov 24 11:21 fog
drwxr-xr-x  2 root     root     4096 Nov 24 11:19 html
-rw-r--r--  1 www-data www-data   52 Nov 24 11:18 index.php

/var/www/html:
total 20
drwxr-xr-x 2 root root  4096 Nov 24 11:19 .
drwxr-xr-x 4 root root  4096 Nov 24 11:18 ..
lrwxrwxrwx 1 root root    13 Nov 24 11:19 fog -> /var/www/fog/
-rw-r--r-- 1 root root 10701 Nov 24 11:17 index.html

@sebastian-roth said in New FOG Server doesn't recognize System MAC Address:

@michaeloberg Well if you didn’t mix up the information and I am pretty sure you haven’t it’s as easy as updating the FOS kernel (Web UI -> FOG Configuration -> Kernel Update: 5.10.71 is the latest as of now, and still pretty solid as people have been using it for weeks already). That should give you a newer kernel on the newer server and fix the issue you described.

PS: Leave the pass-through setting in the UEFI/BIOS as is.

I followed the steps you mentioned, it said it downloaded and installed the Kernel, but when I look at the GUI it shows this:

When I run the bzImage command in Putty it shows this:

/var/www/html/fog/service/ipxe/bzImage: Linux kernel x86 boot executable bzImage , version 4.19.145 (sebastian@Tollana) #1 SMP Sun Sep 13 05:35:01 CDT 2020, RO-r ootFS, swap_dev 0x8, Normal VGA

Also testing the machine in PXE still shows the Dock MAC address. Is there a command I need to run in the CLI to process the downloaded Kernel from the GUI?

@sebastian-roth said in New FOG Server doesn't recognize System MAC Address:

file /var/www/html/fog/service/ipxe/bzImage

Old Version of FOG:
MAC is Registered as the System MAC: 38:14:28:d1:63:c1

/var/www/html/fog/service/ipxe/bzImage: Linux kernel x86 boot executable bzImage , version 5.6.18 (sebastian@Tollana) #1 SMP Tue Jun 16 16:55:16 CDT 2020, RO-roo tFS, swap_dev 0x8, Normal VGA

New Version of FOG

MAC is Registered as the Docking Station MAC: b0:7b:25:97:5d:fb

/var/www/html/fog/service/ipxe/bzImage: Linux kernel x86 boot executable bzImage, version 4.19.145 (sebastian@Tollana) #1 SMP Sun Sep 13 05:35:01 CDT 2020, RO-rootFS, swap_dev 0x8, Normal VGA

**Where do I check the UEFI settings? On the system, Dell 7420, it is in the BIOS, settings are below. Do note this is the same unit that works on 1.5.7 and not 1.5.9

@sebastian-roth

Old:

New:

After a long battle troubleshooting USB Type-C NIC adaptors/Docks and my old FOG server, I have decided to build an entirely new server with Debian 10 and FOG 1.5.9.

I still have my old FOG server running in parallel with the new server, I am simply changing the DHCP Option 66 in DHCP to point from the old and new servers in my troubleshooting.

When I PXE boot a system on the new installation of FOG, it is recognizing the docking station MAC and not the system MAC, so when I register a new device, reboot, it says the device is not registered. These units are Dell 7420 with the WD19 Dock. They worked fine on the old version of FOG (Ubuntu/1.5.7).

When I change the DHCP Option 66 back to my old server, FOG recognizes the system MAC. This tells me the compatibility of the system is there and that the BIOS is set correctly.

I am at my end with this, I have rebuilt the server again this morning thinking that after I imported the Database from the old server, it could have corrupted the new server. Not the case this time as I even manually entered my AD information and settings in the FOG GUI. It is 100 percent clean and I have NOT updated the version of iPXE as I tried that on the previous install of the new server and that did not work either. Is there a setting in 1.5.9 that tells the dock to pass the system MAC?

Thanks in advance.

Michael

@michaeloberg said in Issues with USB Type C NIC Adaptors:

@kghli @george1421 @Sebastian-Roth

This could be a breakthrough. I just noticed that the system is passing the address through iPXE correctly and that FOG is what is recognizing the USB Type-C dongle’s MAC address - the exact scenario that @kghli is experiencing. I took a screen shot of the issue and here is the iPXE address (which is the correct system address):

Then when I boot to FOG (now running Debian 10.11 and FOG 1.5.9, and choose “Client System Information” then choose “Display MAC Address” it show’s the USB Dongle’s MAC:

Hopefully this is going to help troubleshoot our issues as we have narrowed it down to FOG alone, not the manufacture of the system, the BIOS configuration or the version of FOG.

Thanks in advanced!

Mike

I also recompiled iPXE from (g4bd0) to (g1844a) and verified the date (ls -la /tftpboot/*.efi) was today and it still is not working.

@kghli @george1421 @Sebastian-Roth

This could be a breakthrough. I just noticed that the system is passing the address through iPXE correctly and that FOG is what is recognizing the USB Type-C dongle’s MAC address - the exact scenario that @kghli is experiencing. I took a screen shot of the issue and here is the iPXE address (which is the correct system address):

Then when I boot to FOG (now running Debian 10.11 and FOG 1.5.9, and choose “Client System Information” then choose “Display MAC Address” it show’s the USB Dongle’s MAC:

Hopefully this is going to help troubleshoot our issues as we have narrowed it down to FOG alone, not the manufacture of the system, the BIOS configuration or the version of FOG.

Thanks in advanced!

Mike

@george1421 @Sebastian-Roth

OK - Update with the USB Type C NIC Adaptors:

Last night I built a new Fog Server running Debian 10.11 and FOG 1.5.9

That said I should be up to date with the OS and Fog software.

The problems continue with the HP Probook 430 Laptops, the MAC Address of the host registered in fog is the dongle and not the system address.

I made sure the MAC-Address Passthrough option is set to “system” in the BIOS. And in windows it works properly - it is only in the preboot environment that the MAC address doesn’t work correctly.

I also have 134 Dell 7420 laptops and they work fine, so I tried the USB Type C dock that I imaged all of the devices with and same thing, the host registers the Dock and not the system address.

Any ideas on this? HP support only provides the MAC-Passthrough to the native OS and not the preboot environment, it is beyond their scope of support.

Thank you,

Michael

@george1421 Hello! I fired up a new VM and installed Debian 10.11 (buster). I did a modified installation from the YouTube video you shared, I did partitioning based on this video - https://wiki.fogproject.org/wiki/index.php?title=Debian_8

I installed 1.5.9 and setup the DB and changed the fog default password.

My next question is - can I export my settings off of my old FOG server into the new one? Currently I have both VMs fired up so I can simply toggle between the two IPs in a tabbed browser.

Once I get the new server setup, I am going to change my DHCP and PXE settings on my Windows network to test PXE booting my new computers that use the USB dongle. I am going to be beyond thrilled if this works as I have several hundred of these machines that need imaged.

Thank you so much for your help and look forward to your response!

Gratefully,

Michael

@george1421 Thanks, I will give that a try in the morning. Thanks for the nudge in the right direction - much appreciated!

@sebastian-roth Thank you for the information, I appreciate everything you do for the entire FOG community. As a novice user, I am trying my absolute best to navigate through this mucky situation where my new computers will not boot to PXE using a USB dongle. I have another thread open for that issue where it was suggested that it could be related to an end of life issue with Ubuntu 16.04. That said, I researched on the following page to get the latest information: https://fogproject.org/download - it lists the latest stable version of the FOG software (1.5.9) and two recommended Operating Systems: CentOS and Debian. Not familiar with either, I found the step by step video that Wayne made on Debian to be useful and choose that OS and downloaded it from https://www.debian.org/. Now I understand operating systems come and go, but I downloaded Debian 11 today directly from their website. If this operating system is not supported, can you provide me with a current OS recommendation?

Again I apologize for the incredibly elementary questions I have, following the steps in the video located here https://wiki.fogproject.org/wiki/index.php?title=Debian_8
it is showing a different root prompt than I was experiencing. Please excuse my ignorance in the forum, I don’t want to waste anyone’s time or get free lessons on Linux. I am trying my best and with be grateful for anything you can answer.

I recently fired up a new VM, Debian 8 vr 11.

I followed every step in this video except for the name of the server as I already have a fog-server (old running Ununtu 16.04). This one is named SVR-FOG.

https://wiki.fogproject.org/wiki/index.php?title=Debian_8

After installing the OS, and enabling the password for SSH, I try to login using Putty to the IP but I cannot sign into root. If I use my account and type SU then the root password - it shows this:

I am attempting to run the command apt-get install git -y
but I am not at the # prompt. Mine shows /home/mike#
I don’t know what I did, maybe I have to start over. I am not sure why I cannot sign into the server straight away using the root username.

Any help would be appreciated.

Thanks,

Michael