netdev - Re: IPv6 Policy based routing not working.

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABQpAL4zbeqX4X1Kuzw-+FOppmYx7VzTzJn9OMLyYVBdS0Bz9w@mail.gmail.com>
Date:	Wed, 27 Aug 2014 11:32:55 +0530
From:	Tushar Shinde <mtk.tushar@...il.com>
To:	Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc:	netdev@...r.kernel.org
Subject: Re: IPv6 Policy based routing not working.

So do we need to always use ipv6 address to bind unlike ipv4?

Tushar

On Wed, Aug 27, 2014 at 11:25 AM, Hannes Frederic Sowa
<hannes@...essinduktion.org> wrote:
> On Mi, 2014-08-27 at 10:24 +0530, Tushar Shinde wrote:
>> Hi Hannes,
>>
>> Thank you for reply.
>>
>> I tested it will 2 kernels 2.6.32-431.11.2.el6.x86_64, and ubuntu
>> 14.04 kernel 3.13.
>>
>> ping6 -I <IPv6 src ip> <dest> is working. I also verified ssh with -b working.
>>
>> So my question is, is it necessary to give bind address to make source
>> based routing work? why don't it select ip address of given bind
>> interface? Because of this SO_BINDTODEVICE may not work as expected.
>
> Hmm, not sure, but last time I looked ping6 did not do SO_BINDTODEVICE
> at all and I doubt it changed. It merely sets outgoing interface index
> in cmsg PKTINFO data.
>
> Semantically those are not the same. Interface index on global
> destination addresses is only advisory, no strict routing lookup will be
> done.
>
> Bye,
> Hannes
>
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html