[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#493972: ITP: etherpuppet -- create a virtual interface from a remote Ethernet interface

On Wed, Aug 06, 2008 at 01:21:09PM +0200, Guus Sliepen wrote:
> On Wed, Aug 06, 2008 at 11:44:51AM +0200, Vincent Bernat wrote:
> > * Package name    : etherpuppet
> >   Description     : create a virtual interface from a remote Ethernet interface
> > 
> > Etherpuppet is a small program that will create a virtual interface
> > (TUN/TAP) on one machine from the ethernet interface of another
> > machine through a TCP connection. Everything seen by the real
> > interface will be seen by the virtual one. Everything sent to the
> > virtual interface will be emitted by the real one.
> > 
> > It has been designed because one often has a small machine as his
> > Internet gateway, and sometimes want to run some big applications that
> > need raw access to this interface, for sniffing (Ethereal, etc.) or
> > for crafting packets that do not survive being reassembled, NATed,
> > etc.
> What is the added value of etherpuppet over existing tools, such as
> openvpn, tinc, gvpe, vde2? If there is none, or if the functionality
> that is missing from etherpuppet can be easily integrated with one of
> the existing tools, then you should tell upstream that it would be
> better to invest time and energy in one of the other solutions.

Well, etherpuppet is not really something to use as a simple vpn. You
use it to really clone (including low level stuff) the interface on the
remote side.


Reply to: