Please don't drop the list. You could add support for this encapsulation to OVS, but that's not necessarily easy because it requires making nontrivial changes in multiple places.
You could probably kluge in support by using some kind of kernel feature. I don't know how to do that. Or you could just use one of the many encapsulations natively supported by OVS. OVS has support for GRE, VXLAN, STT, Geneve, and NSH over IPv6. On Wed, Jan 02, 2019 at 11:44:06AM -0500, Prathamesh Prabhudesai wrote: > So is there a way I can do that? If I have v4 packet, I need to put v6 > header on top of it and get it in the OVS pipeling again? > > On Wed, Jan 2, 2019 at 11:18 AM Ben Pfaff <[email protected]> wrote: > > > On Wed, Jan 02, 2019 at 11:09:41AM -0500, Prathamesh Prabhudesai wrote: > > > Hello Team > > > > > > I am not sure if its the right way to contact you guys but I am learning > > > OVS and would be great if you can answer my question. Is it possible to > > set > > > the action as output to some tunnel where I am just encapsulating a > > packet > > > in user space and then get the new encapped packet back in the OVS > > pipeline > > > to process more rules? If its not possible then how can I encap my packet > > > without doing an output action. > > > > > > To be more specific: > > > I have v4 packet which is in the flow pipeline. Then I want to put a v6 > > > header on top of the v4 packet (ipinip6). Then again I want it back in > > the > > > OVS pipeline just to process more rules. > > > > > > It will be really helpful if you can clear my doubt. I have been > > struggling > > > with it for a long time. > > > > I don't think OVS supports that encapsulation. > > > > > -- > > Sincerely, > > Prathamesh Prabhudesai <http://prathprabhudesai.github.io/> > > Software Developer at Nokia > > NC State Graduate > > (919)-948-8794 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
