Help - Invalid Mac Address
-
Ok thanks - going to give this a go. Will the commands mean that only a single mac address will be added as the host as opposed to both mac addresses?
Also not 100% how to make the change to SVN - where can I find this to edit? Is it easy enough to complete?
-
Are these commands just overwriting the files:
/var/www/fog/service/Pre_Stage1.php
/var/www/fog/service/Post_Stage2.php
/var/www/fog/service/Post_Stage3.php
/var/www/fog/service/Post_Wipe.phpIf so can I download new files from:
[URL=‘https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/Pre_Stage1.php’][U][COLOR=#0066cc]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/Pre_Stage1.php[/COLOR][/U][/URL]
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/Post_Stage2.php[/url]
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/Post_Stage3.php[/url]
[URL=‘https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/Post_Wipe.php’][U][COLOR=#0066cc]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/Post_Wipe.php[/COLOR][/U][/URL]and then upload to /var/www/fog/service/ myself?
-
Yes, they’re just overwriting. If you want to upload yourself you most certainly can.
-
Thank you - will give it a go. Appreciate your help and will let you know the results.
-
I have uploaded the new files and the issue has now been resolved fog is recognising the correct mac address. Thank you for taking the time to look at this.
-
Scott, Tom,
I am having a similar issue to this using fog Version 1.20.
I had an HP Elitebook that was not able to be registered at all. I updated the Kernal to the most recent bzImage files (posted on 2015-07-13) and then it booted into the screen to add the host but I got the “Invalid Mac Address Issue” (similar to this post): https://forums.fogproject.org/topic/4755/invalid-mac-address)
Wondering if I should try the update mentioned in this ticket or if this was something already built into 1.20. Any help would be greatly appreciated.
Thanks!
- Chris
-
@csavo The fix is to update to FOG Trunk - that will likely fix it.
However understand that FOG Trunk is the developmental version of FOG, it is what WILL be FOG 1.3.0 some day. Right now things are very stable IMHO and it’s getting close to release, but that’s not to say there is no possibility of bugs. FOG Trunk gets updated many times a day - and most bugs are minor, and if you find them, just report them here so we can fix them and get to FOG 1.3.0 faster.
If you would like to upgrade to trunk, you can pick one of the methods described here, I would recommend GIT:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk -
Just as a little background, I am using my FOG server with dnsmasq as I do not have access to the DHCP server on the network I am working with. Is there any known issues with updating to the FOG Truck and using it with dnsmasq?
-
@csavo Nope. It will function exactly how it is now. FOG doesn’t bother with your dnsmasq configuration - but I’d still make a copy of the configuration just because it’s good practice to have copies of configurations.
-
Working great now after moving to the Trunk. I was pleasantly surprised with how well the upgrade process worked. All I had to do after the update was reconfigure some of my settings for dnsmasq and then I was up and running.
Thank you for your help @Wayne-Workman !
