mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Dmitry Samersoff <dms@samersoff.net>
To: musl@lists.openwall.com, Rich Felker <dalias@libc.org>,
	Alexander Scherbatiy <alexander.scherbatiy@bell-sw.com>
Subject: Re: [musl] getaddrinfo(3) with AI_V4MAPPED and AI_ALL flags
Date: Fri, 31 Jul 2020 19:21:47 +0300	[thread overview]
Message-ID: <8bd97d8a-ff78-27a0-8231-ffd0357218eb@samersoff.net> (raw)
In-Reply-To: <20200730160012.GT6949@brightrain.aerifal.cx>

Hello Rich,

I'm not sure that mapping of INADDR_ANY (0.0.0.0) and return of 
::ffff:0.0.0.0' has any sense.

Should it be filtered out on musl level?

-Dmitry

On 30.07.2020 19:00, Rich Felker wrote:
> On Thu, Jul 30, 2020 at 06:20:36PM +0300, Alexander Scherbatiy wrote:
>>
>>   glibc getaddrinfo(3) function uses /etc/gai.conf file to sort
>> addrinfo results.
>>   does musl getaddrinfo(3) implementations allows to configure the
>> results order?
> 
> Presently no, and there doesn't seem to have been a lot of demand for
> it, though there was at least one other request. IIRC I asked about
> the motivation since normally the default sorting should do the right
> thing, and I believe it was for the sake of overriding for some sites
> with broken IPv6 connectivity. If you have other use cases in mind it
> would be good to mention them to help document that this is a feature
> that makes sense to consider adding.
> 
> Rich
> 


  reply	other threads:[~2020-07-31 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 10:17 Alexander Scherbatiy
2020-02-27 14:45 ` Rich Felker
2020-07-30 15:20   ` Alexander Scherbatiy
2020-07-30 16:00     ` Rich Felker
2020-07-31 16:21       ` Dmitry Samersoff [this message]
2020-07-31 19:19         ` Rich Felker
2020-08-03  8:15           ` Dmitry Samersoff
2020-08-03 13:37             ` Rich Felker

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=8bd97d8a-ff78-27a0-8231-ffd0357218eb@samersoff.net \
    --to=dms@samersoff.net \
    --cc=alexander.scherbatiy@bell-sw.com \
    --cc=dalias@libc.org \
    --cc=musl@lists.openwall.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.vuxu.org/mirror/musl/

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).