[vbox-dev] TUN and TAP Documentation

JD jd1008 at gmail.com
Tue Mar 11 17:22:09 GMT 2008

Sorry, Frank - Pavel muller is correct.
I struggled for 2 weeks and you and another one of your
colleagues even sent me nasty email.
The document fails to mention that if the tun/tap bridged
"host interface" is used, you will need to add firewall rules
to your host to FORWARD tap packets to your outbound
network interface, and to MASQUERADE the tap IP
address as the outbount IP address. This topic is NOT
discussed well at all - and without it, bridged networking
documention is crippled as far as most people (who are
NOT networking engineers) are concerned.

> ----------------------------------------------------------------------
> Message: 1
> Date: Mon, 10 Mar 2008 13:31:43 +0100
> From: Frank Mehnert <frank at innotek.de>
> Subject: Re: [vbox-dev] TUN and TAP Documentation
> To: vbox-dev at virtualbox.org
> Message-ID: <200803101331.47227.frank at innotek.de>
> Content-Type: text/plain; charset="iso-8859-1"
> On Sunday 09 March 2008, Pavel Muller wrote:
>> However these sources don?t describe TUN/TAP interface in detail. This
>> ins?t possible, that don?t exit detailed manual:(
> These manual in summary are completely sufficient. What do you want to
> know except for information found in these descriptions? They describe
> how to open a tun/tap device and how to receive/send packets. Nothing
> else is needed. Note further that creating such complex manuals like
> the Intel manual you referred is often not possible since many Linux
> programmers work in their spare time only -- in contrast to the authors
> of the Intel manuals. On the other side, there is a huge amount of
> example code for these open-source interfaces.
> Kind regards,
> Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20080311/54b28824/attachment.html>

More information about the vbox-dev mailing list