PXE-M0F: Exiting Broadcom PXE ROM.

Tom Elliott

To me, this looks like it doesn’t even recognize that a network cable is plugged in as it’s not even attempting to load to undionly files. this is not to say it’s directly a problem with the file, but I’d start here. It seems, to me, that the cable may have some issue, and the only reason you’re not seeing it when it gets to DHCP for PXE is because ProxyDHCP is responding with just enough for the nic to be able to pick up an IP address.

Can you boot the system fully and attempt running the windows tftp -c command line to get the undionly file?

Have you ensured your system has the undionly.0 file as you’re using proxy dhcp?

Sebastian Roth

Please try tcpdump on the FOG server:

[CODE]sudo tcpdump -i eth0 -w issue.pcap udp[/CODE]

Upload the dump file or take a look at it yourself using wireshark!

Wayne Workman

I booted the machine up fully and used the command prompt to grab the file.

[CODE]C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix  . :
    IP Address. . . . . . . . . . . . : 10.0.0.15
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 10.0.0.1

Ethernet adapter Local Area Connection 3:

    Connection-specific DNS Suffix  . :
    IP Address. . . . . . . . . . . . : 10.198.1.6
    Subnet Mask . . . . . . . . . . . : 255.255.255.252
    Default Gateway . . . . . . . . . : 10.198.1.5

C:\Documents and Settings\Administrator>tftp 10.0.0.3 get undionly.kpxe c:\undio
nly.kpxe
Transfer successful: 89460 bytes in 1 second, 89460 bytes/s

C:\Documents and Settings\Administrator>cd c:\

C:>dir
Volume in drive C has no label.
Volume Serial Number is FC56-C26E

Directory of C:\

04/03/2015 01:26 AM 0 AUTOEXEC.BAT
04/03/2015 01:26 AM 0 CONFIG.SYS
04/04/2015 02:23 AM <DIR> dell
04/03/2015 01:28 AM <DIR> Documents and Settings
04/03/2015 01:23 AM <DIR> Inetpub
04/04/2015 02:25 AM <DIR> Intel
04/03/2015 10:24 PM <DIR> Program Files
04/08/2015 04:37 PM 89,114 undionly.kpxe
04/03/2015 10:33 PM <DIR> WINDOWS
3 File(s) 89,114 bytes
6 Dir(s) 61,086,072,832 bytes free

C:>[/CODE]

undionly.0 is also present.

[CODE][root@localhost tftpboot]# ls
boot.txt ipxe.efi ipxe.pxe snponly.efi undionly.pxe
default.ipxe ipxe.kkpxe memdisk undionly.0 vesamenu.c32
foginstall.log ipxe.kpxe pxelinux.0.old undionly.kkpxe
i386-efi ipxe.krn snp.efi undionly.kpxe
[root@localhost tftpboot]# [/CODE]

I’m going to do a TCP dump as Uncle Frank suggested… It should shed some light on what’s happening…

Oh, and so you guys don’t freak, it only has 1 NIC. The second one listed there in IPCONFIG is a virtual adapter for my encrypted VPN service. It has zero bearing on net-booting, as it’s virtual and part of the OS.

Tom Elliott

Can you post the ltsp.conf file?

Tom Elliott

Nevermind you already did. Remove the dhcp-option=66,blahblah

Wayne Workman

Removed the dhcp option 66 and restarted dnsmasq… still no luck…

Wayne Workman

I started the below command, booted the target computer, waited till it failed and started booting windows, then killed the command. Says 5 packets were captured.

I’ve got the feeling that 5 packets doesn’t cut it…

[CODE][root@localhost ~]# sudo tcpdump -i enp2s0 -w issue.pcap udp
tcpdump: listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
stop
^C5 packets captured
5 packets received by filter
0 packets dropped by kernel
[root@localhost ~]# [/CODE]

Think it has anything to do with the adapter name? It’s very unusual… enp2s0

Packet capture file is attached.

EDIT: getting wireshark now…

[url=“/_imported_xf_attachments/1/1853_issue.pcap.zip?:”]issue.pcap.zip[/url]

Wayne Workman

According to Wireshark, my FOG server’s dnsmasq service only sends out one packet…

[IMG]http://s29.postimg.org/56b9s2qp3/Screenshot_from_2015_04_08_17_30_15.png[/IMG]

Wayne Workman

In the ltsp.conf file,

I am eyeballing this line:

[CODE]dhcp-option=vendor:PXEClient,6,2b[/CODE]

I don’t think it’s right… How can I bypass it so that it just gives undionly.kpxe to everything?

Sebastian Roth

DHCP offers are both missing ‘next-server’… but your FOG server 10.0.0.3 should provide this information! I think you kind of mis-configured dnsmasq a little.
[CODE]dhcp-boot=undionly.kpxe,10.0.0.3[/CODE]
and completely remove the dhcp-option 66 line…

Wayne Workman

Still no change, but there was a change in traffic. tcpdump said 13 or so packets were captured, but the filter only stored 5 of them. I’ve also reboot the FOG server too, and tried again.

New ltsp.conf file:
[CODE]port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=undionly.kpxe,10.0.0.3
dhcp-option=17,/images
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
pxe-prompt=“Press F8 for boot menu”, 3
pxe-service=X86PC, “Boot from network” undionly
pxe-service=X86PC, “Boot from local hard disk”, 0
dhcp-range=10.0.0.3,proxy[/CODE]

[url=“/_imported_xf_attachments/1/1854_issue.pcap.zip?:”]issue.pcap.zip[/url]

Tom Elliott

Because the boot file is undionly.kkpxe I believe you need to also have undionly.kkpxe.0 in the tftpboot folder.

Wayne Workman

[quote=“Tom Elliott, post: 45204, member: 7271”]Because the boot file is undionly.kkpxe I believe you need to also have undionly.kkpxe.0 in the tftpboot folder.[/quote]

undionly.kkpxe.0 ?? or cp undionly.kkpxe undionly.0 ?
I thought I was using undionly.[B][U]kpxe[/U][/B] ?

Jaymes Driver

[quote=“Wayne Workman, post: 45215, member: 28155”]undionly.kkpxe.0 ?? or cp undionly.kkpxe undionly.0 ?
I thought I was using undionly.[B][U]kpxe[/U][/B] ?[/quote]

Dnsmasq adds a .0 to the file name, I never really understood why, but adding a symlink for undionly.0 seems to resolve the issue for using DNSMASQ.

This is explained in the documentation on the dnsmasq set up page.

[quote]
Make a symlink for the undionly.kpxe file so dnsmasq can find it.
[code]cd /tftpboot
sudo ln -s undionly.kpxe undionly.0[/code]
source:[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]
[/quote]

of course you don’t have to use the Undionly.kpxe file, you can use Ipxe.kpxe or any of the variants, but you still need to include a symlink for the .0

I noticed this when we moved from pxelinux.0 (look there’s that .0 again!!!) to the Undionly.kpxe platform for iPXE in 0.33b. I could not get my boot file on my machine during pxe boot, in doing some research (I believe I found the information in wireshark) I found that the machines were looking for Undionly.0 instead of Undionly.kpxe.

I added a symlink for udionly.kpxe to undionly.0 and the problem resolved itself.

I started by using the pxelinux.0 to chainload the undionly.kpxe file until I understood the .0 being appended to the file name.
The Thread where I discuss this issue and my notes on resolution can be found here:[url]http://fogproject.org/forum/threads/dnsmasq-help-for-ipxe-stuff.10222/[/url]

Tom Elliott

Try changing this:
[code]port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=undionly.kpxe
dhcp-option=17,/images
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
pxe-prompt=“Press F8 for boot menu”, 3
pxe-service=X86PC, “Boot from network” undionly
pxe-service=X86PC, “Boot from local hard disk”, 0
dhcp-range=10.0.0.3,proxy
dhcp-option=66,“10.0.0.3”[/code]

TO THIS:
[code]port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=undionly.0,10.0.0.3,10.0.0.3
dhcp-option=17,/images
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
pxe-prompt=“Press F8 for boot menu”, 3
pxe-service=X86PC, “Boot from network”, undionly
pxe-service=X86PC, “Boot from local hard disk”, 0
dhcp-range=10.0.0.3,proxy[/code]

Wayne Workman

Made the change to the file, wow!

However, it still doesn’t boot… I’ve tried the Optiplex 745 and my laptop, which is a Dell D620.

Here’s what it does: [media=youtube]g1mQa-18ISQ[/media]

Wayne Workman

Going to try the other files in a bit…

Tom Elliott

What’s the output of the browser if you type in:

[url]http://10.0.0.3/fog/service/ipxe/boot.php[/url]

Wayne Workman

[quote=“Tom Elliott, post: 45278, member: 7271”]What’s the output of the browser if you type in:

[url]http://10.0.0.3/fog/service/ipxe/boot.php[/url][/quote]

[CODE]
Forbidden

You don’t have permission to access /fog/service/ipxe/boot.php on this server.
[/CODE]

I did this:
[CODE]chmod -R 755 /var/www/html/fog[/CODE]

And now that link gives output.

and I GET THE FOG MENU!!! WOOT WOOT!!

Wayne Workman

Currently uploading an image.

EDIT: Image uploaded fine.

PXE-M0F: Exiting Broadcom PXE ROM.

150

11.7k

17.2k

154.7k