Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.176.36])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 4C96A782CF6
	for <~alpine/devel@lists.alpinelinux.org>; Tue, 19 Jan 2021 20:19:24 +0000 (UTC)
Received: from mx1.tetrasec.net (mail.local [127.0.0.1])
	by mx1.tetrasec.net (Postfix) with ESMTP id 6B0581803C3
	for <~alpine/devel@lists.alpinelinux.org>; Tue, 19 Jan 2021 20:19:23 +0000 (UTC)
Received: from [172.17.48.222] (096-036-137-107.res.spectrum.com [96.36.137.107])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: nangel@tetrasec.net)
	by mx1.tetrasec.net (Postfix) with ESMTPSA id 490E31803C2
	for <~alpine/devel@lists.alpinelinux.org>; Tue, 19 Jan 2021 20:19:23 +0000 (UTC)
Message-ID: <bd67e3ced53af4ed734a425ec7596bdd5bd963dd.camel@alpinelinux.org>
Subject: Re: Proposed system change: Use dhcpcd as default DHCP client
From: Nathan Angelacos <nangel@alpinelinux.org>
To: ~alpine/devel@lists.alpinelinux.org
Date: Tue, 19 Jan 2021 15:19:22 -0500
In-Reply-To: <2R13E13K99O5U.2AJR60YXHCP5M@8pit.net>
References: <eb865f14-75ae-491b-179c-f6dc9f5df49@dereferenced.org>
	 <1ZT7J29AS5AJH.2CQHETQ00K814@8pit.net>
	 <66a3aa3-f55b-cdcd-d033-d6505985ccef@dereferenced.org>
	 <2R13E13K99O5U.2AJR60YXHCP5M@8pit.net>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

On Tue, 2021-01-19 at 19:54 +0100, S=C3=B6ren Tempel wrote:
>=20
>=20
> Ah, wasn't aware that this is an actual issue for people. I agree
> that we should find some way to make it easier for people to use
> DHCPv6 if they have to for some reason.


Spectrum (old Charter) customer here from Southeast US. Spectrum (old
Time Warner) in Northeast US apparently had IPv6 working years ago, but
that was not the case across the ISP.

They finally deployed it here in the Southeast, and its DHCPv6.  dhcpcd
let me grab a /56 via DHCPv6-PD (completely undocumented) until a
couple of weeks ago, when they apparently decided they only hand out
/60's. <sarcasm> I guess there's a shortage of prefixes? </sarcasm>

My personal experience is yes, there are "Tier 1" ISPs in the USA who
still haven't figured out how they want to hand out prefixes, or /128's
for that matter.


> I agree, we should definitely address this somehow. Maybe we could
> also just make it easier to install and configure dhcpcd and advise
> people to use it if they need DHCPv6 (instead of enabling it by
> default)? Though that would of cause not work by default then.

In my use case, I just install dhcpcd and move on.  It is bigger, but
it "just works". =20

No objections to pushing the other features upstream, but if we want
something for the next release, I wonder if giving the user the option
is viable.  We already do that with the choice of ssh and ntp; do we
let the user choose?  (if you have IPv4, this is smaller; if you need
DHCPv6-PD, this is your choice, etc.)


Like you two, not adamant on the subject, just commenting on what's
needed to make it work here.


Cheers