From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: hf@hfnet.de
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard Android: Cached resolved host
Date: Sun, 4 Nov 2018 18:25:50 +0100 [thread overview]
Message-ID: <CAHmME9rm838UB=stvUPZkOVe1SuDQFNOvAyPHU7dhQscnCOahA@mail.gmail.com> (raw)
In-Reply-To: <523fbb0f-934e-4ba0-0948-718c9e1844a1@hfnet.de>
t's mostly this way to prevent DNS lookup failures during the network
connectivity changes, such as turning on and off and on a tunnel
really fast. I agree the current implementation's behavior is
suboptimal though. Probably instead we should invalidate based on the
TTL.
The code in question lives at
app/src/main/java/com/wireguard/config/InetEndpoint.java if you want
to take a stab at fixing it.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-11-04 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 16:40 WireGuard Android: Cached resolved host Heiko Friedel
2018-11-04 17:25 ` Jason A. Donenfeld [this message]
2018-11-05 16:56 ` Heiko Friedel
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='CAHmME9rm838UB=stvUPZkOVe1SuDQFNOvAyPHU7dhQscnCOahA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=hf@hfnet.de \
--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;
as well as URLs for NNTP newsgroup(s).