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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKoUArnvBBF=CdzKNBNLOu4ZDw8yG7RJ4J+ruXOQSrcV91U0+Q@mail.gmail.com>
Date:   Sat, 18 Mar 2017 12:28:18 +0200
From:   Rami Rosen <roszenrami@...il.com>
To:     David Ahern <dsa@...ulusnetworks.com>
Cc:     Daniele Orlandi <daniele@...andi.com>,
        Netdev <netdev@...r.kernel.org>
Subject: Re: SO_BINDTODEVICE in VRFs not working?

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

Regards,
Rami Rosen