A pure virtual nic

I have opened a project in SourceForge, it provides a pure virtual
ethernet adapter.  If you are interested to join it, please mail me.

Project Name: pvnet

http://sourceforge.net/projects/pvnet/

2011/12/29 Zhen-Hua Li [off-list ref]:

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

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.



2011/12/29 Michał Mirosław [off-list ref]:

2011/12/29 Zhen-Hua Li [off-list ref]:

quoted

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

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[off-list ref]:

quoted

2011/12/29 Zhen-Hua Li[off-list ref]:

quoted

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 [off-list ref]
Candela Technologies Inc  http://www.candelatech.com

When a program sends out a packet, at start_xmit function. it will
unpack it and packet again with HTTP proxy headers, then give it to
the actual physical ethernet adapter.
When it receives a packet, unpack it and remove the http proxy
headers, and then put it back to the queue in kernel.


2011/12/30 Ben Greear [off-list ref]:

On 12/29/2011 05:51 PM, Li, Zhen-Hua wrote:

quoted

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

quoted

2011/12/29 Michał Mirosław[off-list ref]:

quoted

2011/12/29 Zhen-Hua Li[off-list ref]:

quoted

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 [off-list ref]
Candela Technologies Inc  http://www.candelatech.com

From: "Li, Zhen-Hua" <redacted>
Date: Wed, 4 Jan 2012 10:07:08 +0800

When a program sends out a packet, at start_xmit function. it will
unpack it and packet again with HTTP proxy headers, then give it to
the actual physical ethernet adapter.
When it receives a packet, unpack it and remove the http proxy
headers, and then put it back to the queue in kernel.

A netfilter module is a much more appropriate way to implement this.
You can even implement this kind of packet mangling in userspace using
nfqueue.