Received: from mx1.mailbun.net (unknown [170.39.20.100]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTP id F0B16781AE0 for <~alpine/devel@lists.alpinelinux.org>; Mon, 18 Jan 2021 19:30:48 +0000 (UTC) Received: from nanabozho.lan (unknown [107.242.112.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: ariadne@dereferenced.org) by mx1.mailbun.net (Postfix) with ESMTPSA id 365AD111231 for <~alpine/devel@lists.alpinelinux.org>; Mon, 18 Jan 2021 19:30:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dereferenced.org; s=mailbun; t=1610998241; bh=oYhOMHn0iAoTG3j8Hn5TcnWQ3mBpwOQISTeQ60t0ejw=; h=Date:From:To:Subject; b=epfVO3Zm38JT7MA05PzZUMdDegrrK+d3mjfR6mNlMKYLjojciqAByWDENJMFGJNW9 evnQWDXAxjeuPsJtjTmpvJlE0f58E70RTXteYhkw8sBMzFlnFHKA9iweeOgZp4BhjF 91aTHZnhRxG1JcWOX3SjtvBZw9QPASEzeqDyWSgs+zg5Hb+6R49JgxGw5xF7wkxNMb 6NgGDszBt5yAq5ljtxGxJeZvy7m3EPogaAvYav4+Ye2jdUG1P+HcVVgnUx97Jvi1dT Rmpr2nfCfAqyWVWasHCVATCYAmdmOS31UEGkRuZPy9Hvpoi2ZPEfJYFgdfKPpO/lNe Bo+rPenYhkmrQ== Date: Mon, 18 Jan 2021 12:30:40 -0700 (MST) From: Ariadne Conill To: ~alpine/devel@lists.alpinelinux.org Subject: Proposed system change: Use dhcpcd as default DHCP client Message-ID: MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Hello, I would like to propose we use dhcpcd as the DHCP client moving forward. ## Background At present, Alpine uses udhcpc as the default DHCP client. With the world transitioning toward IPv6, it makes sense to use a DHCP client which actively supports dual-stack configurations -- dhcpcd is the only client we package which does so cleanly. ## Benefits to Alpine By focusing on the dhcpcd client as our preferred DHCP client, we can support dual-stack IPv4+IPv6 autoconfiguration out of the box. This is helpful for CPE and home router deployments, where an ISP provides DHCP for IPv4 and DHCPv6-PD for prefix delegation, which is the most common form of dual-stack deployment at the consumer ISP level. At present, users must install dhcpcd or ISC dhclient in order to support this configuration -- while this is not a huge burden for the user, the future is trending towards network deployments which do not have IPv4 service at all[0], which makes integrating a high quality DHCPv6 client into our base system a strategic priority. By using dhcpcd by default, Alpine will support IPv4-only networks, IPv4 and IPv6 dual-stack networks and IPv6-only networks in all possible auto-configuration scenarios. Finally, dhcpcd has the best security maintenance record of the DHCP clients we presently support: BusyBox udhcpc, ISC dhclient and dhcpcd. ## Testing Users can verify their setup continues to work by simply installing dhcpcd and testing. ## Contingency Plan If dhcpcd has release-critical bugs, we can simply remove it from alpine-base, at which point BusyBox udhcpc will continue to be the default again. ## Timeline I would like to add dhcpcd to alpine-base in February. Ariadne [0]: https://ipv4flagday.net