[vbox-dev] [PATCH] UDPTunnel : new network interface backend to allow using this to link to GNS3 and QEMU instances over the network

Oelewapperke oelewapperke at gmail.com
Wed May 11 15:09:15 GMT 2011

By default everything is disabled. It has to be enabled specifically using
./configure --enable-udptunnel

If you don't pass this option, there is nothing to see : there won't be a
selection with "UDP tunnel" anywhere. VBoxManage won't show it either. There
is only 1 field and 1 method call in the API that remain visible if
udptunnel is not enabled.

It's the same as VDE is done now.


On Wed, May 11, 2011 at 5:03 PM, Perry Halbert <phalbert at cox.net> wrote:

>  OK, but you still are not considering the regular end user that does not
> compile their copy of VirtualBox.
> As you say I can select to not have host-only but where is the ability to
> not have UDP?  I think it must be considered and built in.
> On 05/11/2011 09:52 AM, Alexey Eromenko wrote:
> On Wed, May 11, 2011 at 5:41 PM, Perry Halbert <phalbert at cox.net> <phalbert at cox.net> wrote:
>  Question,
> Why not put this in an Extension Pack as an addon instead of changing the
> base code for everyone?
>  Developing Extension Pack is harder than this patch. (it means, that
> only very big features will make it into ext.pack), or features with
> incompatible licenses (like VNC).
>  Myself I like the idea of being able to either have this or not. Seems to me
> that is one reason that the Ext. Pack was implemented.  What about the
> security of the added UDP protocol such as three-way handshake that is
> missing in UDP used for the validity of the claimed source address.  I know
> that all of this seems small but to rush to change the base without
> considering the underlaying issues seems wrong.
>   If the decision is to include this in the base then there should also be a
> way to disable it built in as well.
>  Just don't use it if you don't like it. I don't use "Host-only
> network", because for my use cases, loopback + bridge cover this need.
> UDP tunnel is not secured, and this is by design, and documented in the docs.
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> http://vbox.innotek.de/mailman/listinfo/vbox-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20110511/55c3e2f5/attachment.html>

More information about the vbox-dev mailing list