Hi all
I followed the instructions on how to configure a Raspberry Pi for network boot from the website. My dnsmasq.conf file on the server looks like this:
port=0
dhcp-range=192.168.1.255,proxy
log-dhcp
enable-tftp
tftp-root=/tftpboot
pxe-service=0,"Raspberry Pi Boot"
Using tcpdump, I can see the boot request come from the Pi over the network:
21:51:23.066981 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from b8:27:eb:ac:3f:81 (oui Unknown), length 320
21:51:23.229204 IP 192.168.1.43.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314
However, it always just show this in the daemon.log file over and over:
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 available DHCP subnet: 192.168.1.255/255.255.255.0
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 PXE(eth0) b8:27:eb:ac:3f:81 proxy
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 tags: eth0
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 broadcast response
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 sent size: 1 option: 53 message-type 2
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 sent size: 4 option: 54 server-identifier 192.168.1.43
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 sent size: 17 option: 97 client-machine-id 00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Jan 15 21:51:23 raspberrypi dnsmasq-dhcp[1940]: 653460281 sent size: 32 option: 43 vendor-encap 06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Any thoughts or ideas on why it always hangs just after option 43?
I also tried with an SD card in the pi with the latest bootcode.bin file on the card, yet the behaviour is exactly the same
Thanks in advance for any help/suggestions
Cheers
Mike
- DougieLawson
- Posts: 43580
- Joined: Sun Jun 16, 2013 11:19 pm
- Location: A small cave in deepest darkest Basingstoke, UK
Re: DHCP/PXE booting hangs just after "option: 43 vendor-enc
Try
Code: Select all
dhcp-range=192.168.2.10,192.168.2.40,300h
Languages using left-hand whitespace for syntax are ridiculous
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
Re: DHCP/PXE booting hangs just after "option: 43 vendor-enc
Fantastic, that was it! Worked first timeDougieLawson wrote:TryCode: Select all
dhcp-range=192.168.2.10,192.168.2.40,300h
This was the page I used to do the install and configuration - https://www.raspberrypi.org/documentati ... utorial.md
Does it need updating or was I doing something wrong?
Cheers
- DougieLawson
- Posts: 43580
- Joined: Sun Jun 16, 2013 11:19 pm
- Location: A small cave in deepest darkest Basingstoke, UK
Re: DHCP/PXE booting hangs just after "option: 43 vendor-enc
If you're going to proxy your existing DHCP server with DNSmasq you need to know the broadcast address for the primary (WiFi) interface on the TFTP/DHCP server machine. That DHCP server needs to be contactable as DNSmasq is going to request a DHCP address from the existing DHCP server.
My alternative sets DNSmasq up as a self contained DHCP server with it's own private address block. But the assigned addresses won't be routeable to the public internet or even to your home LAN.
My alternative sets DNSmasq up as a self contained DHCP server with it's own private address block. But the assigned addresses won't be routeable to the public internet or even to your home LAN.
Languages using left-hand whitespace for syntax are ridiculous
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
Re: DHCP/PXE booting hangs just after "option: 43 vendor-enc
Ah, I hadn't realised that's what it was doing. I was disabling DHCP on the router when trying to boot the Pi, so that makes sense now.DougieLawson wrote:If you're going to proxy your existing DHCP server with DNSmasq you need to know the broadcast address for the primary (WiFi) interface on the TFTP/DHCP server machine. That DHCP server needs to be contactable as DNSmasq is going to request a DHCP address from the existing DHCP server.
My alternative sets DNSmasq up as a self contained DHCP server with it's own private address block. But the assigned addresses won't be routeable to the public internet or even to your home LAN.
Cheers