<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
It's possible to disable the netflt approach at compile time, by
undefining/removing some define (grep NETFLT). As an alternative, I
have written a patch to fully enable the TUN/TAP device, while not
(AFAIK) conflicting with the netflt approach (they can coexist). I've
submitted this patch to the ML before, but have not seen any replies.
Let me know if anyone wants to take a look at it.<br>
<br>
Best regards,<br>
<br>
Ivo Smits<br>
<br>
Op 28-5-2010 20:48, Frank Mehnert schreef:
<blockquote cite="mid:201005282048.42635.frank.mehnert@sun.com"
type="cite">
<pre wrap="">On Friday 28 May 2010, Alexey Eremenko wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I don't know if the performance would be highter with TUN/TAP (VBox
2.0 and older) mode...
i.e. Is the slowdown causes by vboxnetflt or some other reason ?
Unfortunately VBox 3.2.0 does not support TUN/TAP, and VBox 2.0 won't
install on such new hosts.
</pre>
</blockquote>
<pre wrap="">
You could test to set up a TAP device manually and connect VBox
in bridged mode to this TAP device.
Kind regards,
Frank
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
vbox-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a>
<a class="moz-txt-link-freetext" href="http://vbox.innotek.de/mailman/listinfo/vbox-dev">http://vbox.innotek.de/mailman/listinfo/vbox-dev</a>
</pre>
</blockquote>
</body>
</html>