RIPng Commands (Quagga)

In Fireware v12.8.x or lower, Fireware uses the Quagga routing software suite v1.2.4, which supports most routing commands available in more recent versions of Quagga.

In Fireware v12.9 or higher, Fireware uses the Free Range Routing (FRR) routing engine, which replaces Quagga. If your configuration includes Quagga commands for dynamic routing, those commands work after you upgrade. Some FRR commands appear in a different section than in Quagga.

To create or modify a routing configuration file, you must use the correct routing commands. This list includes some of the supported routing commands that you can use in a RIPng configuration. The sections must appear in the configuration file in the same order they appear in this list.

For a sample routing configuration file, go to Sample RIPng Routing Configuration File (Quagga).

To configure RIPng, go to Configure IPv6 Routing with RIPng.

Example RIPng Commands (Quagga in Fireware v12.8.x or Lower)

Section Command Description
Configure interfaces
  no ipv6 ripng split-horizon Disable split-horizon; enabled by default
Configure RIPng routing daemon
  router ripng Enable RIPng
Configure interfaces and networks
  network eth[N] Enable RIPng on the specified interface
  network [A:B:C:D:E:F:G:H/M] Enable RIPng on the specified network
  passive-interface eth[N] Set the specified interface to passive mode
Distribute routes to RIPng peers and inject OSPF or BGP routes to RIPng routing table
  route [A:B:C:D:E:F:G:H/M] Enable RIPng static route announcements for the specified IPv6 network
  distribute-list [ACCESS-LIST] (in|out) eth[N] Enable RIPng to use the specified access list to filter the RIPng path for the specified interface. The parameter in or out specifies whether the access list applies to incoming or outgoing packets on the specified interface.
  distribute-list prefix [PREFIX-LIST] (in|out) eth[N] Enable RIPng to use the specified prefix list to filter the RIPng path. The parameter in or out specifies whether the prefix list applies to incoming or outgoing packets on the specified interface.
  default-information originate Share route of last resort (default route) with RIPng peers
  default-metric <METRIC> Set the default metric value for redistributed routes. The metric must be an integer from 1 to 16.
  redistribute static Redistribute firewall static routes to RIPng peers
  redistribute static route-map [MAPNAME] Redistribute static routes, with a route map filter (mapname)
  redistribute connected Redistribute routes from all interfaces to RIPng peers
  redistribute connected route-map [MAPNAME] Redistribute routes from all interfaces to RIPng peers, with a route map filter (mapname)
  redistribute ospf6 Redistribute routes from OSPFv3 to RIPng
  redistribute ospf6 route-map [MAPNAME] Redistribute routes from OSPFv3 to RIPng, with a route map filter (mapname)
  redistribute bgp Redistribute routes from BGP to RIPng
  redistribute bgp route-map [MAPNAME] Redistribute routes from BGP to RIPng, with a route map filter (mapname)
Configure route redistribution filters with route maps and access lists
  ipv6 access-list [ACCESS-LIST] [PERMIT|DENY] [A,B,C,D/M | ANY] Create an access list to allow or deny redistribution of only one IP address or for all IP addresses
  ipv6 prefix-list [PREFIX-LIST] [PERMIT|DENY] [A,B,C,D/M | ANY] Create a prefix list with a name
  route-map [MAPNAME] permit [N] Create a route map with a name and allow with a priority of N
  match interface eth[N] Match the specified interface

Related Topics

About Routing Information Protocol (RIP and RIPng)

Configure IPv6 Routing with RIPng