• So I have an issue with MS Surfaces. I only have a handful of usb/ethernet adapters. Ratio is about 100:1.

    This causes enormous problems for my cloning guys who are as sharp as a bowling ball.

    So I had a hair brained idea. What if I lie to fog? If I boot a custom ipxe image via USB and change the mac in the ipxe bios via “set net0/mac aa:bb:cc:dd:ee:ff”. This does work and my dhcp is non the wiser, but if I chain to the ipxe.efi on the fog server it reverts the mac back to the hardware default and performs another dhcp request.

    Soooo what if I go straight from my custom ipxe to fog by calling the script directly from the fog server and cut out the fog default ipxe.efi?

    What does the default ipxe.efi script call to start the fog boot process so I can call it directly from my custom ipxe.efi USB image?

  • Senior Developer

    @cmurray139 Just to add a bit more information. default.ipxe -> http://x.x.x.x/fog/service/ipxe/boot.php

    But I guess you will run into another issue as the FOS Linux system is another environment that you’d need to use the fake MAC address…

    Nevertheless it’s an interesting idea. Please give it a try and see how far you get. Let us know what you find out and if we can help you with anything.

  • Developer

    @cmurray139 the default fog ipxe boot files load /tftpboot/default.ipxe on your server. this is a ipxe boot script file that has the address of your fog server in it. this file can be customized if you like (i use a customized one to direct certain computers to my dev fog server instead of the production one, for example). make backups of your changes, this file is overwritten whenever you perform an upgrade of fog.