headless rpi

This is intended to setup a headless raspberry pi

<pi mount point>/rootfs/etc/dhcpcd.conf
 
Also put a file called ssh in <pi mount point>/boot

Be sure to configure the pi to use ssh on the first boot, as the ssh file gets cleared on each boot

headless rpi dhcpcd.conf

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# Most distributions have NTP support.
#option ntp_servers

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private



interface eth0
arping 192.168.1.1

# Corresponds to above arping command. If the arping gets a hit, we fall down to this profile
# The internet says we can have as many mappings like this as we want, so that we can
# deploy the pi to disparate networks
# This will also fall back to dhcp if we don't get any hits
profile 192.168.1.1
static ip_address=192.168.1.75/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1