That's true, and it's how I would write it. I was trying to emphasize the fact that the values there were not relevant, but the f's also munged with the first part of the mask, so it didn't really help clarify much.
--Justin > On Aug 19, 2016, at 10:55 AM, Ben Pfaff <b...@ovn.org> wrote: > > Usually we'd write this as dl_dst=01:02:03:00:00:00/ff:ff:ff:00:00:00. > That is, it's conventional to write the wildcarded bits as 0s. > > On Fri, Aug 19, 2016 at 10:09:31AM -0700, Justin Pettit wrote: >> The ovs-ofctl man page has examples. However, here's another: >> "dl_dst=01:02:03:ff:ff:ff/ff:ff:ff:00:00:00" matches any destination mac >> address that begins with "01:02:03". >> >> --Justin >> >> >>> On Aug 19, 2016, at 10:06 AM, Amrane Ait Zeouay <a.zeouayam...@gmail.com> >>> wrote: >>> >>> So how can you give me an example of wildcarded match. >>> >>> On 19 Aug 2016 19:04, "Justin Pettit" <jpet...@ovn.org> wrote: >>> >>>> On Aug 19, 2016, at 9:59 AM, Amrane Ait Zeouay <a.zeouayam...@gmail.com> >>>> wrote: >>>> >>>> Thank you for your reply, just the last question. How can i add a >>>> wildcarded match is it like ovs-oftcl add-flow br0 >>>> dl_dst=ff:ff:ff:ff:ff:00/ff:ff:ff:ff:ff:ff,actions=output:2 >>> >>> The format looks basically correct, but the match is sort of odd. If you >>> specify the all-ones wildcard, it's an exact match, so you don't need to >>> specify it; this would have the same effect: "dl_dst=ff:ff:ff:ff:ff:00". >>> And that seems like an odd MAC address, but I don't know your application. >>> >>> --Justin >>> >>> >> >> _______________________________________________ >> discuss mailing list >> discuss@openvswitch.org >> http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
