|author||David S. Miller <firstname.lastname@example.org>||2015-09-24 14:31:37 -0700|
|committer||David S. Miller <email@example.com>||2015-09-24 14:31:37 -0700|
|parent||net: gianfar: remove misuse of IRQF_NO_SUSPEND flag (diff)|
|parent||lwtunnel: remove source and destination UDP port config option (diff)|
Merge branch 'lwt_arp'
Jiri Benc says: ==================== lwtunnel: make it really work, for IPv4 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. ==================== Signed-off-by: David S. Miller <firstname.lastname@example.org>
Diffstat (limited to 'net/sched/cls_fw.c')
0 files changed, 0 insertions, 0 deletions