arisjr wrote: ↑
Wed Oct 25, 2017 1:27 pm
I have a Raspeberry Pi 3 fully functional, I have already installed two systems on it with success.
Now I'm trying to use PXE with it.
I've followed the tutorial , but the client part is not working.
I have checked the OTP value and its OK, but without the MicroSD card, the Raspberry Pi does nothing, no messages in the screen, nor even access the network for PXE/dhcp (I've checked with wireshark).
What am I doing wrong?
 https://www.raspberrypi.org/documentati ... utorial.md
Network Booting is challenging at the best of times with full blown systems and O/S. Of course the problem lies either in the Server or the Client (RPI). As far as I know the PXE code in the RPI-3 is solid. You need to look to your server. My advice is to grab an old laptop or PC, load the same O/S as your BootP server and try to configure the laptop as a Net boot client, thus proving the Server config is sound. The Server will also give you detailed BootP logs (if enabled) to help you work through things.
In my experience network boot problems usually are with the server config, areas of focus;
The initial DHCP request for a TCP/IP address is not being fulfilled. Without a IP address it stops dead. The ARP tables, and DHCP logs in your server will tell you if your RPI (based on its MAC address) is getting a valid IP address.
The next hurdle is passing the TFTP parameters via the PXE/DHCP server to the client. If successful you will see an attempt from the client to load the bet.boot file from the TFTP server. Enable detailed logging on the TFTP server. Quiet often basic firewall/o/S security gets in the way of a TFTP request.
If the client is getting a valid IP, and a loading a valid net boot file, you should see a boot occur, thereafter its easy to diagnose the problems as you will have a RPI boot console.
Net Boot/PXE is complex. Do some reading and be sure you understand the end to end process, then confirm each step of the process is working. This is not an area for shotgun diagnostics