From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 208879] gai.conf(5) doesnt mention ip addrlabel configuration
Date: Sun, 04 Jan 2026 18:18:39 +0000 [thread overview]
Message-ID: <bug-208879-11311-mizP1stP6a@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208879-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208879
Dr. David Alan Gilbert (linux@treblig.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linux@treblig.org
--- Comment #1 from Dr. David Alan Gilbert (linux@treblig.org) ---
I'm using the labels in gai.conf succesfully (since I use ULA IPv6 addresses
internally and NAT, so mark fc00::/7 the same as ::/0 ).
Note gai.conf only influences only getaddrinfo name lookup (in glibc?),
I'm told 'ip addrlabel' is used by some kernel routing code.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
parent reply other threads:[~2026-01-04 18:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-208879-11311@https.bugzilla.kernel.org/>]
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=bug-208879-11311-mizP1stP6a@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/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