From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id CAA3B139083 for ; Fri, 13 Oct 2017 20:59:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C5BA02BC033; Fri, 13 Oct 2017 20:58:58 +0000 (UTC) Received: from forward100o.mail.yandex.net (forward100o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::600]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4F9EB2BC027 for ; Fri, 13 Oct 2017 20:58:58 +0000 (UTC) Received: from mxback7o.mail.yandex.net (mxback7o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::21]) by forward100o.mail.yandex.net (Yandex) with ESMTP id C79E62A23A85 for ; Fri, 13 Oct 2017 23:58:54 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback7o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id vWrqiwcUWZ-wsS0L5dN; Fri, 13 Oct 2017 23:58:54 +0300 Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id bB3G4JiHLr-ws8C19dQ; Fri, 13 Oct 2017 23:58:54 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) From: "Vadim A. Misbakh-Soloviov" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Why I can't I build systemd without ipv6? Date: Sat, 14 Oct 2017 03:58:52 +0700 Message-ID: <2374693.n4jBRkxzkn@note> In-Reply-To: <14d2d8af-e7b9-d5e6-06c1-a7f3ad01ac23@gmail.com> References: <14d2d8af-e7b9-d5e6-06c1-a7f3ad01ac23@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 538d494d-7e09-4104-871a-3c5c8dacc903 X-Archives-Hash: 16a3fb46dd6225e5cefff98877e040ad Well, actually, you was alread adviced about some working methods of solving your issue (both right and wrong ones, but it is anyway your decision to take ones to use), so I'll just clarify the simple thing: You can suffer on such problems in relation to IPv6 **ONLY** in the case when your ISP **DO** have IPv6 support (say, announce IPv6 preffix to you via SLAAC or DHCPv6), but having **BROKEN** IPv6 routing. (well, it can also be the case that they had no VLAN per customer and you're getting foreign SLAAC/DHCPv6 announces from some of your neighbours, but I'd prefer to not think such a worse things about ISP I don't know yet :D) So, ideally, you **SHOULD NOT** disable IPv6 on your side, but shame your ISP support line (for either broken IPv6 routing or not having VLAN per customer, depends on the real case) instead. P.S. don't consider "capsed" words as crying, please. Just consider it as "extra bold" mark.