0

I'm in the process of updating some introductory networking tutorials for Raspbian Stretch and want to confirm a few details are consistent with the preferred practices under this release.

I am aware that for most applications, networking should be configured under the dhcpcd client. However, when running the isc-dhcp-server daemon, I expect that we want to disable the dhcp client for the corresponding interfaces and fall back to /etc/network/interfaces (which does not exist at all in the latest version).

@Milliways has given some excellent instructions for both methods in , so I'll keep this short and to the point.

1) When preparing Raspbian Stretch to run a DHCP server, is /etc/network/interfaces still the preferred method. If memory serves correctly, static configuration through dhcpcd.conf in Jessie did not complete in time to avoid errors in the launch of the isc-dhcp-server.

2) The server configuration only applies to one interface in this scenario (Pi as a simple router). I suppose that I could blacklist this interface in dhcpcd rather than disable the service directly, allowing dhcpcd to manage configuration of the remaining networks. But it also seems like this hybrid approach could cause conflicts. What configuration would you recommend for DHCP client (and wpa_supplicant config) on remaining interfaces?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.