Host Pending MAC create multi mac address!
lorde last edited by Wayne Workman
- FOG Version: 1.3.5-RC-10
- OS: Debian
- Service Version:
Host Pending MAC in Laptop create multi mac address, i delete all, or approve but the problem continue. I need help! :)
What I’m trying to say, is how to appropariately fix the problem in rc-10.
The problem, as you’re seeing it, is NOT a bug, rather a fix of an older bug. The only reason it “didn’t” do this in the past was because it was broken.
@lorde The problem is broken in that revision, not resolved.
@Tom-Elliott Tanks for the reply!
In the Running Version 1.3.1-RC-6 I don’t have this problem, i just revert 1.3.5-RC-10 to RC-6 and the problem is solved.
The problem came when I upgraded version 1.3.1-RC-6 to 1.3.1-RC-10.
Talvez tenha existido algum problema. Os adaptadores rede são um por portatil, mas só os Toshiba Kira. No entanto em portáteis com rede nativa o problema é o mesmo.
Para já vou manter a versão 1.3.1-RC-6, e vou fazer uma instalação limpa do Fog!
Obrigado a todos!
Fog é espectacular!
@lorde The problem isn’t the version, the problem is the shared adapter.
In the past, the register elements was broken. now it is working.
If you don’t want “pending” mac’s to associate based on the shared adapter, find that adapter on the original host and set it to “client ignored”
This post is deleted!
In several Toshiba Kira laptops we use network adapters, and never had problems.
Some laptops do not have adapter and also started to give the same problem.
In the previous version of FOG this did not happen, only after upgrading to the latest version 1.3.5-RC-10 I will revert to the previous version,
I can not stop this problem. Sorry for the English.
@george1421 Looking at this, it would seem the 60 mac is not the “issue” itself.
FOG uses ANY approved mac address associated with a host to link it to that host. If no host is found for any mac on the system and you’re running the new client, a new host will be created with “pending” status.
I’m going on a limb and going to guess @lorde has a “common” mac address associated within the image. This mac is being sent with the register module. Because, after the first time, one of afilomena’s now approved mac addresses are being sent with the request, another host’s mac’s are being associated with the afilomena host.
While I don’t have an answer for you but I have to ask, are you using a usb network adapter for imaging? AND/OR what is device 60.57:18:58:bb:88?
I can say that is an intel network adapter.