WireGuard Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Andre Tann <atann@alphasrv.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Delay in ipv6
Date: Thu, 5 Jun 2025 17:04:59 +0500	[thread overview]
Message-ID: <20250605170459.43439532@nvm> (raw)
In-Reply-To: <7e977585-5b93-4591-94f7-bf33c8923543@alphasrv.net>

On Wed, 4 Jun 2025 16:53:33 +0200
Andre Tann <atann@alphasrv.net> wrote:

> Hi all,
> 
> I hope this is not offtopic here. If so, pls let me know a better place 
> for this question.
> 
> I configured wireguard to route both IPv4 and IPv6. Both protocols work 
> fine. But test-ipv6.com only gives 9/10 points because the browser does 
> not use IPV6 even though it is available.
> 
> Then I investigated a bit and found this:
> 
> ping -4 dns.google => ping sequence starts immediately
> ping -6 dns.google => .5 secs delay => ping sequence starts
> ping -6 dns.google => ping sequence starts immediately
> 
> i.e.: On the first try, ping6 takes longer, but the second time there is 
> no delay anymore.

Hello,

Which DNS resolvers do you use?
Try 8.8.8.8 or 1.1.1.1 at first, and then their v6 equivalents.

> I suspected DNS trouble, but pinging 2001:4860:4860::8844 shows the 
> exact same behavior: delay the first time, no delay next time.

This might be caused by DNS again, trying to resolve PTR record for the IP.

Recheck if "ping -n" starts in this case without a delay.

-- 
With respect,
Roman

      reply	other threads:[~2025-06-05 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 14:53 Delay in ipv6 Andre Tann
2025-06-05 12:04 ` Roman Mamedov [this message]

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=20250605170459.43439532@nvm \
    --to=rm@romanrm.net \
    --cc=atann@alphasrv.net \
    --cc=wireguard@lists.zx2c4.com \
    /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