Hi,
I experienced a bug with veth pairs and OVS v1.0.1, spent a few hours making
a replicatable bug report, but then tried the master branch and the bug went
away.
Out of curiosity, when is the next stable release expected, and is there any
pattern to the OVS release cycle?
Thanks,
Brandon
_
On Thu, Aug 05, 2010 at 02:31:28PM -0700, Dan Wendlandt wrote:
> The easiest thing to do here is to connect both eth0 and eth1 to the same
> physical switch (as I mentioned previously, this physical switch must
> support VLAN forwarding).
I don't think that special support for VLANs in the physica
On Thu, Aug 5, 2010 at 1:59 PM, Nikos wrote:
> Ok and how will i connect the two interfaces? Using eth0 and eth1 as ports
> in a separate bridge is not allowed because they are already in use.. Any
> ideas? Thanks again!
>
My understanding is that you are using two different NICs on the same box
On Thu, Aug 5, 2010 at 12:24 PM, Nikos Bregiannis wrote:
> I have a machine with 6 ethernet card inside.
> I want to test the configuration you have in the site
> http://openvswitch.org/?page_id=146 with the only difference that i dont
> need the Management Network Cloud.
>
> My configuration
>
>
I have a machine with 6 ethernet card inside.
I want to test the configuration you have in the site
http://openvswitch.org/?page_id=146 with the only difference that i dont
need the Management Network Cloud.
My configuration
ETH0: br0 with ports --tap0 (tag=1)
--tap1 (tag=2)
On Tue, Aug 3, 2010 at 7:31 PM, 陈文龙 wrote:
> To set up VLANs for VMs, I may take use of many physicals, connect them
> together.
> Configure them as VLAN trunks will result in a big broadcast domain, which
> may
> reduce the performance of network.
> Is there any way to avoid it?
>
Vlans are com
