Drop CONFIG_IPV6 ?
fhfrediani at gmail.com
Sun Mar 13 21:32:01 PDT 2022
How come, at the stage we are, one can be thinking of disabling IPv6
just because the ISP didn't deploy it yet ?
How one can expect IPv6 to advance (and it has been going farily well),
if routers at end user have IPv6 disabled ? What when the ISP finishes
deployment and deliver IPv6 yo users ?
This shouldn't be considered under no other circumstances except for
personal customized images and quiet older routers.
On 14/03/2022 00:54, Philip Prindeville wrote:
> Yeah, I disable CONFIG_IPV6, since most American ISP's have started rolling out residential IPv6. My local pop & pop ILEC hasn't deployed it. There's not even an announced date for it on their roadmap.
> I suspect that if everyone had an IPv6 address, which would be both routable and non-dynamic, then people could more easily run servers on their networks... which might be anethema to the ISP's.
>> On Mar 13, 2022, at 5:31 PM, Etienne Champetier <champetier.etienne at gmail.com> wrote:
>> Hi All,
>> We currently have some circular dependencies caused by the usage of
>> PROVIDES and @IPV6
>> One radical way to fix, suggested by Jow, is to completely remove
>> CONFIG_IPV6 from OpenWrt.
>> This would also allow to simplify packaging of some core components.
>> Is anyone disabling CONFIG_IPV6 ?
>> Do people agree we can drop CONFIG_IPV6 ?
>> Should we do this before we branch 22.x ?
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
More information about the openwrt-devel