On 3 February 2017 at 14:31, Vijay Sampath
wrote:
> Hi Joe,
>
> Thanks for the reply; I will play with limiting the number of flows.
>
> So what would be the way to wildcard src/dst MACs? Is there another type of
> action I can specify.
If you know a priori where
On 3 February 2017 at 11:25, Vijay Sampath via discuss
wrote:
> We have a default rule in ovs which I assume makes it behave like a regular
> L2 switch
>
> cookie=0x0, duration=71407.425s, table=0, n_packets=33577078,
> n_bytes=38722336595, idle_age=0,
Jason,
There has been some initial work on SFC for OVN:
http://openvswitch.org/support/ovscon2016/7/1400-fourie.pdf
https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328377.html
-Louis
From: ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org]
On Fri, Feb 03, 2017 at 07:52:28PM +, Shuaijun Zhang wrote:
> >
> >
> >
> > Message: 2
> > Date: Fri, 3 Feb 2017 09:32:41 -0700
> > From: Scott Lowe
> > To: ovs-discuss@openvswitch.org
> > Subject: Re: [ovs-discuss] Does OVN support to set traffic routing
> >
>
>
>
> Message: 2
> Date: Fri, 3 Feb 2017 09:32:41 -0700
> From: Scott Lowe
> To: ovs-discuss@openvswitch.org
> Subject: Re: [ovs-discuss] Does OVN support to set traffic routing
> rules?
> Message-ID:
>
We have a default rule in ovs which I assume makes it behave like a regular
L2 switch
cookie=0x0, duration=71407.425s, table=0, n_packets=33577078,
n_bytes=38722336595, idle_age=0, hard_age=65534, priority=0 actions=NORMAL
Through a traffic generator we are sending unknown unicast
Maybe you just misunderstand the syntax. "output:tap0" is always going
to be an error because output ports have to be specified by number,
e.g. "output:3" if tap0 is port 3.
On Fri, Feb 03, 2017 at 10:26:03AM -0800, Joo Yong-Seok wrote:
> Thanks for your answer. Actually, when I ran "ovs-ofctl"
Thanks for your answer. Actually, when I ran "ovs-ofctl" command to insert
the rule, it complained like "output to unknown port". That seems to be
first issue. I was trying to redirect the packet to tap0 by specifying the
output port.
Secondly, no matter what the error is, I ran the traffic, and
On Fri, Feb 03, 2017 at 11:02:39AM +, Gabor Locsei wrote:
> Due to an unitialized script variable, we managed to create a bridge with an
> 'empty' name.
>
> ovs-vsctl threw an error but the object was created nonetheless. I reproduced
> the error on different versions.
> To avoid