netdev - Re: [RFC] interface for outgoing packet

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]

Date:	Thu, 08 Sep 2011 08:09:05 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Viral Mehta <viral.vkm@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC] interface for outgoing packet

Le mercredi 07 septembre 2011 à 20:24 -0400, Viral Mehta a écrit :
> Hi All,
> 
> How reasonably I can assume that,
> 
> on whatever interface, I received the last packet
> for a particular Socket Connection, the same interface will be
> used to SEND the next packet for same socket connection?
> 

No

> I am collecting the logs on one of my test machines.
> And it shows, I can assume all the time that "interface" which received packet
> for some socket connection, the same will be used to send packet for
> that connection
> 
> But, I am not sure if I am missing some scenarios
> or setup (for e.g., bonding) where it can be wrong ?
> 
> It would be more help if some one can shed some light.

By default, a socket is not bound to one interface, so you cant assume
this.

Check SO_BINDTODEVICE socket option if you need it.



--
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