On Sat, Jan 26, 2013 at 11:19:18PM -0200, Ramon Marques wrote:
> Hello,
>
> I am trying to use ovs-ofctl to add a flow that matches the nw_dst field.
> I'm running ovs-ofctl add-flow
> tcp:127.0.0.1:6634nw_dst=10.0.0.2,actions=mod_vlan_vid:1,output:2
>
> and I get the following mesasge:
>
> 20
Hi Ramon,
Here while adding flow you are giving only L3 field *nw_dst*, that is why
flow is geeting normalized and it is ignoring the* nw_dst* while adding
flow.
In openvswich you have to specify *L2 field* also when you are specifying
an L3 field.
Please read* ovs-ofctl *man page for understandi
Problem solved. Thanks.
On Sat, Jan 26, 2013 at 11:36 PM, Justin Pettit wrote:
> Try adding "ip" to your flow specification.
>
> --Justin
>
>
> On Jan 26, 2013, at 5:19 PM, Ramon Marques wrote:
>
> Hello,
>
> I am trying to use ovs-ofctl to add a flow that matches the nw_dst field.
> I'm runni
Try adding "ip" to your flow specification.
--Justin
On Jan 26, 2013, at 5:19 PM, Ramon Marques wrote:
> Hello,
>
> I am trying to use ovs-ofctl to add a flow that matches the nw_dst field.
> I'm running ovs-ofctl add-flow tcp:127.0.0.1:6634
> nw_dst=10.0.0.2,actions=mod_vlan_vid:1,output:
Hello,
I am trying to use ovs-ofctl to add a flow that matches the nw_dst field.
I'm running ovs-ofctl add-flow
tcp:127.0.0.1:6634nw_dst=10.0.0.2,actions=mod_vlan_vid:1,output:2
and I get the following mesasge:
2013-01-27T01:09:28Z|1|ofp_util|INFO|normalization changed ofp_match,
details:
