2006-06-27 09:52:03 +02:00
|
|
|
# Canonical Zserv route types information registry for Quagga.
|
|
|
|
|
#
|
|
|
|
|
# Used to construct route_types.c and route_types.h
|
|
|
|
|
#
|
|
|
|
|
# comma-seperated fields of either 2 fields (help strings) or 7 fields.
|
|
|
|
|
# White space before and after the comma seperators is stripped.
|
|
|
|
|
# Lines /beginning/ with # are comments.
|
|
|
|
|
#
|
|
|
|
|
####
|
|
|
|
|
# 7 field line has format:
|
|
|
|
|
# ZServ route type, canonical name, daemon, route char, ipv4, ipv6, short desc
|
|
|
|
|
#
|
|
|
|
|
# Zserv route type: Corresponding with zebra.h. Key field.
|
|
|
|
|
# canonical name: Typically derived from the route type definition.
|
|
|
|
|
# Used in 'redistribute' commands in daemons.
|
|
|
|
|
# Key field.
|
|
|
|
|
# daemon: The daemon which may originates this route type
|
|
|
|
|
# for redistribution to other daemons.
|
|
|
|
|
# NULL if not applicable.
|
|
|
|
|
# M:N definitions of type:daemon are allowed.
|
|
|
|
|
# Used to construct vty command strings.
|
|
|
|
|
# route char: Single character to denote the route, if applicable.
|
|
|
|
|
# Used to denote route type where space is tight,
|
|
|
|
|
# e.g. 'show ip route' / 'show ipv6 route'.
|
|
|
|
|
# 'X' is reserved as the 'not needed' placeholder.
|
|
|
|
|
# ipv4: IPv4 capable? yes/no, or 1/0.
|
|
|
|
|
# ipv6: IPv6 capable? ditto.
|
|
|
|
|
# short desc: Very brief description. Used in header of
|
|
|
|
|
# 'show ip route'. May be specified as NULL
|
|
|
|
|
# if the canonical name suffices.
|
|
|
|
|
#
|
|
|
|
|
# Key fields obviously must be a unique ASCII alpha-numeric word.
|
|
|
|
|
# Lower-case is required, brevity is optional but highly desirable.
|
|
|
|
|
#
|
|
|
|
|
####
|
|
|
|
|
# 2 field format:
|
|
|
|
|
#
|
|
|
|
|
# Zserv route type, Long description
|
|
|
|
|
#
|
|
|
|
|
# Long description: Full description, but should try fit on a line.
|
|
|
|
|
####
|
|
|
|
|
|
|
|
|
|
## type cname daemon C 4 6 short help
|
|
|
|
|
ZEBRA_ROUTE_SYSTEM, system, NULL, 'X', 0, 0, "Reserved"
|
2009-09-16 01:52:42 +02:00
|
|
|
ZEBRA_ROUTE_KERNEL, kernel, zebra, 'K', 1, 1, "kernel route"
|
|
|
|
|
ZEBRA_ROUTE_CONNECT, connected, zebra, 'C', 1, 1, "connected"
|
|
|
|
|
ZEBRA_ROUTE_STATIC, static, zebra, 'S', 1, 1, "static"
|
2006-06-27 09:52:03 +02:00
|
|
|
ZEBRA_ROUTE_RIP, rip, ripd, 'R', 1, 0, "RIP"
|
|
|
|
|
ZEBRA_ROUTE_RIPNG, ripng, ripngd, 'R', 0, 1, "RIPng"
|
|
|
|
|
ZEBRA_ROUTE_OSPF, ospf, ospfd, 'O', 1, 0, "OSPF"
|
2016-10-13 02:20:15 +02:00
|
|
|
ZEBRA_ROUTE_OSPF6, ospf6, ospf6d, 'O', 0, 1, "OSPFv3"
|
2006-06-27 09:52:03 +02:00
|
|
|
ZEBRA_ROUTE_ISIS, isis, isisd, 'I', 1, 1, "IS-IS"
|
|
|
|
|
ZEBRA_ROUTE_BGP, bgp, bgpd, 'B', 1, 1, "BGP"
|
2015-02-04 07:01:14 +01:00
|
|
|
ZEBRA_ROUTE_PIM, pim, pimd, 'P', 1, 0, "PIM"
|
2006-06-27 09:52:03 +02:00
|
|
|
# HSLS and OLSR both are AFI independent (so: 1, 1), however
|
|
|
|
|
# we want to disable for them for general Quagga distribution.
|
|
|
|
|
# This at least makes it trivial for users of these protocols
|
|
|
|
|
# to 'switch on' redist support (direct numeric entry remaining
|
|
|
|
|
# possible).
|
|
|
|
|
ZEBRA_ROUTE_HSLS, hsls, hslsd, 'H', 0, 0, "HSLS"
|
2009-09-16 01:52:42 +02:00
|
|
|
ZEBRA_ROUTE_OLSR, olsr, olsrd, 'o', 0, 0, "OLSR"
|
2015-05-20 03:03:42 +02:00
|
|
|
ZEBRA_ROUTE_TABLE, table, zebra, 'T', 1, 1, "Table"
|
2016-03-01 19:31:28 +01:00
|
|
|
ZEBRA_ROUTE_LDP, ldp, ldpd, 'L', 0, 0, "LDP"
|
bgpd: add L3/L2VPN Virtual Network Control feature
This feature adds an L3 & L2 VPN application that makes use of the VPN
and Encap SAFIs. This code is currently used to support IETF NVO3 style
operation. In NVO3 terminology it provides the Network Virtualization
Authority (NVA) and the ability to import/export IP prefixes and MAC
addresses from Network Virtualization Edges (NVEs). The code supports
per-NVE tables.
The NVE-NVA protocol used to communicate routing and Ethernet / Layer 2
(L2) forwarding information between NVAs and NVEs is referred to as the
Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. For
general background on NVO3 and RFP concepts see [1]. For information on
Openflow see [2].
RFPs are integrated with BGP via the RF API contained in the new "rfapi"
BGP sub-directory. Currently, only a simple example RFP is included in
Quagga. Developers may use this example as a starting point to integrate
Quagga with an RFP of their choosing, e.g., OpenFlow. The RFAPI code
also supports the ability import/export of routing information between
VNC and customer edge routers (CEs) operating within a virtual
network. Import/export may take place between BGP views or to the
default zebera VRF.
BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VPN
information between NVAs. BGP based IP VPN support is defined in
RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659,
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Use
of both the Encapsulation Subsequent Address Family Identifier (SAFI)
and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute, are supported. MAC address distribution does
not follow any standard BGB encoding, although it was inspired by the
early IETF EVPN concepts.
The feature is conditionally compiled and disabled by default.
Use the --enable-bgp-vnc configure option to enable.
The majority of this code was authored by G. Paul Ziemba
<paulz@labn.net>.
[1] http://tools.ietf.org/html/draft-ietf-nvo3-nve-nva-cp-req
[2] https://www.opennetworking.org/sdn-resources/technical-library
Now includes changes needed to merge with cmaster-next.
2016-05-07 20:18:56 +02:00
|
|
|
#vnc when sent to zebra
|
|
|
|
|
ZEBRA_ROUTE_VNC, vnc, NULL, 'v', 1, 1, "VNC"
|
|
|
|
|
# vnc when sent to bgp
|
2016-11-04 17:47:36 +01:00
|
|
|
ZEBRA_ROUTE_VNC_DIRECT, vnc-direct,NULL, 'V', 1, 1, "VNC-Direct", bgpd
|
|
|
|
|
# vnc when sent to bgp (resolve NVE mode)
|
|
|
|
|
ZEBRA_ROUTE_VNC_DIRECT_RH, vnc-rn, NULL, 'V', 0, 0, "VNC-RN"
|
bgpd: add L3/L2VPN Virtual Network Control feature
This feature adds an L3 & L2 VPN application that makes use of the VPN
and Encap SAFIs. This code is currently used to support IETF NVO3 style
operation. In NVO3 terminology it provides the Network Virtualization
Authority (NVA) and the ability to import/export IP prefixes and MAC
addresses from Network Virtualization Edges (NVEs). The code supports
per-NVE tables.
The NVE-NVA protocol used to communicate routing and Ethernet / Layer 2
(L2) forwarding information between NVAs and NVEs is referred to as the
Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. For
general background on NVO3 and RFP concepts see [1]. For information on
Openflow see [2].
RFPs are integrated with BGP via the RF API contained in the new "rfapi"
BGP sub-directory. Currently, only a simple example RFP is included in
Quagga. Developers may use this example as a starting point to integrate
Quagga with an RFP of their choosing, e.g., OpenFlow. The RFAPI code
also supports the ability import/export of routing information between
VNC and customer edge routers (CEs) operating within a virtual
network. Import/export may take place between BGP views or to the
default zebera VRF.
BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VPN
information between NVAs. BGP based IP VPN support is defined in
RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659,
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Use
of both the Encapsulation Subsequent Address Family Identifier (SAFI)
and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute, are supported. MAC address distribution does
not follow any standard BGB encoding, although it was inspired by the
early IETF EVPN concepts.
The feature is conditionally compiled and disabled by default.
Use the --enable-bgp-vnc configure option to enable.
The majority of this code was authored by G. Paul Ziemba
<paulz@labn.net>.
[1] http://tools.ietf.org/html/draft-ietf-nvo3-nve-nva-cp-req
[2] https://www.opennetworking.org/sdn-resources/technical-library
Now includes changes needed to merge with cmaster-next.
2016-05-07 20:18:56 +02:00
|
|
|
# bgp unicast -> vnc
|
|
|
|
|
ZEBRA_ROUTE_BGP_DIRECT, bgp-direct, NULL, 'b', 0, 0, "BGP-Direct"
|
|
|
|
|
# bgp unicast -> vnc
|
|
|
|
|
ZEBRA_ROUTE_BGP_DIRECT_EXT, bgp-direct-to-nve-groups, NULL, 'e', 0, 0, "BGP2VNC"
|
2016-10-05 22:58:01 +02:00
|
|
|
ZEBRA_ROUTE_ALL, wildcard, none, '-', 0, 0, "-"
|
2006-06-27 09:52:03 +02:00
|
|
|
|
|
|
|
|
## help strings
|
|
|
|
|
ZEBRA_ROUTE_SYSTEM, "Reserved route type, for internal use only"
|
|
|
|
|
ZEBRA_ROUTE_KERNEL, "Kernel routes (not installed via the zebra RIB)"
|
|
|
|
|
ZEBRA_ROUTE_CONNECT,"Connected routes (directly attached subnet or host)"
|
|
|
|
|
ZEBRA_ROUTE_STATIC, "Statically configured routes"
|
|
|
|
|
ZEBRA_ROUTE_RIP, "Routing Information Protocol (RIP)"
|
|
|
|
|
ZEBRA_ROUTE_RIPNG, "Routing Information Protocol next-generation (IPv6) (RIPng)"
|
|
|
|
|
ZEBRA_ROUTE_OSPF, "Open Shortest Path First (OSPFv2)"
|
|
|
|
|
ZEBRA_ROUTE_OSPF6, "Open Shortest Path First (IPv6) (OSPFv3)"
|
|
|
|
|
ZEBRA_ROUTE_ISIS, "Intermediate System to Intermediate System (IS-IS)"
|
|
|
|
|
ZEBRA_ROUTE_BGP, "Border Gateway Protocol (BGP)"
|
2015-02-04 07:01:14 +01:00
|
|
|
ZEBRA_ROUTE_PIM, "Protocol Independent Multicast (PIM)"
|
2006-06-27 09:52:03 +02:00
|
|
|
ZEBRA_ROUTE_HSLS, "Hazy-Sighted Link State Protocol (HSLS)"
|
bgpd: add L3/L2VPN Virtual Network Control feature
This feature adds an L3 & L2 VPN application that makes use of the VPN
and Encap SAFIs. This code is currently used to support IETF NVO3 style
operation. In NVO3 terminology it provides the Network Virtualization
Authority (NVA) and the ability to import/export IP prefixes and MAC
addresses from Network Virtualization Edges (NVEs). The code supports
per-NVE tables.
The NVE-NVA protocol used to communicate routing and Ethernet / Layer 2
(L2) forwarding information between NVAs and NVEs is referred to as the
Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. For
general background on NVO3 and RFP concepts see [1]. For information on
Openflow see [2].
RFPs are integrated with BGP via the RF API contained in the new "rfapi"
BGP sub-directory. Currently, only a simple example RFP is included in
Quagga. Developers may use this example as a starting point to integrate
Quagga with an RFP of their choosing, e.g., OpenFlow. The RFAPI code
also supports the ability import/export of routing information between
VNC and customer edge routers (CEs) operating within a virtual
network. Import/export may take place between BGP views or to the
default zebera VRF.
BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VPN
information between NVAs. BGP based IP VPN support is defined in
RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659,
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Use
of both the Encapsulation Subsequent Address Family Identifier (SAFI)
and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute, are supported. MAC address distribution does
not follow any standard BGB encoding, although it was inspired by the
early IETF EVPN concepts.
The feature is conditionally compiled and disabled by default.
Use the --enable-bgp-vnc configure option to enable.
The majority of this code was authored by G. Paul Ziemba
<paulz@labn.net>.
[1] http://tools.ietf.org/html/draft-ietf-nvo3-nve-nva-cp-req
[2] https://www.opennetworking.org/sdn-resources/technical-library
Now includes changes needed to merge with cmaster-next.
2016-05-07 20:18:56 +02:00
|
|
|
ZEBRA_ROUTE_VNC, "Virtual Network Control (VNC)"
|
2006-06-27 09:52:03 +02:00
|
|
|
ZEBRA_ROUTE_OLSR, "Optimised Link State Routing (OLSR)"
|
2015-05-20 03:03:42 +02:00
|
|
|
ZEBRA_ROUTE_TABLE, "Non-main Kernel Routing Table"
|
2016-03-01 19:31:28 +01:00
|
|
|
ZEBRA_ROUTE_LDP, "Label Distribution Protocol (LDP)"
|
2016-11-04 17:47:36 +01:00
|
|
|
ZEBRA_ROUTE_VNC_DIRECT, "VNC direct (not via zebra) routes"
|