[ovs-discuss] writing a flow rule in OF15
Ben Pfaff
blp at nicira.com
Mon Oct 26 00:55:57 UTC 2015
Delete the double quotes, keep the single quotes.
On Mon, Oct 26, 2015 at 12:46:35AM +0000, Anees Mohsin Hadi Al-Najjar wrote:
> Hi Ben,
>
> I found code to quote the rule like this:
> ovs-ofctl -O OpenFlow15 add-flow br0 'priority=4000, idle_timeout=0, hard_timeout=0, eth_type=0x0806, arp_op=1, eth_src="00:00:00:00:01:02", actions= set_field:2->arp_op, set_field:"00:00:00:00:01:02"->arp_tha'
>
> I have applied it, but another type of error, which is:
> ovs-ofctl: "00:00:00:00:01:02": invalid Ethernet address
>
> I appreciate if you or somebody else help me to fix it.
>
> Thanks
> Anees
> From: Ben Warren [mailto:ben at skyportsystems.com]
> Sent: Monday, 26 October 2015 10:18 AM
> To: Anees Mohsin Hadi Al-Najjar <a.alnajjar1 at uq.edu.au>
> Cc: discuss at openvswitch.org
> Subject: Re: [ovs-discuss] writing a flow rule in OF15
>
> Hi Anees,
>
> Everything from “priority” on has to be a single argument according to your shell: quote it properly and don’t use any spaces.
>
> —Ben
>
> On Oct 25, 2015, at 5:12 PM, Anees Mohsin Hadi Al-Najjar <a.alnajjar1 at uq.edu.au<mailto:a.alnajjar1 at uq.edu.au>> wrote:
>
> Dear all,
>
> I am trying to write rules in latest OVS version, 2.4, and using OpenFlow 1.5. I am facing a problem with that.
>
> Could you possibly tell me how to fix it?
>
> Thanks.
>
> My rule is:
>
> ovs-ofctl -O OpenFlow15 add-flow br0 priority=4000, idle_time_out=0, hard_timeout=0, eth_type=0x0806, arp_op=1, eth_src="00:00:00:00:01:02", actions= set_field:2->arp_op, set_field:"00:00:00:00:01:02”->arp_tha
>
> ovs-ofctl: 'add-flow' command takes at most 2 arguments
>
>
>
> Anees
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org<mailto:discuss at openvswitch.org>
> http://openvswitch.org/mailman/listinfo/discuss
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss
More information about the discuss
mailing list