The Mac OS is not seeing or communicating with the DHCP server in the router. Try setting it to manual, and putting in the router/gateway address (192.168.1.1) and a manual address for the Mac (192.168.1.109 for example - whatever is not taken by the other devices.). Mac OS X comes with a DHCP server built-in. The server is called bootpd and does both DHCP and BOOTP. These instructions just describe using it for DHCP. To start, you need to create a configuration file for the server. The file should be stored in /etc/bootpd.plist. If you want to determine the IP address of the DHCP server from which a Mac OS X system received its IP address, subnet mask, etc., you can obtain that information from a command-line interface (CLI), i.e., a Terminal window by using the command ipconfig getpacket interface where interface is the relevant network interface, which will usually be en0 or en1.
|Click here to return to the 'How to set up a Mac as a PXE boot server, with Debian Live' hint|
I didn't see this mentioned so try to avoid having two devices running DHCP on one network, otherwise you may find the client doesn't pick up the server & PXE boot fails (or worse things happen).
Personally I find this Mac PXE boot server somewhat involved, on Debian it's simpler to use dnsmasq. Skip to the using dnsmaq section…
You can run it from a USB stick if you want to keep the Mac setup on OS X.
Good work getting this running on OS X.
The nice part of the pure OSX approach is that you only have to set it up once. You can even effectively turn it off (well, the bootp part, at least) by changing your Network Preferences for the Ethernet port. I have a Network Location saved for just this purpose. Like I said in my other comment, if the network set for the Ethernet port doesn't match, the bootp server doesn't respond to incoming requests.
I suppose you could 'turn off' the nfs and tftp by adding firewall rules only allowing connections from the configured network address range.
Dhcp Server For Macos 10.13
It's a good idea to use something other than 192.168.x.x for your network. Those IPs are used by lots of routers, VMWare, Parallels, etc. Use 10.x.y.z as an alternative with a unique number for 'x'. Make sure your network and network masks match between bootp and Network Preferences. If they don't match, e.g. 10.1.1.x/16 vs 10.1.1.x/24, bootp will silently refuse to answer.
Set the bootp flag to detect other dhcp servers as well.
I use this for testing hardware and always change the paths for tftpboot and debian-live to be inside my home directory.
Last, if you're only testing with one machine, you don't need a hub/switch. Just connect a cable direct from your mac to the device.
It's a good idea to use something other than 192.168.x.x for your network. Those IPs are used by lots of routers, VMWare, Parallels, etc. Use 10.x.y.z as an alternative with a unique number for 'x'. Make sure your network and network masks match between bootp and Network Preferences. If they don't match, e.g. 10.1.1.x/16 vs 10.1.1.x/24, bootp will silently refuse to answer.Not necessarily true, at least for a home network. 192.168.x.0/24 is great for home networks precisely because it is not (sanely) used in enterprise, and thus there are no route collisions when connecting to VPNs.
Also, in the case that you do want to connect to other 10/8 networks and participate within that IP space, you shouldn't randomly select one because once again you may have routing problems.
But hey, 10/8 networks are really easy to type, especially if you use 10.0.0.x, because you can type those like 10.x and they'll still work with most CLI tools and browsers and stuff.
nfsroot=10.1.1.1:/srv/debian-live. (For the alternate setup, edit the fetch= parameter in live.cfg, to something like
Should be doable even with other than 192.168.x.x!
Dhcp Server For Macbook Pro
Dhcp Server For Macos High Sierra
very awesome, thanks!
I was just looking to do something like this since i've been jumping through a bunch of linux distros lately for testing stuff.