1

I'm planning to do a Debian server which can deliver picore pxe to RPI 3/3+.

I have dnsmasq which gives a correct IP in the range and will provide the correct tftpboot option with the "Raspberry Pi Boot" given by a tag based on the mac address (3 first hex b8:27:eb:::*).

The first time, the rpi boots quite well (2nd try due to lack of traffic on my VLAN). But after the first boot, I have to change my DHCP range to get another IP address. Without that change the Pi won't boot.

I've read that it may come from the GUID which says it already got the pxe boot and won't provide it twice.

Piotr Kula
  • 17,336
  • 6
  • 66
  • 105
Thanatheos
  • 55
  • 4

1 Answers1

1

It is very difficult to guess what the problem could be with the information you provide. Often I find it is the emulation of old style networking through systemd. systemd cannot 100 % emulate that old networking, particular with a complex setup like net booting, so you will find strange side effects. So I prefer to use systemd direct to realize net booting from a Raspberry Pi as master. You can look at an accepted solution at Netbooting multiple “workers” RPi from a “master” RPi.

Ingo
  • 42,961
  • 20
  • 87
  • 207