On Fri, 13 Nov 2015, Christian Franke wrote:
For me I ended up defining a "nexthop" as an abstract concept that might
either be another router, an interface, or possibly in the future maybe
an MPLS action.
Or an ethernet address, etc.
This "nexthop" is described by a struct nexthop and has
a type like NEXTHOP_TYPE_IPV4, NEXTHOP_TYPE_IFINDEX, etc.
For the specific case of having an ip as a "nexthop", I tried to avoid
calling that ip "nexthop" since it may lead to confusion with the
general concept, but called it "gateway" instead - this is also what the
ip field in struct nexthop is called ("gate").
Does that reflect the general consensus how these objects should be
called, or does it differ?
Well, I guess an IP nexthop has to have an IP address, an IP ifindex
nexthop an ifindex. Also, we need IP address + ifindex for IPv6 link-local
right?
So the type perhaps need to refer to a family more generally, and each
family will have a set of things that are valid for it (ifindex, address,
whatever).
regards,
--
Paul Jakma p...@jakma.org @pjakma Key ID: 64A2FF6A
Fortune:
Getting into trouble is easy.
-- D. Winkel and F. Prosser
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
