Please bear with me as I don't quite understand the significance of the
vlan_mode setting.
In any case, I changed the br0 port and vnet0 port to vlan_mode=native-tagged,
still guest 1 is not able to ping guest 2. The ping result is the same as
before.
From: Ben Pfaff
To: Ming-Ching Tie
On Wed, Feb 25, 2015 at 03:31:23PM +, Finucane, Stephen wrote:
> We've pushed a good chunk of our integration test framework, known as 'toit'
> (The Open vSwitch Integration Testsuite), to the OPNFV community. You can
> find the mail with links to the reviews here:
>
>
> http://lists.
On Tue, Mar 03, 2015 at 09:55:26PM -0800, Ben Pfaff wrote:
> On Wed, Mar 04, 2015 at 01:45:44AM +, Ming-Ching Tiew wrote:
> > I posted this to virtualbox forum which I got no response and now I am
> > posting it here as it might be a openvswitch problem instead of virtualbox
> > :-
> > I have
On Wed, Mar 04, 2015 at 01:45:44AM +, Ming-Ching Tiew wrote:
> I posted this to virtualbox forum which I got no response and now I am
> posting it here as it might be a openvswitch problem instead of virtualbox :-
> I have used virtualbox with open vswitch without any problem when I am not
>
I posted this to virtualbox forum which I got no response and now I am posting
it here as it might be a openvswitch problem instead of virtualbox :-
I have used virtualbox with open vswitch without any problem when I am not
using VLAN.
However, when I am using VLAN tagging in one of the open vsw
Thank, Ben. Can you please elaborate more about the optimization "should
only affect cases where a MAC
would otherwise quickly bounce back and forth between a number of learned
ports." I reproduced it with a simple setup which has only three switches
forming a triangle (VLAN set up to avoid loop),
On Tue, Mar 03, 2015 at 12:25:20PM -0600, Cheng Jin wrote:
> I have a problem with updating OVS' MAC learning table, when it is in the
> 'standalone' mode running like a legacy Ethernet bridge.
>
> The switch has an entry to a destination, including the destination MAC
> (say, 00:00:00:00:00:01),
Hi all,
I have a problem with updating OVS' MAC learning table, when it is in the
'standalone' mode running like a legacy Ethernet bridge.
The switch has an entry to a destination, including the destination MAC
(say, 00:00:00:00:00:01), an output port (say, 1), VLAN, and Age. However,
the switch
What's in the ovs-vswitchd log?
On Tue, Mar 03, 2015 at 12:51:18PM -0500, Krishna Pratap wrote:
> I tried bringing the port up. it doesn't change any thing. here is the
> output.
>
>
> root@ccpu5:~# ovs-vsctl set bridge br0
> other-config:hwaddr=\"00:15:17:a0:29:80\"
> root@ccpu5:~#
> root@ccpu
I tried bringing the port up. it doesn't change any thing. here is the
output.
root@ccpu5:~# ovs-vsctl set bridge br0
other-config:hwaddr=\"00:15:17:a0:29:80\"
root@ccpu5:~#
root@ccpu5:~#
root@ccpu5:~# ovs-ofctl dump-ports-desc br0
OFPST_PORT_DESC reply (xid=0x2):
LOCAL(br0): addr:16:0a:05:2e:2
On Tue, Mar 03, 2015 at 11:28:27AM -0500, Krishna Pratap wrote:
> Is it possible to set the MAC address of the local port of bridge( not the
> address of bridge itself) with a fixed address?
>
> I tried couple of ways to do it. one of them mentioned here in this old
> thread
> http://openvswitch.o
Hi,
Is it possible to set the MAC address of the local port of bridge( not the
address of bridge itself) with a fixed address?
I tried couple of ways to do it. one of them mentioned here in this old
thread
http://openvswitch.org/pipermail/discuss/2011-June/005297.html
i tested this one out but i
On Tue, Mar 03, 2015 at 08:08:39AM -0800, Ben Pfaff wrote:
> On Tue, Mar 03, 2015 at 04:58:47PM +0300, Alexey I. Froloff wrote:
> > When saving/restoring bridge state during force-reload-kmod
> > dynamic and 'scope link' addresses are not restored. This breaks
> > IPv6 in a very bad way, because r
On Tue, Mar 03, 2015 at 04:58:47PM +0300, Alexey I. Froloff wrote:
> When saving/restoring bridge state during force-reload-kmod
> dynamic and 'scope link' addresses are not restored. This breaks
> IPv6 in a very bad way, because restored interface no longer have
> link-local (fe80::) address. Be
> -Original Message-
> From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of Pravin
> Shelar
> Sent: Monday, March 2, 2015 9:57 PM
> To: Iezzi, Federico
> Cc: discuss@openvswitch.org
> Subject: Re: [ovs-discuss] Info next OVS with Intel DPDK
>
> On Mon, Mar 2, 2015 at 6:09 A
Hi,
When saving/restoring bridge state during force-reload-kmod
dynamic and 'scope link' addresses are not restored. This breaks
IPv6 in a very bad way, because restored interface no longer have
link-local (fe80::) address. Because of that it is unable to
receive RAs and assign global dynamic ad
oh yep, got it, thanks a lot Ben!
On Mon, Mar 2, 2015 at 11:29 PM, Ben Pfaff wrote:
> On Mon, Mar 02, 2015 at 04:08:52PM +0500, david jhon wrote:
> > I am really sorry for this absurd question but I am not getting exactly
> why
> > my code for setting a column in database fails on this assertion
Hi Pravin,
Thanks a lot for your answer.
Regards,
Federico
-Original Message-
From: Pravin Shelar [mailto:pshe...@nicira.com]
Sent: lunedì 2 marzo 2015 22:57
To: Iezzi, Federico
Cc: discuss@openvswitch.org
Subject: Re: [ovs-discuss] Info next OVS with Intel DPDK
On Mon, Mar 2, 2015 at
18 matches
Mail list logo
