From: Jiri Benc <jb...@redhat.com> Date: Tue, 22 Sep 2015 18:12:10 +0200
> One of the selling points of lwtunnel was the ability to specify the tunnel > destination using routes. However, this doesn't really work currently, as > ARP and ndisc replies are not handled correctly. ARP and ndisc replies won't > have tunnel metadata attached, thus they will be sent out with the default > parameters or not sent at all, either way never reaching the requester. > > Most of the egress tunnel parameters can be inferred from the ingress > metada. The only and important exception is UDP ports. This patchset infers > the egress data from the ingress data and disallow settings of UDP ports in > tunnel routes. If there's a need for different UDP ports, a new interface > needs to be created for each port combination. Note that it's still possible > to specify the UDP ports to use, it just needs to be done while creating the > vxlan/geneve interface. > > This covers only ARPs. IPv6 ndisc has the same problem but is harder to > solve, as there's already dst attached to outgoing skbs. Ideas to solve this > are welcome. I'm applying this series as-is, as it's a reasonable step forward in dealing with this issue. Thanks Jiri. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
