From: Lars Ingebrigtsen <larsi@gnus.org>
To: toke@toke.dk (Toke Høiland-Jørgensen)
Cc: 14779@debbugs.gnu.org
Subject: bug#14779: 24.3; Failure to resolve IPv6 addresses in make-network-process
Date: Wed, 23 Oct 2019 13:39:53 +0200 [thread overview]
Message-ID: <875zkfhera.fsf@gnus.org> (raw)
In-Reply-To: <87d2qzzs1t.fsf@toke.dk> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\= \=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of "Wed, 03 Jul 2013 15:33:50 +0200")
toke@toke.dk (Toke Høiland-Jørgensen) writes:
> I'm using ERC to connect to IRC, and was wondering why the connection
> used IPv4 rather than IPv6 when the server has both addresses
> configured. Messing with the DNS resolver so the address only resolves
> to IPv6 made Emacs unable to connect at all.
>
> Investigating this further, it seems that by default
> make-network-process does not resolve IPv6 addresses at all unless
> specifically asked to do so. More precisely, patch open-network-stream
> to pass :family 0 (line 143 of network-stream.el) makes resolution work
> as expected (i.e. first IPv6, then v4 if no v6 address exists), but the
> default of leaving out the :family parameter (or setting it to nil)
> makes resolution IPv4-only, resulting in a 'Name or service not known'
> error when trying to connect.
The code has changed substantially in the six years since this was
reported.
Are you still seeing these problems?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-23 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 13:33 bug#14779: 24.3; Failure to resolve IPv6 addresses in make-network-process Toke Høiland-Jørgensen
2013-07-03 16:41 ` Andreas Schwab
2013-07-03 16:51 ` Toke Høiland-Jørgensen
2013-07-03 20:04 ` Andreas Schwab
2013-07-03 20:22 ` Toke Høiland-Jørgensen
2019-10-23 11:39 ` Lars Ingebrigtsen [this message]
2019-10-23 12:24 ` Unknown
2019-10-24 11:45 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zkfhera.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=14779@debbugs.gnu.org \
--cc=toke@toke.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.