Let’s bump an old topic

Do I have to tag my FOGserver in all VLANS in order to get this plugin working?
And configure all VLANS on my FOGserver?

/etc/network/interfaces

eth0.1 (default vlan)

eth0.100 (vlan 100)

eth0.1000 (vlan 1000)

I am at home now and can only resume testing in 3 days.

I downloaded ipxe.efi twice and calculated the checksum for both files.
I compared the md5-hash with the file on in my tftpfolder and it was trice the same…
No errors there…

I tested the ipxe.efi ROM on 2 different machines (intel NUC DC3217IYE and a Lenovo [SIZE=13px][FONT=Ubuntu][COLOR=#555555]ThinkPad Edge E540).[/COLOR][/FONT][/SIZE]Both time, the boot was interrupted as described above.

I will test snp.efi and snponly.efi in 3 days but I still got the feeling I’m doing something wrong.
Or is it a coincidence both machines refused to boot from the ipxe?

Would it help to try a legacy boot from ipxe.kpxe to test the ROM in non-uefi mode?

Is there a way to find out what NIC’s are supported by ipxe.efi?
Or a manual to build my own ROM for the NIC?

What’s the difference between:
[LIST]
[]intel.efi
[]intel.[B]kk[/B]pxe
[]intel.[B]k[/B]pxe
[]intel.pxe
[/LIST]
Can I failover between computers?
First try ipxe.efi
Then try intel.efi
Then try undionly.kpxe
…
I can test the hell out of FOG if you want me to

I can comment out the picturecode allright (if I would know in what file to comment )

But I don’t think I’m smart enough to build my own ROM for that NIC.
Especially since I have at least 5 different computertypes in my network and I would have to build one ROM to rule them all…

That being said, do we really need uefi (now)?
I can install 8.1 with legacy boot enabled, right?

Or am I missing the big picture again?

I did configure both bootfiles on the same tftpserver.
Maybe that’s what I did wrong?

This is what i see on my boot screen:
[CODE]tftp://MY.IP/default.ipxe… ok
http://MY.IP/fog/service/ipxe/boot.php… ok
http://MY.IP/fog/service/ipxe/bg.png… ok

Could not use picture: Exec format error (htt://ipxe.org/2e008081)
Could not boot: Exec format error (htt://ipxe.org/2e008081)
Could not boot: Exec format error (htt://ipxe.org/2e008081)

Failed to get IP, Booting back to bios
[/CODE]

I downloaded ipxe.efi from [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url]

[B]edit:[/B] even if I don’t use the policy and make ipxe.efi the default BootFile Name of that scope, I get the same error. Maybe my ipxe.efi file is corrupt?

[quote=“Junkhacker, post: 46793, member: 21583”]for windows server 2012 DHCP, it was as simple as the link Wayne Workman posted.
[url]http://www.syslinux.org/archives/2014-January/021404.html[/url] create vendor class that matches uefi systems ([I][COLOR=#000000]PXEClient:Arch:00007[/COLOR][/I]) and give those that match a different bootfile (in my case, ipxe.efi)[/quote]

Did you got this up and running?
I created the Vendor Class, created the policy, downloaded ipxe.efi and updated the DHCP server settings in 2012R2

Legacy Boot + undionly.kpxe ~ working
UEFI boot + ipxe.efi ~ [B]not working[/B]

[B]edit:[/B] typo ([I]ipxe.kpxe[/I] should have been[I] ipxe.efi[/I])