One could add support to OVS for this model of VXLAN and other protocols. I do not see how tun_metadataXX is relevant to VXLAN, because it does not have Geneve- or NSH-like TLV options.
On Tue, Jun 04, 2019 at 01:48:56PM -0400, Vasu Dasari wrote: > Ben, > > Do you think, is there a way I can use "tun_metadataXX" infrastructure with > "push" and "pop" actions to achieve adding and remove headers? Or these > operations are quite centric to ash/geneveve, etc?? > > -Vasu > > *Vasu Dasari* > > > On Tue, Jun 4, 2019 at 1:13 PM Ben Pfaff <b...@ovn.org> wrote: > > > On Mon, Jun 03, 2019 at 09:33:03PM -0400, Vasu Dasari wrote: > > > I would like to specify VxLAN header fields in its entirety. That is, > > would > > > like to specify following fields of the VxLAN packet:, > > > > > > Output port: Physical port from which frame needs to leave. > > > Encapsulated L2 header: Ethernet Source, Destination, Vlan Tag > > > Encapsulated L3 header: IP source, Ip destination > > > VxLAN Header: VNI > > > > > > I see that I can specify L3 and VNI fields using, tun-src, tun-dst, > > tun-id > > > fields. > > > I am wondering how would I specify encapsulated L2 header and physical > > > output port information? > > > > OVS doesn't currently implement VXLAN that way. > > _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
