From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Why I can't I build systemd without ipv6?
Date: Sat, 14 Oct 2017 12:05:12 +0100 [thread overview]
Message-ID: <1978080.VMMMtPNdTy@dell_xps> (raw)
In-Reply-To: <8dbaf54c-fa49-5713-66ee-1cba89439cfd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
On Friday, 13 October 2017 22:55:50 BST Daniel Frey wrote:
> On 10/13/2017 02:48 PM, Grant Edwards wrote:
> > On 2017-10-13, Vadim A. Misbakh-Soloviov <gentoo@mva.name> wrote:
> >> 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.
> >
> > It might not be the ISP that's broken. It might be the user's
> > firewall/router. A lot of the cheap consumer models are starting to
> > "support" IPv6 by default when it appears to them that the ISP
> > supports IPv6. But, the default IPv6 firewall/router settings aren't
> > always usable.
>
> I'm currently using the ISP provided router, as I don't have anything
> ATM that can handle 150 mbps symmetrical.
>
> Dan
I'm guessing the delay is due to DNS resolution missing of being misconfigured
somewhere in your/your ISPs network. Could you tweak your router's DNS
resolver addresses to point to OpenDNS resolvers, or some such if your ISP's
are not working properly?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-14 11:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 17:29 [gentoo-user] Why I can't I build systemd without ipv6? Daniel Frey
2017-10-13 17:41 ` Jack
2017-10-13 19:21 ` Daniel Frey
2017-10-13 17:41 ` daniel
2017-10-13 19:23 ` Daniel Frey
2017-10-13 17:50 ` [gentoo-user] " Grant Edwards
2017-10-13 19:38 ` Daniel Frey
2017-10-13 18:05 ` [gentoo-user] " Canek Peláez Valdés
2017-10-13 19:33 ` Daniel Frey
2017-10-13 21:58 ` Daniel Frey
2017-10-14 7:37 ` Tom H
2017-10-14 15:00 ` Daniel Frey
2017-10-13 18:34 ` Mike Gilbert
2017-10-13 19:02 ` Rich Freeman
2017-10-13 19:42 ` Daniel Frey
2017-10-13 19:32 ` Daniel Frey
2017-10-13 20:58 ` Vadim A. Misbakh-Soloviov
2017-10-13 21:48 ` [gentoo-user] " Grant Edwards
2017-10-13 21:55 ` Daniel Frey
2017-10-14 11:05 ` Mick [this message]
2017-10-14 15:03 ` Daniel Frey
2017-10-14 15:08 ` [gentoo-user] " Daniel Frey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1978080.VMMMtPNdTy@dell_xps \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox