From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Greg Troxel <gdt@lexort.com>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>,
Maxime Devos <maximedevos@telenet.be>,
guile-devel@gnu.org
Subject: Re: (web server) serving on both ipv6 and ipv4?
Date: Thu, 20 Jan 2022 08:24:10 +0100 [thread overview]
Message-ID: <877dauj23t.fsf@web.de> (raw)
In-Reply-To: <rmiczknh98r.fsf@s1.lexort.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Greg Troxel <gdt@lexort.com> writes:
> [[PGP Signed Part:Signature made by expired key 1FDA7AE8098ED60E Gregory D. Troxel (low security, at work) <gdt@work.lexort.com>]]
>
> 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.
I see portability, but for simplicity and having the same codebase, I
think that IPV6_V6ONLY=0 is the right choice.
It is possible to listen both on v6 and v4 for the same port, but you’ll
then have more complexity — I’m mainly thinking about tutorials here:
You’ll have to explain a lot more if you have to take care of v6 vs. v4
instead of having a library that does both.
An alternative could be a server using the fiberized web server to be
able to tie efficiently into the rest of the code via a plain fibers
channel.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2022-01-20 7:24 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
2022-01-20 7:24 ` Dr. Arne Babenhauserheide [this message]
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=877dauj23t.fsf@web.de \
--to=arne_bab@web.de \
--cc=gdt@lexort.com \
--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).