netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Li, Zhen-Hua" <lizhenhua.dev@gmail.com>
Cc: "Michał Mirosław" <mirqus@gmail.com>,
	"Linux NetDev" <netdev@vger.kernel.org>
Subject: Re: A pure virtual nic
Date: Fri, 30 Dec 2011 07:44:21 -0800	[thread overview]
Message-ID: <4EFDDC55.80406@candelatech.com> (raw)
In-Reply-To: <CAEk7JKY6xtBm4DraqRMYEnmZZhsOZoZG-MSgrq+W4n2eCCz1Sg@mail.gmail.com>

On 12/29/2011 05:51 PM, Li, Zhen-Hua wrote:
> I plan to add some protocols to it. For example, HTTP Proxy packet
> analysis. So user-space programs can use an NIC in common way in a
> proxy needed environment.

When a program transmits a packet on your virtual NIC, where does the
packet go?  When it receives a packet, where did the packet come from?

Thanks,
Ben

>
>
>
> 2011/12/29 Michał Mirosław<mirqus@gmail.com>:
>> 2011/12/29 Zhen-Hua Li<lizhenhua.dev@gmail.com>:
>>> I have opened a project in SourceForge, it provides a pure virtual
>>> ethernet adapter.  If you are interested to join it, please mail me.
>>
>> Is veth or tap (both in vanilla kernel) not enough for you? What are
>> the differences?
>>
>> Best Regards,
>> Michał Mirosław
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2011-12-30 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29  3:12 A pure virtual nic Zhen-Hua Li
2011-12-29  9:19 ` Michał Mirosław
2011-12-30  1:51   ` Li, Zhen-Hua
2011-12-30 15:44     ` Ben Greear [this message]
2012-01-04  2:07       ` Li, Zhen-Hua
2012-01-04  2:48         ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EFDDC55.80406@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=lizhenhua.dev@gmail.com \
    --cc=mirqus@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).