Dell Latitude 3340 with USB-C Ethernet Adapter - bad mac address registered

[pbriec]

Hi @Tom-Elliott

is there any workaround?
thanks

Pierre

[Tom Elliott]

@pbriec I suppose, what kernel are you currently using?

[pbriec]

@Tom-Elliott

how to check that?
I’ve seen that in FOG Configuration: bzImage and bzImage32
I’ve never updated kernel in FOG

[george1421]

@pbriec From the FOG web ui -> FOG Configuration -> Kernel update. It should tell you the current version and what is available. Download both the x64 and x32 bit version for the latest version of the FOS Linux kernel.

[pbriec]

@george1421 @Tom-Elliott

i’ve downloaded and installed the last kernel 6.1.63 (both x64 & x86).
I still get the mac’s dongle address in the compatibility menu. In debug menu, all is fine.

[Tom Elliott]

@pbriec The team and I in the background have been doing a lot a bit of testing.

Would you be willing to install the latest working-1.6 branch (or dev-branch)? I know this is technically an alpha, and will take a moment to get used to using, but functionally it should operate like normal just with a new UI:

cd /path/to/fog/installer
git checkout working-1.6
git pull
cd bin
sudo ./installfog.sh -y

This should download latest inits which, to the best of our knowledge works to set the mac.

You would need the domacset=1 setting.

Effectively, what this does, is it sets a new variable as part of the bootup called setmacto as the same as the mac address of the net0 adapter. (Thank you @george1421) If domacset is configured and this variable is set, it will do the network startup, get dhcp, check if the network is up and available, and then set that device to the setmacto MAC address, and reaccomplish DHCP since the MAC changed.

I have added this code to dev-branch as well, but if you’re willing to test the working-1.6 it’s worth it in my opinion (of course I would say that lol).

Of course if you aren’t comfortable testing the alpha, but okay with the iterative development (dev-branch) change the checkout to use that branch.

This should work though it does require (on registration) the domacset=1 at a global level - which I think is fine.

Also, the installer I have the argument -y this just means to ‘Auto accept’ as it may ask questions. If you’re uncomfortable with that method, please just remove the -y argument.

[pbriec]

Hi @Tom-Elliott,

So i’ve tested and it seems to work.
Now, i’ve the same MAC address both in compatibiliy mode and after dhcp process.
I’ve read again my notes and i can’t manager to wake up with WOL.
I don’t know what is wrong.
I will contact Dell tomorrow. I remember it was working before.
I’ve tested another laptop with ethernet, and it’s working fine.
The WOL processus could be unmanaged with usb ethernet adapter?

thanks
Pierre

[Tom Elliott]

@pbriec

I have modified the init’s that should automate the fixing of mac address when there’s a passthrough (variance of ipxe -> init) noticed.

You will no longer need the domacset flag defined, it will just do the action of setting the mac address as appropriate:

https://github.com/FOGProject/fos/releases/tag/EXP_20240618

Replacing the init files as required shoudl fix this issue and as we get new versions happening, this will become a standard.

[pbriec]

@Tom-Elliott

Ok, i’ve updated the init.xz and init_32.xz files. I confirm that i do not have to set the kernel args now.
I’ve registered the laptop from scratch and now it’s the correct mac address.

I’ve noticed some bad things with this new FOG.

An old laptop can be woken up and FOG create a task that is not automatically deleted after.
This new laptop with USB adapter cannot be woken up and the task is remaining in the actives tasks.

I’ve never managed to wake up this new laptop
In the new Fog, i have the following error: “DataTables warning: table id=host-snapin-history-table - Ajax error. For more information about this error, please see https://datatables.net/tn/7”
So it doesn’t start the PC, and if i wake up it manually, it will boot to fog trying to do something that failed.
refind also doesn’t boot correctly the PC.

So the new fog is fine about the mac address problem but the fonctionnalities are strange
Have you noticed that?

Pierre

[Tom Elliott]

@pbriec I don’t know what you mean by waking up an old laptop. I’m assuming there’s a task that you’re not able to see in the UI, but that was an imaging type of task (those are the type that do WOL)

As to why your new laptop is not able to WOL, i do not know if it’s because of the passthrough vs the actual MAC address of the adapter. You could test, but adding the true mac address of the adapter to the host and tasking to see if it wakes up. This is because the magic packet needs to indicate the burned in address (to my knowledge) for the interface to actually respond and kick up the system. Then again, i don’t know how an externally but connected (USB-C/USB-A) wire would tell the laptop to wake up. I could imagine it working on USB-C, but still having a bit more difficultly than a natively board mounted network card.

As for the host-snapin-history-table, I’m aware of the issue, but I have not yet been able to replicate it.

I’ll see if I can do so today, by creating a false entry.

Thank you!

[Tom Elliott]

@pbriec Figured out, I think, the issue of your host-snapin-history-table:

It’s database entries have gone out of sync:

Please login to your mysql/mariadb on the server: (The password will be in your /opt/fog/.fogsettings file under snmysqlpass or something very similary, usually under the variable named snmysqluser=fogmaster

mysql -u fogmaster -p fog

It will prompt for your password, which you collected earlier and hit enter

in the mysql side you can run:

delete from snapinJobs where sjID not in (select stJobID from snapinTasks) or sjID=0;
delete from snapinJobs where sjHostID not in (select hostID from hosts) or sjHostID=0;
delete from snapinTasks where stJobID not in (select sjID from snapinJobs) or stJobID=0;

That should fix the host-snapin-history-table issue.

[JJ Fullmer]

@pbriec I can confirm that these sql commands fix the issue with the snapin table ajax error.

I am trying to recreate your wol issues too.

I am unable to get wol with or without fog on my lenovo laptop with the lenovo branded usb-c ethernet adapter. Are you using a usb/usb-c adapter for ethernet or are you using a docking station?

[pbriec]

@JJ-Fullmer it’s a dell usb-c ethernet adapter.
I don’t understand what is wrong. I’ve ever managed to wake up the laptop but it don’t work at all time.
I thought it came from the New fog but i was wrong. I’ve tested with old one, doesn’t work.
As i’m using VM for fog, i’m able to switch between the two version using Snapshot.
Even with old fog, it doesn’t start. Very strange.
Another laptop with builtin ethernet port is working fine.
The specs of the usb-c ethernet adapter is quite clear, it supports wake on lan https://www.dell.com/fr-fr/shop/adaptateur-dell-usb-c-vers-ethernet-25-gbit-s/apd/470-bcfv/wi-fi-et-gestion-de-réseau

[george1421]

@JJ-Fullmer said in Dell Latitude 3340 with USB-C Ethernet Adapter - bad mac address registered:

I am unable to get wol with or without fog on my lenovo laptop with the lenovo branded usb-c ethernet adapter.

Is the computer powering off the network adapter in sleep mode or keeping it active?

I know WOL from anything other than g3 mode and windows is involved (i.e. s1-s4 has some kind of windows os interaction). So the windows OS needs to leave the power on the nic to be able to be woke up from these modes. Windows is a fickle beast.

[JJ Fullmer]

@george1421 I don’t often use the s0 or s3 sleep on my laptop, I just go full on full off. I don’t have a lot of need for WOL to work on laptops in our environment so I’m not too worried about it, but I’ll test wake from sleep mode.

@pbriec The specs say it does WOL from s0/s3 which are sleep modes, not full off modes.
I was able to recreate the issue where the wol task wouldn’t delete and was causing computers to boot to fog and showing that error screen and @Tom-Elliott believes he has that fixed (I’m about to test that)

I did confirm that add WOL to a normal task (like image deploy or inventory) does work as expected in the Newer Fog. So WOL functionality still works the same. I tested that on a standard desktop with built-in ethernet.

[JJ Fullmer]

@pbriec The specs of my lenovo adapter also state WOL is supported but I can’t get it to work from off or from sleep with or without FOG being the one to send the wake packet.
But I am able to get WOL to work on a standard desktop from Fog without issue now. So do another pull of working-1.6 to get fog’s WOL task updated.

I’d suggest running it without -y to make sure you get prompted to do any database schema updates via the web-ui. It’s not often that you have to push that button but there are for sure some when upgrading from 1.5.x to 1.6.x. Unless @Tom-Elliott has added something to the installer to make -y automate the schema updates.

cd /path/to/fog/installer
git checkout working-1.6
git pull
cd bin
sudo ./installfog.sh

[Tom Elliott]

@JJ-Fullmer -y does indeed automate the schema updates.