[ovs-discuss] problem in adding flows

Prashant Chougule chougulepavan at gmail.com
Sat Apr 27 06:31:04 UTC 2013


ok..,

i ran ovs on my local machine ubuntu 12.04, with bridge br0 and eth0 port
under that,
 after that i create one file name "file1" with some 10 flows,
actually i want test the ovs with acl(access control list) rules, so i take
some of their rules put it in ovs format as shown above,

after that i ran command sudo ./ovs-ofctl add-flows br0 file1
             o/p: unknown keyword priority
 check with different format also like instead of priority i put in_port,
dl_type still same problem.






On Sat, Apr 27, 2013 at 11:41 AM, Justin Pettit <jpettit at nicira.com> wrote:

> I can't reproduce any problem loading flows in the 1.9 release.  The flows
> you defined still won't match the nw_src and nw_dst, since you didn't
> specify matching IP packets.  Perhaps if you showed what you actually ran,
> the contents of the file, and the output of the command, we might be able
> to help you more.
>
> --Justin
>
>
> On Apr 26, 2013, at 10:11 PM, Prashant Chougule <chougulepavan at gmail.com>
> wrote:
>
> > same problem with these flows also ,
> > unknown keyword priority when ./ovs-ofctl add-flow br0 file
> >
> >  1
> priority=60008,in_port=1,idle_timeout=0,nw_src=81.110.124.109,nw_dst=249.145.51.3,actions=output:2
> >   2
> priority=60007,in_port=1,idle_timeout=0,nw_src=81.110.124.62,nw_dst=74.104.165.223,actions=output:2
> >   3
> priority=60006,in_port=1,idle_timeout=0,nw_src=81.110.124.43,nw_dst=249.145.51.3,actions=output:2
> >   4
> priority=60005,in_port=1,idle_timeout=0,nw_src=81.110.124.34,nw_dst=249.145.51.3,actions=output:2
> >   5
> priority=60004,in_port=1,idle_timeout=0,nw_src=81.110.124.13,nw_dst=45.128.3.166,actions=output:2
> >   6
> priority=60003,in_port=1,idle_timeout=0,nw_src=81.110.124.0,nw_dst=249.145.51.3,actions=output:2
> >   7
> priority=60002,in_port=1,idle_timeout=0,nw_src=82.129.237.14,nw_dst=249.142.21.146,actions=output:2
> >   8
> priority=60002,in_port=1,idle_timeout=0,nw_src=82.129.237.25,nw_dst=249.142.21.146,actions=output:2
> >   9
> priority=60001,in_port=1,idle_timeout=0,nw_src=82.129.237.58,nw_dst=249.142.21.146,actions=output:2
> >  10
> priority=60000,in_port=1,idle_timeout=0,nw_src=82.129.237.181,nw_dst=45.128.3.166,actions=output:2
> >
> >  above flows not working, do i need to add some masking to abve i am
> using ovs-1.9.0 ?
> >
> > i try with other file with 10 flows like given one it, its working,it
> showing me in table.
> >
> >
>  priority=60000,idle_timeout=50000,dl_type=0x0806,nw_src=192.168.1.9,nw_dst=192.168.1.15,table=20,dl_dst=b8:70:f4:a
>    8:a3:34,dl_src=e8:40:f2:3c:ad:93,nw_proto=1,actions=output:1
> >
> >
> > On Sat, Apr 27, 2013 at 10:09 AM, Justin Pettit <jpettit at nicira.com>
> wrote:
> > Most of the priority definitions don't look wrong, but here are a few
> things:
> >
> >         - You can't specify a priority over 65535 (I see a 65536 in
> there), since it's expecting a 16-bit value.
> >         - Your dl_type won't work with your nw_src and nw_dst
> definitions, since it's not an IP ethertype.
> >         - I'm not sure it's in your file, but you can't put numbers
> before your flow definitions.
> >         - I'd use "ovs-ofctl add-flows <file>", since that's closer to
> what you want to do.
> >
> > --Justin
> >
> > On Apr 26, 2013, at 8:45 PM, Prashant Chougule <chougulepavan at gmail.com>
> wrote:
> >
> > > hi,
> > >
> > > I am trying to add file with 1000 rules, it will give me unknown
> keyword priority as a error if push individual flow it is working,
> > > some of the rules from the file
> > >
> > >
> > >    1
> priority=65536,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=81.110.124.109,nw_dst=249.145.51.3,actions=output:2
> > >   2
> priority=60001,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=81.110.124.62,nw_dst=74.104.165.223,actions=output:2
> > >   3
> priority=60002,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=81.110.124.43,nw_dst=249.145.51.3,actions=output:2
> > >   4
> priority=60003,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=81.110.124.34,nw_dst=249.145.51.3,actions=output:2
> > >   5
> priority=60004,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=81.110.124.13,nw_dst=45.128.3.166,actions=output:2
> > >   6
> priority=60005,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=81.110.124.0,nw_dst=249.145.51.3,actions=output:2
> > >   7
> priority=60006,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=82.129.237.14,nw_dst=249.142.21.146,actions=output:2
> > >   8
> priority=60007,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=82.129.237.25,nw_dst=249.142.21.146,actions=output:2
> > >   9
> priority=60008,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=82.129.237.58,nw_dst=249.142.21.146,actions=output:2
> > >  10
> priority=60009,idle_timeout=50000,dl_type=0x060,in_port=ANY,nw_src=82.129.237.181,nw_dst=45.128.3.166,actions=output:2
> > >  it is standard rule set i put it in openflow format,
> > > try with ./ovs-ofctl add-flow br0 -<file it show me ovs-ofctl: unknown
> keyword priority. is their any wrong in my syntax?
> > >
> > > --
> > > Thanks &Regards,
> > > Prashant Chougule.
> > > _______________________________________________
> > > discuss mailing list
> > > discuss at openvswitch.org
> > > http://openvswitch.org/mailman/listinfo/discuss
> >
> >
> >
> >
> > --
> > Thanks &Regards,
> > Prashant Chougule.
>
>


-- 
Thanks &Regards,
Prashant Chougule.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130427/17986c52/attachment.html>


More information about the discuss mailing list