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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 9 Sep 2008 00:17:35 -0700
From:	David Stevens <>
To:	RĂ©mi Denis-Courmont <>
Cc:	Bernhard Schmidt <>,
	Brian Haley <>,,
Subject: Re: [IPv6] "sendmsg: invalid argument" to multicast group after some time wrote on 09/08/2008 11:52:05 PM:

> On Tue, 9 Sep 2008 02:38:53 +0200, Bernhard Schmidt 
> wrote:
> > ff00::/8 dev teredo  metric 256  mtu 1280 advmss 1220 hoplimit 
>                ^^^^^^
> Uho... that interface is not multicast-capable. Not sure how the kernel
> handles the conflicting routes.

        Multicast programs shouldn't rely on the routing
table at all, IMAO. Unicast routing has nothing at all
to do with multicast routing, where a single address
means copying and forwarding to multiple different
segments, and the address has nothing at all to do with
the routing topology.
        That's why the scope_id should be set (and to
the proper index for eth0), but I think either strace
is lying to us here or they're using SO_BINDTODEVICE
        But when it's breaking, I imagine it is ending
up on the wrong interface and thus the EINVAL... I
just don't see how some addresses still work while
others fail at the same time. :-)


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists