Host registration error.
-
@erasp21 said in Host registration error.:
There were three options for Host Based MAC Address.
So what was the default setting for this value?
-
The default setting was “System Address”.
-
Hello.
In the BIOS settings of the PC
Advanced --MAC Address Pass Thruough
“System Address” (default)
I feel that the problem is that FogServer reads the USB Type-C NIC MAC Address when trying to register the Host.How can I make FogServer read only the MAC Address that my PC has?
-
@erasp21 said in Host registration error.:
I feel that the problem is that FogServer reads the USB Type-C NIC MAC Address when trying to register the Host.
This is something deep down in how firmware (UEFI), NIC adapter and probably the OS driver handle things. It’s not something we can change in FOG. Well there might be special driver options you could set via /proc in FOS but I really doubt you can change that behavior of which MAC is seen.
-
@george1421 it looks like you hit the nail on the head here. I’m having this same issue with a hp 1040 g7. After disabling MAC passthrough in BIOS I was able to capture an image! Deploying is similar, disabling mac passthrough and everything is good!
-
@jpolk91 said in Host registration error.:
disabling mac passthrough and everything is good
Just to help me and the OP of the thread. Disabling mac pass through and imaging a second computer. Does FOG see that second computer’s mac address as already registered. Or you have to register the second computer with FOG, which gets a different mac address.
Since I don’t have HP on my campus we need to fully understand this feature because I’ve seen an uptick in posts regarding this issue.
-
@george1421 sure.
With MAC pass through disabled FOG registers the MAC of the adapter, so if you use a different adapter for the computer receiving the image it will need to be registered. If you use the same adapter as the computer that uploaded the image it will not.
However, even if you use the same adapter to deploy as you did to upload it seems MAC pass through needs to be disabled on the receiving machine as well or it will error out before deploying. This could be wrong though, I haven’t thoroughly tested it, just tried it on one machine one time.
Let me know if you want me to try anything. I should have one or two of these machines for a little while yet.
-
@jpolk91 @george1421
Hello, everybody.
I have 5 HP 830 G7 kitchens.
Therefore, please let us know if you would like us to try something. -
@erasp21 said in Host registration error.:
@jpolk91 @george1421
Hello, everybody.
I have 5 HP 830 G7 kitchens.
Therefore, please let us know if you would like us to try something.My hope is to use the MAC address that Laptop originally has with MAC pass through enabled.
-
@jpolk91 @george1421
Hello, everybody.In the BIOS settings of the PC
Advanced–MAC address passthrough
“System address” (default)How about giving FogServer a little image gift by recognizing only the MAC address that the PC has?
-
@erasp21 said in Host registration error.:
How about giving FogServer a little image gift by recognizing only the MAC address that the PC has?
Not sure what you mean by “image gift” but what you seem to ask is not in the FOG servers hand. Depending on the firmware settings and maybe also drivers (iPXE using different ones than FOS Linux and different to Windows) the MAC address seen by the FOG server is whatever is presented by firmware/settings/driver. Not much we can do about it.
-
I have the same problem. I enabled passthrough and FOG still gets the external MAC (from the docking-station) .
The interesting thing is that FOG reads the corrects MAC while doing this network stuff, seconds before that white main menu. I can read the correct MAC there!!
But when I try the full registration from the menu, FOG compares the other MAC.
This is weird. -
I know this thread is old, but I am adding onto it with my research and findings.
My experience with this issue is only with HP computers, so no idea how other manufacturers do this.
HP’s firmware is written in a way that MAC address passthrough only works using HP thunderbolt docks, on Windows, using the correct dock drivers. MAC address passthrough also does not work with USB-C to Ethernet adapters because the adapters are not thunderbolt. Given this information, FOS out of the box would not be able to access the MAC address passthrough.
Judging by the Linux kernel patches I have seen online, adding this support to FOS would be pretty difficult since it seems like it depends on the network controller of each dock. This means that each dock needs to be programmed into the kernel and changes to that network controller driver need to be made as well.The other part of the issue is that iPXE gets the MAC address of the device in a different way than FOS. In my experience, iPXE gets the system MAC address (the same address that should get passthrough), while FOS gets the address that Linux gives through the
ip addrcommand.
I have read other threads where iPXE gives a different MAC address, but it wasn’t HP so I can’t check on that.I have a workaround that I did for HP computers which I have been testing for a couple weeks. The workaround is working for me, but I would rather do some more testing before putting out a tutorial.
-
Two years later and I just ran into this on a Dell Latitude 5330 with a Dell USB-C to Ethernet adapter.
Here’s my summary,
Using the latest bzimage, FOG was able to use the registered the passthrough MAC that is baked into the BIOS.
Image capture and deploy went fine, but everything FOG related in Windows reported that the client wasn’t registered. Because I didn’t check for a driver for the USB-C to Ethernet adapter, windows used the generic Microsoft driver for the adapter and FOG (and all of windows) sees the USB-C to Ethernet adapter’s MAC address.
As soon as I installed an up to date Realtek driver, Windows started using the BIOS passthrough MAC and everything works as normal.
-
@mbuteyn Hey there, running into this problem myself with Dells. So you installed the realtek drivers for the specific usb-c NIC you’re using? Which bzimge are you using as well? I have March 5, 2023
5.15.93
AMD/Intel 64 Bit and 32 bit but no luck. -
@typotony This is an old thread and a lot of things have changed since it was started. It probably would be in your best interest to start a new thread.
You might need to explain where its failing (in the new thread).
Does the computer PXE boot?
Do you get to the iPXE menu?
If you can get to the FOG iPXE menu, if you select hardware check does FOS Linux (a.k.a the kernel) detect the USB Nic? -
@george1421 Thanks for responding. I’ll go ahead and create a new thread. Thank you!
