On Mon, Feb 23, 2015 at 1:36 PM, Mehrdad Moradi <[email protected]>
wrote:
> Thanks Minoru for the response. Given this feature is not available, do
> you know if it is possible
> to match both VLAN and MPLS tags in one flow entry? For example, the
> following:
>
> If (vlan_id ==10 and mpls_label==20): drop packet
>
> or we will need to first let's say match on MPLS label and pop its label
> in the first flow table
> and then match on the vlan_id in the second table and drop the packet there
>
As you've pointed out, this is ambiguous. Does this mean MPLSoE or
EoMPLS? The OpenFlow spec is not at all specific when it comes to these
kinds of questions, and I think you should expect that they are unlikely to
work the way you want. Even in a switch where there are multiple tables of
different capabilities and the ordering seems clear (e.g. the MPLS match
table comes before the L2 VLAN table, etc.), it may still not allow
actually making a match in that second table because making a *match* in
the first table doesn't actually change the parse state of the packet
unless you have immediate action sets available.
--
Nick
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel
