From: Stefan Metzmacher <metze@samba.org>
To: Namjae Jeon <linkinjeon@kernel.org>, linux-cifs@vger.kernel.org
Cc: smfrench@gmail.com, senozhatsky@chromium.org, tom@talpey.com,
atteh.mailbox@gmail.com,
"ΕΛΕΝΗ ΤΖΑΒΕΛΛΑ" <helentzavellas@yahoo.gr>
Subject: Re: [PATCH 1/4] ksmbd: off ipv6only for both ipv4/ipv6 binding
Date: Mon, 27 May 2024 18:09:27 +0200 [thread overview]
Message-ID: <53a2b3b0-3600-4da1-b651-e10a065020e0@samba.org> (raw)
In-Reply-To: <20240502121425.5123-1-linkinjeon@kernel.org>
Hi Namjae,
> ΕΛΕΝΗ reported that ksmbd binds to the IPV6 wildcard (::) by default for
> ipv4 and ipv6 binding. So IPV4 connections are successful only when
> the Linux system parameter bindv6only is set to 0 [default value].
> If this parameter is set to 1, then the ipv6 wildcard only represents
> any IPV6 address. Samba creates different sockets for ipv4 and ipv6
> by default. This patch off sk_ipv6only to support IPV4/IPV6 connections
> without creating two sockets.
I think having two sockets '::' and '0.0.0.0' would be
better, would that also be possible?
It makes it more explicit and avoids ipv4 mapped addresses
like ::ffff:192.0.2.128, which are really ugly.
metze
prev parent reply other threads:[~2024-05-27 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 12:14 [PATCH 1/4] ksmbd: off ipv6only for both ipv4/ipv6 binding Namjae Jeon
2024-05-02 12:14 ` [PATCH 2/4] ksmbd: avoid to send duplicate lease break notifications Namjae Jeon
2024-05-02 12:14 ` [PATCH 3/4] ksmbd: use rwsem instead of rwlock for lease break Namjae Jeon
2024-05-02 12:14 ` [PATCH 4/4] ksmbd: do not grant v2 lease if parent lease key and epoch are not set Namjae Jeon
2024-05-27 16:09 ` Stefan Metzmacher [this message]
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=53a2b3b0-3600-4da1-b651-e10a065020e0@samba.org \
--to=metze@samba.org \
--cc=atteh.mailbox@gmail.com \
--cc=helentzavellas@yahoo.gr \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox