Hmm, I’m not clear.
Do you mean, I should not add tag filed on physical interface?
Then how can I set tagged interface?
In my setting,
I made a bridge xenbr2.100 and its interface is eth2.100 (used by vlan 8021q)
For this, I did not set tag field, and I set 100 for trunks field (both
On Wed, May 26, 2010 at 7:28 PM, 신용진 wrote:
>
> > If you are using OVS to do the vlans, you should set the tag field on the
> internal port and leave the other ports alone to trunk.
>
> Yes, for eth1 and eth2, I set tag field only. And empty trunks field in
> Port table.
>
Generally you want to s
> Are you still using vconfig to configure the vlans or are you only using OVS
> to handle all of the vlan functionality?
I am testing both of them. My server has 5 ethernet port, and I use vconfig to
configure vlans in some port, and also using OVS to handle vlan functions in
other port and
On Wed, May 26, 2010 at 6:58 PM, 신용진 wrote:
> Hmm,
>
>
> At first, I do not set any values both of "tag", and "trunks"
> But servers and VMs cannot communicate each other.
> So, I searched about "trunk" on openvswitch, and I set the value on them.
>
>
> Let's suppose that I put an IP on VLAN as 1
Hmm,
At first, I do not set any values both of "tag", and "trunks"
But servers and VMs cannot communicate each other.
So, I searched about "trunk" on openvswitch, and I set the value on them.
Let's suppose that I put an IP on VLAN as 10.10.10.101 at SV1(Server1).
When I ping to 10.10.10.101 fr
I sent out a patch that should prevent us from making that mistake again.
On Wed, May 26, 2010 at 11:08 AM, Ben Pfaff wrote:
> Thanks for the report.
>
> We do need to figure out a way to keep that file up-to-date. Maybe
> boot.sh should update it.
>
> On Wed, May 26, 2010 at 08:01:12PM +0200,
Thanks for the report.
We do need to figure out a way to keep that file up-to-date. Maybe
boot.sh should update it.
On Wed, May 26, 2010 at 08:01:12PM +0200, Joan Cirer wrote:
> I applied to patch and it compiled with no error, but after compling I saw
> thaht debian/changelog is at version 0.90
Hi,
Thanks,
I applied to patch and it compiled with no error, but after compling I saw
thaht debian/changelog is at version 0.90.6 and not at version 1.0.0-1
Regards
On Wed, May 26, 2010 at 18:48, Ben Pfaff wrote:
> On Wed, May 26, 2010 at 12:07:50PM +0200, Joan Cirer wrote:
> > I'm trying to
On Wed, May 26, 2010 at 06:59:25AM +, DarkBls wrote:
> With a bit more thinking, since we have a centralized configuration
> database, there is no benefit to have the feature of switch stacking
> over a cascading. But we need the spanning tree to be able to make a
> redudant topology.
It may b
On Thu, May 27, 2010 at 01:22:15AM +0900, �ſ��� wrote:
> After I posted original thread, I could find the "Port" table has
> information about "trunk"
>
> And the manual(http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf) said,
>
> A bridge port must be configured for VLANs in one of two mutually
On Wed, May 26, 2010 at 12:07:50PM +0200, Joan Cirer wrote:
> I'm trying to build the debian package on Ubuntu 10.04, but during the
> tests, test 262 fails.
Oops. That's a bug in the testsuite. You can ignore it. I will send
out a patch to fix it shortly.
To build the Debian packages without
After I posted original thread, I could find the "Port" table has
information about "trunk"
And the manual(http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf) said,
A bridge port must be configured for VLANs in one of two mutually exclusive
ways:
1) A‘‘trunk port’’ has an empty value for tag and a
On Wed, May 26, 2010 at 11:38:01AM +0900, ? wrote:
> How can I set trunk through open vswitch?
In Open vSwitch, ports are trunks by default. Only if you configure a
port as having a specific vlan does it disable trunk mode.
___
discuss mailing
With a bit more thinking, since we have a centralized configuration database,
there is no benefit to have the feature of switch stacking over a cascading.
But we need the spanning tree to be able to make a redudant topology.
De : Jesse Gross
À : DarkBls
Cc :
14 matches
Mail list logo
