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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 30 Nov 2009 11:37:31 -0800 From: Ben Greear <greearb@...delatech.com> To: "Eric W. Biederman" <ebiederm@...ssion.com> CC: Patrick McHardy <kaber@...sh.net>, netdev@...r.kernel.org Subject: Re: RFC: net 00/05: routing based send-to-self implementation On 11/30/2009 11:32 AM, Eric W. Biederman wrote: > Patrick McHardy<kaber@...sh.net> writes: > >> These patches are yet another attempt at adding "send-to-self" functionality, >> allowing to send packets between two local interfaces over the wire. Unlike >> the approaches I've seen so far, this one is purely routing based. >> Especially the oif classification should also be useful for different setups. > > Why not put each physical interface in a different network namespace? > That should work with no changes today. This doesn't work if you want to have one application manage lots of interfaces and send traffic between these interfaces. Certainly there are use-cases that can use multiple name-spaces, but it's nice to have the option not to use them as well. Thanks, Ben -- Ben Greear <greearb@...delatech.com> Candela Technologies Inc http://www.candelatech.com -- 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
Powered by blists - more mailing lists