lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <ab2cc07a-3b66-a47b-402d-1b29c0d9d384@gmail.com>
Date:   Fri, 20 Apr 2018 09:02:23 +0200
From:   Andre Naujoks <nautsch2@...il.com>
To:     netdev@...r.kernel.org
Subject: socketoption IPV6_MULTICAST_LOOP Bug?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ