From: Eli Zaretskii <eliz@gnu.org>
To: Robin Tarsiger <rtt@dasyatidae.com>
Cc: emacs-devel@gnu.org
Subject: Re: ai_flags in calls to getaddrinfo
Date: Sun, 03 Jan 2021 18:00:41 +0200 [thread overview]
Message-ID: <83czymc8nq.fsf@gnu.org> (raw)
In-Reply-To: <bdba96d2-18be-cc93-0f48-d2c0b9e4ef13@dasyatidae.com> (message from Robin Tarsiger on Thu, 31 Dec 2020 16:40:18 -0600)
> From: Robin Tarsiger <rtt@dasyatidae.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 31 Dec 2020 16:40:18 -0600
>
> does it happen with all names, including for instance "he.net" or
> "ipv6.google.com"
It does:
With AI_ALL and AI_V4MAPPED flags:
(network-lookup-address-info "he.net")
=> ([216 218 236 2 0] [8193 1136 0 1283 0 0 0 2 0])
(network-lookup-address-info "he.net" 'ipv6)
=> ([0 0 0 0 0 65535 55514 60418 0])
(network-lookup-address-info "ipv6.google.com")
=> nil: WSANO_DATA error
(network-lookup-address-info "ipv6.google.com" 'ipv6)
=> nil: WSAHOST_NOT_FOUND error
Without the AI_* flags:
(network-lookup-address-info "he.net")
=> ([216 218 236 2 0])
(network-lookup-address-info "he.net" 'ipv6)
=> nil: WSANO_DATA error
(network-lookup-address-info "ipv6.google.com")
=> nil: WSAHOST_NOT_FOUND error
(network-lookup-ddress-info "ipv6.google.com" 'ipv6)
=> nil: WSANO_DATA error
Note the difference in he.net resolution with and without the 'ipv6
argument, and also the behavior of ipv6.google.com with the ipv6
argument. Interesting, no?
> What about "localhost"?
As I said, localhost works the same with and without the AI_* flags.
I get:
(network-lookup-address-info "localhost")
=> ([0 0 0 0 0 0 0 1 0] [127 0 0 1 0])
(network-lookup-address-info "localhost" 'ipv6)
=> ([0 0 0 0 0 0 0 1 0])
> >> Does it have any IPv6 addresses configured, or no? What is
> >> its resolver configuration like?
> >
> > No idea. If you tell me how to find out, I will try. This system is
> > behind firewalls up the kazoo, so it could be something essential for
> > IPv6 DNS is blocked or intentionally disabled.
>
> If you run 'ipconfig/all' from a command line (which, if you are not
> familiar, you can launch by running 'cmd' from the 'Run' dialog,
> which in turn can be accessed through the Windows+R shortcut), it
> should display a bunch of information about active network connections,
> including local IP addresses and DNS resolver addresses.
Here's the result, with some fields redacted:
Windows IP Configuration
Host Name . . . . . . . . . . . . : (redacted)
Primary Dns Suffix . . . . . . . : (redacted)
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : (redacted)
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : (redacted)
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 6C-4B-90-A3-36-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e855:89df:21cc:1554%7(Preferred)
IPv4 Address. . . . . . . . . . . : 10.99.32.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : Sun 27 Dec 2020 09:20:18
Lease Expires . . . . . . . . . . : Wed 06 Jan 2021 21:20:19
Default Gateway . . . . . . . . . : 10.99.35.254
DHCP Server . . . . . . . . . . . : 10.1.20.36
DHCPv6 IAID . . . . . . . . . . . : 107760528
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-C0-F1-1B-6C-4B-90-A3-36-AB
Thanks.
next prev parent reply other threads:[~2021-01-03 16:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 15:06 ai_flags in calls to getaddrinfo Eli Zaretskii
2020-12-31 22:40 ` Robin Tarsiger
2021-01-01 7:43 ` Eli Zaretskii
2021-01-01 11:40 ` Robin Tarsiger
2021-01-01 12:04 ` Robin Tarsiger
2021-01-01 12:48 ` Eli Zaretskii
2021-01-02 0:19 ` Robin Tarsiger
2021-01-03 16:00 ` Eli Zaretskii [this message]
2021-01-11 10:47 ` ai_flags in calls to getaddrinfo, broader call for reproducibility check Robin Tarsiger
2021-01-11 12:42 ` Robert Pluim
2021-01-11 15:25 ` Eli Zaretskii
2021-01-11 15:47 ` Robert Pluim
2021-01-11 16:44 ` Eli Zaretskii
2021-01-11 17:07 ` Robin Tarsiger
2021-01-11 17:53 ` Robert Pluim
2021-01-11 18:30 ` Robin Tarsiger
2021-01-11 18:42 ` Robert Pluim
2021-01-11 19:28 ` Stefan Monnier
2021-01-11 20:12 ` Robert Pluim
2021-01-11 20:41 ` Eli Zaretskii
2021-01-11 20:55 ` Stefan Monnier
2021-01-11 21:02 ` Robert Pluim
2021-01-11 21:09 ` Lars Ingebrigtsen
2021-01-11 21:15 ` Robert Pluim
2021-01-11 22:42 ` Lars Ingebrigtsen
2021-01-12 9:40 ` Robert Pluim
2021-01-12 12:49 ` Lars Ingebrigtsen
2021-01-12 13:04 ` Robert Pluim
2021-01-12 14:08 ` Lars Ingebrigtsen
2021-01-12 14:29 ` Robert Pluim
2021-01-12 18:06 ` Lars Ingebrigtsen
2021-01-12 15:14 ` Stefan Monnier
2021-01-12 15:45 ` Eli Zaretskii
2021-01-12 3:29 ` Eli Zaretskii
2021-01-11 20:46 ` Eli Zaretskii
2021-01-11 20:56 ` Robert Pluim
2021-01-12 15:01 ` Eli Zaretskii
2021-01-12 15:36 ` Robert Pluim
2021-01-12 15:42 ` Eli Zaretskii
2021-01-12 16:00 ` Robert Pluim
2021-01-12 16:05 ` Eli Zaretskii
2021-01-12 17:56 ` Robert Pluim
2021-01-11 19:32 ` Basil L. Contovounesios
2021-01-11 20:19 ` Robert Pluim
2021-01-11 23:57 ` Andy Moreton
2021-01-12 9:44 ` Robert Pluim
2021-01-12 11:56 ` tomas
2021-01-01 10:59 ` ai_flags in calls to getaddrinfo Lars Ingebrigtsen
2021-01-01 12:50 ` Eli Zaretskii
2021-01-02 5:40 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czymc8nq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rtt@dasyatidae.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).