About 50 Pending macs for one host? Beware of Windows 10 random MAC feature for WLAN!

[x23piracy]

@george1421 i only have this one system throwing such mass of macs, no other system is doing this.
I could not talk to the user yet, but i cannot identify anything on that system whats causing that mac flood.

[Tom Elliott]

@x23piracy It’s not on THAT host. It’s from a common mac from other systems that are sending a MAC that IS on that host.

[x23piracy]

@Tom-Elliott but how could this be possible? let me check which macs fog has registered for it 4313

omg it seems that i already approved some of the wrong macs, the list continues…

This are the macs from a local ipconfig /all from the machine:
LAN: 40-B0-34-11-A6-D2
BT: F4-8C-50-49-D1-B1
WLAN: F2-6F-77-13-41-73
WLAN2: F4-8C-50-49-D1-AE

[Tom Elliott]

@x23piracy IT HAS NOTHING TO DO WITH it4313

It has to do when a mac address that IS registered to it4313, but being presented from the other systems.

[Tom Elliott]

@Tom-Elliott said in About 50 Pending macs for one host?:

F4-8C-50-49-D1-AE

I suspect F4-8C-50-49-D1-AE is the culprit because it appears to be a “Virtual” adapter.

[x23piracy]

@Tom-Elliott ok so you would recommend to filter this mac out?

[Tom Elliott]

@x23piracy I’m giving what I know. I don’t know if that IS the mac that’s causing the problems. You need to compare one of the systems that the associated macs as well as the it4313 device.

[Wayne Workman]

@x23piracy This query will identify which MAC it is:
SELECT hmMAC, count(*) FROM hostMAC GROUP BY hmMAC HAVING COUNT(*) > 1;

[x23piracy]

@Wayne-Workman

mysql> use fog
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> SELECT hmMAC, count() FROM hostMAC GROUP BY hmMAC HAVING COUNT() > 1;
Empty set (0.00 sec)

Hmm? May i did something wrong?

[Tom Elliott]

That SQL Statement will only find mac’s that are registered to multiple hosts. (Meaning there’s duplicate mac’s in the table.) This is not the case. As I’ve stated multiple times now, the problem is One of the MAC’s that is registered to the it4314 MAC already (not in pending) is in common with the other devices, causing those other devices to try to register their own pending macs AS it4313.

This is why we need two systems (at least). We need it4313 and its ipconfig /all, and the other system (based on MAC) and its ipconfig /all.

This is the only way we’re going to find what’s going on.

[x23piracy]

@Tom-Elliott from it4314 (it’s not it4313) my mistake and all adapted it i already posted it’s ifconfig, the other system, could this be potentionally every system in our network or only the ones having fog client running? afaik the client must be registered to send pending macs to fog right? If yes i have always approved pending macs so this system must be known by fog allready? If all this gets a yes why will wayne’s query not work?

I have PDQ Inventory running so i can get a list of all macs easily.

Regards X23

[Tom Elliott]

@x23piracy Wayne’s query is looking for a Single mac be reported multiple times. This isn’t the problem you’re facing. The problem is a single mac, that’s associated to It4314 (sorry) is registered ONLY to 4314, and being used to check in. FOG is seeing it AS it4314 and registering the pending mac’s under that host.

In essence, Wayne’s query is looking for something like:

hmMAC                                    hmHostID
--------------                           --------------
00:01:02:03:04:05                        1
00:01:02:03:04:05                        3

[x23piracy]

@Tom-Elliott @Wayne-Workman @george1421 here come my dublettes, i ran a report from pdq inventory for all macs from all systems and broke it down to dublettes and sorted em, here is the list (argh):

IT3394	00:11:6B:66:3C:89
IT3755	00:11:6B:66:3C:89
IT2658	00:50:56:C0:00:01
IT3256	00:50:56:C0:00:01
IT3905	00:50:56:C0:00:01
IT4004	00:50:56:C0:00:01
IT4027	00:50:56:C0:00:01
IT4092	00:50:56:C0:00:01
IT2658	00:50:56:C0:00:08
IT3256	00:50:56:C0:00:08
IT3905	00:50:56:C0:00:08
IT4004	00:50:56:C0:00:08
IT4027	00:50:56:C0:00:08
IT4092	00:50:56:C0:00:08
IT2980	02:80:37:EC:02:00
IT3210	02:80:37:EC:02:00
IT3271	02:80:37:EC:02:00
IT3286	02:80:37:EC:02:00
IT3394	02:80:37:EC:02:00
IT3445	02:80:37:EC:02:00
IT3456	02:80:37:EC:02:00
IT3460	02:80:37:EC:02:00
IT3503	02:80:37:EC:02:00
IT3514	02:80:37:EC:02:00
IT3540	02:80:37:EC:02:00
IT3776	02:80:37:EC:02:00
IT3832	02:80:37:EC:02:00
IT3299	0A:00:27:00:00:00
IT3909	0A:00:27:00:00:00
IT2740	18:A9:05:C4:D4:30
IT3254	18:A9:05:C4:D4:30
IT3811	34:64:A9:15:C9:E6
IT3944	34:64:A9:15:C9:E6
IT3524	AA:F3:20:52:41:53
it4244	AA:F3:20:52:41:53

What should or what can i do now? Damn there is no it4314 in the list.

Regards X23

[Wayne Workman]

@x23piracy The good news is I only see 7 unique MACs in that list. Add those to the mac filter in the web interface.

Also, how did you even get into this situation? Did you get some new devices recently? Image some new stuff? Create a new image in a VM? What caused this?

[george1421]

@x23piracy Tom and I were chatting last week, and it was his impression that your issue may be related to a mac address for a virtual adapter like a microsoft virtual adapter.

I think that your pdq inventory query only returns mac addresses for physical adapters (??). In that case these virtual ones would not be found. According to Tom the pending mac addresses come from the FOG client sending all discovered mac addresses to the FOG server.

(this following is my personal opinion/) I feel its a flaw in the FOG client, in that it should ONLY send physical mac addresses and leave the virtual ones alone. Because its possible for usb/bluetooth/vpn/etc adapters to have soft mac addresses that could be generated each time a device is plugged in. (/my personal option)

Its also possible if you don’t sysprep the golden image that these duplicate mac address are coming from and the same as the mac addressed defined in the golden image.

Now that you might have a list of 7 or 8 from your initial query. Go to a number of them and dump the output of ipconfig /all > %hostname%_mac.txt (warning I did not test that command so user beware). compare these 7 or so systems to see if any mac address is consistent. If that is the case then that mac address is your filter address for FOG (at least from what I understand chatting with Tom).

[x23piracy]

@Wayne-Workman hell idk i was ill some days and not at work, then i came back and saw the pending macs after i got two new devices for new starters i woud like to image (deploy). Then i mentioned these lot of pending macs from it4314. but the two new devices have nothing todo with it for sure.

Sorry i have no idea what happened. i hate such problems but i will figure that out.

@george1421 ipconfig /all > %hostname%_mac.txt will not destroy something, harmless

[Wayne Workman]

@george1421 It’s more a fog 0.x design flaw that has been carried forward. I understand that @Joe-Schmitt is using UUIDs in the designs for fog 2.0 so this won’t be a problem in the future.

[x23piracy]

@Wayne-Workman said in About 50 Pending macs for one host?:

@george1421 It’s more a fog 0.x design flaw that has been carried forward. I understand that @Joe-Schmitt is using UUIDs in the designs for fog 2.0 so this won’t be a problem in the future.

@Joe-Schmitt is there maybe a way to discard sending macs from virtual adapters with the current fog client, please? Maybe before 2.x?
@george1421 yes, it seems that your are right with pdq inventory, no macs for virtual adapters i didn’t mentioned that i was just wondering why there were some empty cells in the excel export, thats the answer.

Regards X23

[george1421]

@x23piracy said in About 50 Pending macs for one host?:

ipconfig /all > %hostname%_mac.txt will not destroy something, harmless

This is harmless. What it does it this
ipconfig /all lists all of the network adapters with all data. You may be able to get just the mac addresses of all network adapters if you have powershell or VB skills. I was just looking at quick and easy.
> %hostname%_mac.txt sends the output of ipconfig /all to a file titled %hostname% of the computer and _mac.txt. Then you can manually review this file for like mac addresses. Tom gave you a clue to what the troubled mac address could be. You will need to be Shurlock Holmes and find it.

[x23piracy]

@Tom-Elliott @george1421 @Wayne-Workman i could get the desired info from most of the system i found with duplicate macs:

it3210: https://pastebin.com/NLU4uZjM
it3256: https://pastebin.com/4ek2esnT
it3286: https://pastebin.com/KnQ8PWZK
it3905: https://pastebin.com/BKREi3Fu
it4004: https://pastebin.com/v3kxZrk2
it4027: https://pastebin.com/sC01izYN
it4092: https://pastebin.com/v7p1SbZv

What i found out so far:

00:50:56:C0:00:01 VMWare
00:50:56:C0:00:08 VMWare
02:80:37:EC:02:00 WWAN Device (H5321) Ericsson
00:11:6B:66:3C:89 still unclear (Systems are currently not connectable)

Edit:

I could Check it3394 for the 00:11:6B:66:3C:89 mac but the system does not have any device with that mac associated so what should i do know? Set the both vmware macs oon the filter list and also add the wwan device?

My pending mac list ist getting fuller and fuller actually there are more then 300 pending macs from it4314, i need to get rid of this.

Regards X23