From: Andre Naujoks <nautsch2@gmail.com>
To: netdev@vger.kernel.org
Subject: socketoption IPV6_MULTICAST_LOOP Bug?
Date: Fri, 20 Apr 2018 09:02:23 +0200 [thread overview]
Message-ID: <ab2cc07a-3b66-a47b-402d-1b29c0d9d384@gmail.com> (raw)
Hi all.
It seems the documentation (i.e. 'man ipv6') and the actual
behavior of the kernel diverge somehow in regard to what
IPV6_MULTICAST_LOOP does.
The manpage says:
---
IPV6_MULTICAST_LOOP
Control whether the socket sees multicast packets that it has send itself. Argument is a pointer to boolean.
---
However, the actual behavior on my system is, that the whole system
no longer receives multicast packets sent from that socket. As opposed
to only the socket itself no longer seeing its own packets.
Is this a bug, or is the documentation wrong? I sincerely hope this is a bug,
since everything else does not make sense at all in a multiuser system.
Regards
Andre
reply other threads:[~2018-04-20 7:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ab2cc07a-3b66-a47b-402d-1b29c0d9d384@gmail.com \
--to=nautsch2@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).