On 19/06/15 05:49, Roopa Prabhu wrote:
From: Roopa Prabhu <ro...@cumulusnetworks.com>
Introduces two netlink attributes RTA_ENCAP_TYPE and
RTA_ENCAP to support attaching encap information to ipv4 routes.
Surely RTA_ENCAP_TYPE should be part of RTA_ENCAP, since the type
doesn't make sense without the data and vice versa?
RTA_ENCAP is a nested attribute as suggested by Thomas
(and also as Robert had it in his series). RTA_ENCAP
netlink policy is declared by the light weight tunnel
drivers that support this encap type.
fib code calls the following for each nexthop:
- new route handler:
lwt build state (that parses RTA_ENCAP and returns
lwt state that lives in every fib_nh)
- del dump hanlder:
lwt release handler to release lwt state data
- route dump hanlder:
lwt dump encap to fill RTA_ENCAP data
- during input route lookup
sets dst->output to lwtunnel_output which
in turn calls the corresponding lwt tunnel
output function which applies the required
encap and xmits the packet
Signed-off-by: Roopa Prabhu <ro...@cumulusnetworks.com>
Thanks,
Rob
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
