Cerulean
[H]F Junkie
- Joined
- Jul 27, 2006
- Messages
- 9,476
This posting is basically the same thing as Troubleshooting TFTP/PXE with WDS VM and Ubiquiti Dream Machine but using a MoFi Network MOFI4500-4GXeLTE-V3 OpenWrt router instead of a Ubiquiti Dream Machine. Same exact WDS VM, so nothing has changed on the VM itself and we know that WDS and Windows Firewall are configured correctly and work with a Ubiquiti Dream Machine.
The difference in configuration detail between the two routers is that the OpenWrt web-interface does not present options like specifying a PXE boot server and PXE boot file. The router is using dnsmasq for DHCP and DNS.
For extra measure, I did validate and confirm that I can GET the boot file through TFTP from another machine on the same network and running Windows OS using this command:
So now focusing on OpenWrt, my procedure is to connect via SSH with PuTTY and test configurations. When I make changes, I finish it off with the following two commands:
To undo changes, I usually either reboot the router OR re-execute the same commands but with del_list instead of add_list.
So what have I tried?
1)
2)
3)
4)
5)
6)
7)
8)
I am still unable to get a blank VM to PXE boot. I have made sure that the VM NIC is set correctly so that it is trying to get DHCP from the same network. The point of failure is trying to PXE boot:
That's all I get. OpenWrt does not show any DHCP leases for this blank VM. I've tested another VM that already has Windows 10 installed and uses the same NIC settings to confirm that a DHCP lease is successfully acquired.
Maybe I am not setting or adding the correct settings, missing a step or two, or something. I'm hoping someone here has ideas.
EDIT 8 Jul 2021 2008 CST:
I took a look under Advanced > Status > System Log and found this:
EDIT 8 Jul 2021 2034 CST:
I did some reading of https://openwrt.org/docs/guide-user/base-system/dhcp and tried the following but continued to receive "00:0c:29:c4:84:9f ignored" in the System Log.
9)
10)
11)
The difference in configuration detail between the two routers is that the OpenWrt web-interface does not present options like specifying a PXE boot server and PXE boot file. The router is using dnsmasq for DHCP and DNS.
For extra measure, I did validate and confirm that I can GET the boot file through TFTP from another machine on the same network and running Windows OS using this command:
tftp -i 172.16.32.4 GET "\boot\x64\wdsmgfw.efi"
So now focusing on OpenWrt, my procedure is to connect via SSH with PuTTY and test configurations. When I make changes, I finish it off with the following two commands:
uci commit dhcp
/etc/init.d/dnsmasq restart
To undo changes, I usually either reboot the router OR re-execute the same commands but with del_list instead of add_list.
So what have I tried?
1)
Additionally, I added hostname CON-MDT for IP address 172.16.32.4 to the static DNS resolv list so that CON-MDT always resolves to 172.16.32.4.uci add_list dhcp.@dnsmasq[0].dhcp_boot='\boot\x64\wdsmgfw.efi,CON-MDT.contoso.lan,172.16.32.4'
2)
uci add_list dhcp.@dnsmasq[0].dhcp_boot='boot\x64\wdsmgfw.efi,CON-MDT.contoso.lan,172.16.32.4'
3)
uci add_list dhcp.@dnsmasq[0].dhcp_boot='\boot\x64\wdsmgfw.efi,CON-MDT,172.16.32.4'
4)
uci add_list dhcp.@dnsmasq[0].dhcp_boot='boot\x64\wdsmgfw.efi,CON-MDT,172.16.32.4'
5)
uci add_list dhcp.lan.dhcp_option="66,172.16.32.4"
uci add_list dhcp.lan.dhcp_option="67,boot\x64\wdsmgfw.efi"
6)
uci add_list dhcp.lan.dhcp_option="66,172.16.32.4"
uci add_list dhcp.lan.dhcp_option="67,\boot\x64\wdsmgfw.efi"
7)
uci add_list dhcp.@dnsmasq[0].dhcp_option="66,172.16.32.4"
uci add_list dhcp.@dnsmasq[0].dhcp_option="67,\boot\x64\wdsmgfw.efi"
8)
uci add_list dhcp.@dnsmasq[0].dhcp_option="66,172.16.32.4"
uci add_list dhcp.@dnsmasq[0].dhcp_option="67,boot\x64\wdsmgfw.efi"
I am still unable to get a blank VM to PXE boot. I have made sure that the VM NIC is set correctly so that it is trying to get DHCP from the same network. The point of failure is trying to PXE boot:

That's all I get. OpenWrt does not show any DHCP leases for this blank VM. I've tested another VM that already has Windows 10 installed and uses the same NIC settings to confirm that a DHCP lease is successfully acquired.
Maybe I am not setting or adding the correct settings, missing a step or two, or something. I'm hoping someone here has ideas.
EDIT 8 Jul 2021 2008 CST:
I took a look under Advanced > Status > System Log and found this:
My blank VM that is trying to PXE boot are the lines containing "00:0c:29:c4:84:9f ignored", whereas the VM that has a test install of Windows 10 is "172.16.32.34 00:0c:29:22:10:d7". I wonder why dnsmasq is doing this... looks like this person was also experiencing the same problem.Thu Jul 8 15:40:51 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:40:55 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:41:00 2021 cron.info crond[2441]: USER root pid 24880 cmd /vnstat/vnstat.cron
Thu Jul 8 15:41:00 2021 user.notice vnstat_scheduler: Updating Databases...
Thu Jul 8 15:41:03 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:41:14 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:41:18 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:41:26 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:41:35 2021 user.notice internet-ledstatus: Checking... IPv4/IPv6
Thu Jul 8 15:41:42 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:41:50 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:41:54 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:42:00 2021 cron.info crond[2441]: USER root pid 24954 cmd /etc/conn.sh
Thu Jul 8 15:42:00 2021 cron.info crond[2441]: USER root pid 24955 cmd /vnstat/vnstat.cron
Thu Jul 8 15:42:00 2021 user.notice vnstat_scheduler: Backing Up Databases...
Thu Jul 8 15:42:02 2021 user.notice SIM7 Watcher: DNS[1] -> 8.8.8.8
Thu Jul 8 15:42:02 2021 user.notice SIM7 Watcher: DNS[2] -> 172.26.38.1
Thu Jul 8 15:42:02 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 00:0c:29:c4:84:9f ignored
Thu Jul 8 15:42:09 2021 daemon.info dnsmasq-dhcp[24802]: DHCPDISCOVER(br-lan) 172.16.32.34 00:0c:29:22:10:d7
Thu Jul 8 15:42:09 2021 daemon.info dnsmasq-dhcp[24802]: DHCPOFFER(br-lan) 172.16.32.34 00:0c:29:22:10:d7
Thu Jul 8 15:42:09 2021 daemon.info dnsmasq-dhcp[24802]: DHCPREQUEST(br-lan) 172.16.32.34 00:0c:29:22:10:d7
Thu Jul 8 15:42:09 2021 daemon.info dnsmasq-dhcp[24802]: DHCPACK(br-lan) 172.16.32.34 00:0c:29:22:10:d7 CON-W10-2004
Thu Jul 8 15:42:12 2021 user.notice SIM7 Watcher: Host: 172.26.38.1 failed
Thu Jul 8 15:42:12 2021 user.notice SIM7 Watcher: DNS[3] -> 4.2.2.2
EDIT 8 Jul 2021 2034 CST:
I did some reading of https://openwrt.org/docs/guide-user/base-system/dhcp and tried the following but continued to receive "00:0c:29:c4:84:9f ignored" in the System Log.
9)
uci add_list dhcp.lan.dhcp_vendorclass="BIOS,PXEClient:Arch:00000"
uci add_list dhcp.lan.dhcp_vendorclass="UEFI32,PXEClient:Arch:00006"
uci add_list dhcp.lan.dhcp_vendorclass="UEFI,PXEClient:Arch:00007"
uci add_list dhcp.lan.dhcp_vendorclass="UEFI64,PXEClient:Arch:00009"
uci add_list dhcp.lan.dhcp_option="net:UEFI32,\boot\x64\wdsmgfw.efi,,172.16.32.4"
uci add_list dhcp.lan.dhcp_option="net:UEFI,\boot\x64\wdsmgfw.efi,,172.16.32.4"
uci add_list dhcp.lan.dhcp_option="net:UEFI64,\boot\x64\wdsmgfw.efi,,172.16.32.4"
uci add_list dhcp.lan.dhcp_boot="\smsboot\x64\wdsnbp.com,,172.16.32.4"
10)
uci add_list dhcp.lan.dhcp_option="66,172.16.32.4"
uci add_list dhcp.lan.dhcp_option="67,\boot\x64\wdsmgfw.efi"
11)
uci add_list dhcp.lan.dhcp_option="66,,172.16.32.4"
uci add_list dhcp.lan.dhcp_option="67,,\boot\x64\wdsmgfw.efi"
Last edited: