With reference to the Openflow spec 1.3.2
Match field has,
OFPXMT_OFB_TUNNEL_ID
Some theory about it,
A.11.10
Tunnel-ID metadata
The logical port abstraction enables OpenFlow to support a wide variety of
encapsulations. The tunnel-
id metadata OXM_OF_TUNNEL_ID is a new OXM field that expose to the OpenFlow
pipeline metadata
associated with the logical port, most commonly the demultiplexing field
from the encapsulation header
(EXT-107).
For example, if the logical port perform GRE encapsulation, the tunnel-id
field would map to the GRE
key field from the GRE header. After decapsulation, OpenFlow would be able
to match the GRE key
in the tunnel-id match field. Similarly, by setting the tunnel-id, OpenFlow
would be able to set the
GRE key in an encapsulated packet
Thanks
suresh
On Wed, May 23, 2018 at 5:00 PM, Bilal Saleem <mb...@nyu.edu> wrote:
> Hi,
>
> Is there any way to create rules based on gre key field value
>
> I want something like this:
>
> match2 = parser.OFPMatch(in_port=2, eth_dst=dst, eth_type=0x0800,
> ip_proto=47, *grekey=XXXXX*)
>
> Regards
> Bilal
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Ryu-devel mailing list
> Ryu-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>
>
--
*Regards, *
*Knet solutions.*
https://github.com/knetsolutions/KNet
http://knet-topology-builder.readthedocs.io/
http://knetsolutions.in/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel
