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
a
> > user space app behind it (reading and writing to it). It doesn't
seem
> > 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
think
> it is standard in the newer kernels. Otherwise you can download it
from
> http://bridge.sourceforge.net/. Create a bridge and attach both the
real
> ethernet card and the virtual one to it and use the resulting
interface
> 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
as
> another computer on the same ethernet segment to both your computer
and
> 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?
thanks,
shaya potter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Sep 07 2002 - 22:00:30 EST