hi Alin, > actions=strip_vlan,set_tunnel:0x3e9,15,16,17 In the actions above, if 16, and 17 are VXLAN ports, they’ll need a tunnel context to work with. You mention that the tunnel context for 16 and 17 is different from that of 15. In which case, you should be seeing something like: actions=strip_vlan,set_tunnel:0x3e9,15,set_tunnel:0x1234,16,setLtunnel:0x7834, 17
For the latter flow, the existing code works perfectly. However, for the former flow where I don’t see new tunnel context being setup for 16 & 17. Assuming that they are using the same context as 15, you’s also need to make sure that 15’s tunnel context gets saved after processing 15, so that 16 and 17 can use it. So, you’ll have to save ovsFwdCxt->tunKey. In any case, your patch is an improvement over existing code, so I’m ACKing it. Acked-by: Nithin Raju <nit...@vmware.com> -- Nithin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
