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-next>] [day] [month] [year] [list]
Date:   Tue, 8 Aug 2017 13:29:58 +0200
From:   Ondrej Zajicek <santiago@...reenet.org>
To:     David Ahern <dsahern@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: l3mdev: Support for sockets bound to enslaved device

Hi

We noticed that TCP outgoing sockets that are bound to enslaved devices
by SO_BINDTODEVICE fail to connect, while they work when bound to vrf
device instead. We noticed similar behavior on ICMP (i.e. ping -I vrf0
worked, while ping -I eth0 does not if eth0 is enslaved to vrf0). On
the contrary, UDP outgoing sockets bound to enslaved devices worked
as expected. We tested that on Linux 4.9.30-2 from Debian.

I found your patchset 'Support for sockets bound to enslaved device'
( http://www.spinics.net/lists/netdev/msg448040.html ), which seems
to be related to the issue, but the description mentions services,
i.e. listening sockets. Does the patchset (or some other one) fixes
the issue also for outgoing sockets?

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago@...reenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ