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] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r4jjav00.fsf@xmission.com>
Date:	Wed, 13 Mar 2013 13:46:07 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"Martitz\, Thomas" <thomas.martitz@....fraunhofer.de>
Cc:	richard -rw- weinberger <richard.weinberger@...il.com>,
	"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
	"davem\@davemloft.net" <davem@...emloft.net>,
	"edumazet\@google.com" <edumazet@...gle.com>,
	"herbert\@gondor.apana.org.au" <herbert@...dor.apana.org.au>
Subject: Re: Trying to implement secondary loopback

"Martitz, Thomas" <thomas.martitz@....fraunhofer.de> writes:

>>
>> ________________________________________
>> Von: richard -rw- weinberger [richard.weinberger@...il.com]
>> Gesendet: Mittwoch, 13. März 2013 12:13
>> An: Martitz, Thomas
>> Cc: netdev@...r.kernel.org; davem@...emloft.net; edumazet@...gle.com; herbert@...dor.apana.org.au; ebiederm@...ssion.com
>> Betreff: Re: Trying to implement secondary loopback
>>
>> >
>> > So my questions are:
>> > * Is this on purpose/expected?
>> > * Is there anyway around it so that I can have a custom loopback interface
>> > without touching lo's functionality.
>> > * Generally, what's the proper way (if any) implement a secondary loopback
>> > interface?
>>
>> The only really question that matters is, why do you need a second
>> loopback interface?
>> Why can't you use any other pseudo interface?
>>
>
> What pseudo interface do you mean? I'm not aware of alternative pseudo interfaces.
>
> I'm developing a NIC and a driver for it. Thus I'm implementing the interface. I'm trying to implement an interface that does exactly do what loopback does except that I want to extend the loopback path to PCIe. This is for testing & validation purposes.
>
> I tried to implement an interface that's doesn't advertise as
> such. But the data transfer didn't go through my code. My test app is
> a simple client/server setup in a single process that sends/receive
> data to/on 127.0.0.1.

The easy solution is to setup two network namespaces and two nics.
And transmit data from one network namespace to another, through your
nics.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ