No support for Eth + IP + NSH, NSH RFC doesn't say to support it, I think Eth + NSH is enough, I don't understand why you want to insert unnecessary IP header there.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Frederic Tobias Christ Sent: Wednesday, August 1, 2018 6:10 PM To: [email protected] Subject: [ovs-discuss] Supported transport encapsulation for NSH Hi all, I am trying to set up Service Function Chaining (SFC) via Network Service Header (NSH). Since I did not find documentation except the ovs-ofctl man page, I used the test cases like https://github.com/openvswitch/ovs/blob/4e7cef049ada088cbba1e9b29d7d46b5599312a8/tests/nsh.at#L16. While setting up flow entries with matching ethernet- and NSH fields works great, I could not get matching on IP and NSH working. - Is is correct, that matching NSH currently only works with Ethernet as the transport encapsulation? - Is it planned yet to support matching on NSH for other transport encapsulations, for example IP? Thank you and best regards Frederic Christ _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
