Mailing List virtualized_ecs_users@2rosenthals.com Archived Message #59

From:	"Lewis G Rosenthal" <virtualized_ecs_users@2rosenthals.com>	Full Headers Undecoded message
Subject:	Re: [Virtualized eCS] TAP driver killing TCP/IP bandwidth
Date:	Thu, 10 Dec 2009 01:28:11 -0500
To:	Virtualized eCS Users Mailing List <virtualized_ecs_users@2rosenthals.com>

Hey... On 12/10/09 01:09 am, Andy Willis thus wrote : Cliff Scott wrote: ** Reply to message from "Lewis G Rosenthal" <virtualized_ecs_users@2rosenthals.com> on Wed, 09 Dec 2009 14:01:33 -0500 Has anyone else seen this type of performance hit caused by the TAP driver? I don't know if this qualifies as a performance hit, but with the TAP driver my entire external network goes dead. I've spent many hours trying all kinds of stuff and finally gave up. I also have a Broadcom B57 nic, but am using the native driver. You don't have it tied to a wireless as well do you? If I connect to wireless it knocks out my whole network, wired and wireless. Hmmm... I don't think so, as I've never been able to get wireless to work (aside from your hack of routing through the wired interface)... Isn't the binding done in VBox itself and not in PROTOCOL.INI? PROTOCOL.INI says: [TAP_nif] DriverName = TAP$ HandleArps = 1 And if no VM is running, then it shouldn't matter, should it? That configuration is stored in the xml for the VM. I ran all of my tests with nothing else (in terms of networking apps) running. -- Lewis ------------------------------------------------------------- Lewis G Rosenthal, CNA, CLP, CLE Rosenthal & Rosenthal, LLC www.2rosenthals.com Need a managed Wi-Fi hotspot? www.hautspot.com Secure, stable, operating system www.ecomstation.com -------------------------------------------------------------

Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster