netdev - Re: SO_BINDTODEVICE in VRFs 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] [day] [month] [year] [list]

Message-ID: <bd1ecd9f-81f2-f8ef-e2cc-5c828657aad2@cumulusnetworks.com>
Date:   Sun, 19 Mar 2017 21:08:04 -0600
From:   David Ahern <dsa@...ulusnetworks.com>
To:     Rami Rosen <roszenrami@...il.com>
Cc:     Daniele Orlandi <daniele@...andi.com>,
        Netdev <netdev@...r.kernel.org>
Subject: Re: SO_BINDTODEVICE in VRFs not working?

On 3/18/17 4:28 AM, Rami Rosen wrote:
> Hi,
> 
>> Bind to the VRF device not an interface enslaved to it. I want to add
>> the option for enslaved interfaces but have not gotten around to it.
> 
> Maybe this should be added as a note/TBD to the VRF documentation
> (which does mention setsockopt with SO_BINDTODEVICE):
> http://lxr.free-electrons.com/source/Documentation/networking/vrf.txt#L97


I need a doc update to add the 'ip vrf exec'. I can add a to-do list as
well.