On Tue, Jun 21, 2011 at 7:37 PM, el05682 wrote:
> On Tue, 21 Jun 2011 18:56:06 -0700, Jesse Gross wrote:
>>
>> On Tue, Jun 21, 2011 at 6:46 PM, el05682 wrote:
>>>
>>> Thanx for the quick reply. Got that, but I still haven't solved my
>>> problem
>>> though.
>>>
>>> Is there any way to group the p
On Tue, 21 Jun 2011 18:56:06 -0700, Jesse Gross wrote:
On Tue, Jun 21, 2011 at 6:46 PM, el05682
wrote:
Thanx for the quick reply. Got that, but I still haven't solved my
problem
though.
Is there any way to group the packet flow without sacrificing the L2
lookup?
I think that the flows to mul
On Tue, Jun 21, 2011 at 6:46 PM, el05682 wrote:
> Thanx for the quick reply. Got that, but I still haven't solved my problem
> though.
>
> Is there any way to group the packet flow without sacrificing the L2 lookup?
> I think that the flows to multiple ports (i.e. ovs-ofctl add-flow br0
> in_port=
Thanx for the quick reply. Got that, but I still haven't solved my
problem though.
Is there any way to group the packet flow without sacrificing the L2
lookup?
I think that the flows to multiple ports (i.e. ovs-ofctl add-flow br0
in_port=3,actions=output:1,2)
skip this lookup.
I was thinking
On Mon, Jun 20, 2011 at 8:05 PM, el05682 wrote:
> While the connectivity works fine I was considering to add a flow based on
> the gre key. I actually
> want to group the ifaces with the same gre key so I was thinking something
> like
> #ovs-ofctl add-flow br0
> tun_id=1,idle_timeout=0,priority=1,
Hello,
I am using OpenVswitch version 1.1.1.
I have a bridge configuration consisted by multiple EoGRE tunnels.
Here is an example output of ovs-vsctl list Interface (ommiting what I
consider as irrelevant info)
admin_state : up
name: "gre5"
ofport : 5
opti
