[lkml]   [2002]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: virtual ethernet adapter?
On Fri, 2002-09-06 at 08:53, Peter Svensson wrote:
> On 6 Sep 2002, Shaya Potter wrote:
> > from what I can tell, tap just lets a programs use it, but one needs
> > user space app behind it (reading and writing to it). It doesn't
> > to have the ability to live on the network like vmware's vmnet stuff
> > does, perhaps I'm wrong and was confused by the web page.
> Well, you want at program to read and write ethernet frames, don't
you? To
> What happens is that the operating system sees the data written by the
> program as coming in over a ethernet interface, a virtual one.
> To connect that interface to a real one you use the bridging code. I
> it is standard in the newer kernels. Otherwise you can download it
> Create a bridge and attach both the
> ethernet card and the virtual one to it and use the resulting
> br0 (or whatever you choose to call it) instead of the normal ethernet
> interface. Your program that is attached to the "tap" will now appear
> another computer on the same ethernet segment to both your computer
> all others attachet the the segment.

that actually sounds more promising, but does it still involves the
program attached to the tap outputting ethernet frames. i.e. I can't
make a virtual ethernet driver with my own rules, have netfilter bind a
process to just use that adapter, and then just run the process as
normal. or am I still understating the capabilities?


shaya potter

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.141 / U:0.512 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site