From: Greg Troxel <gdt@lexort.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, guile-devel@gnu.org
Subject: Re: (web server) serving on both ipv6 and ipv4?
Date: Wed, 19 Jan 2022 13:27:00 -0500 [thread overview]
Message-ID: <rmiczknh98r.fsf@s1.lexort.com> (raw)
In-Reply-To: <3bbd5a2c267f9e58657b0087e26c92ed36d1b81b.camel@telenet.be> (Maxime Devos's message of "Wed, 19 Jan 2022 09:51:07 +0100")
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
Maxime Devos <maximedevos@telenet.be> writes:
> Maybe the IPV6_V6ONLY (see the ipv6(7) man page) is relevant here.
> Alternatively, you could run two servers in parallel: one bound to an
> IPv4 address and another bound to an IPv6 address.
My feeling is that IPV6_ONLY is best avoided, for portability, and
because mapped addresses (an IPv6 address with the v4 address embedded)
are awkward. So I think it's best to listen on v4 and v6 separately.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2022-01-19 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 7:57 (web server) serving on both ipv6 and ipv4? Dr. Arne Babenhauserheide
2022-01-19 8:51 ` Maxime Devos
2022-01-19 18:27 ` Greg Troxel [this message]
2022-01-20 7:24 ` Dr. Arne Babenhauserheide
2022-01-20 13:38 ` Greg Troxel
2022-01-19 13:07 ` Chris Vine
2022-01-19 13:44 ` Chris Vine
2022-01-19 13:53 ` Chris Vine
2022-01-19 21:12 ` Chris Vine
2022-01-19 21:42 ` Dr. Arne Babenhauserheide
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rmiczknh98r.fsf@s1.lexort.com \
--to=gdt@lexort.com \
--cc=arne_bab@web.de \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).