Sample RIPng Routing Configuration File (FRR)

To use the RIPng dynamic routing protocol with Fireware, you must type RIPng configuration commands or import a configuration file on the Network > Dynamic Routing page. This topic includes a sample configuration file. To use this configuration file as a starting point for your RIPng configuration, copy the text into a text editor application and edit the parameters to meet your business requirements.

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.

For information about RIPng requirements and how to configure RIPng, go to Configure IPv6 Routing with RIPng.

In Fireware v12.8.x or lower, Fireware uses the Quagga routing engine. For a sample routing configuration file for Fireware v12.8.x or lower, go to Sample RIPng Routing Configuration File (Quagga). For a list of Quagga commands, go to RIPng Commands (Quagga).

Sample

This configuration sample shows how to configure some common RIPng commands that you might include in your RIPng configuration in Fireware v12.9 or higher. Your configuration file might include other commands.

For descriptions of common commands, go toRIPng Commands (FRR). For a complete list of FRR commands, go to the FRRouting User Guide.

! SECTION 1: Configure global RIPng daemon properties.

! Enable RIPng daemon. Must be enabled for all RIPng configurations.

 router ripng

! Share route of last resort (default route) from kernel routing table with RIPng peers. 	

 default-information originate 	

! Configure interfaces and networks. 

! Enable RIPng on interface(eth0). 

 network eth0	

! Enable RIPng on network (2000::/64)

 network 2000::/64	

! Set RIPng to receive-only on interface (eth2).	

 passive-interface eth2

! Filter networks in incoming routing updates

distribute-list LISTNAME in 

! Redistribute RIPng routes to peers and inject OSPFv3 or BGP routes to RIPng routing table. 	

! Redistribute firewall static routes to RIPng peers. 	

 redistribute static 	

! Set route maps (MAPNAME) to restrict route redistribution in Section 4. 

! Redistribute routes from all interfaces to RIPng peers or with a route map filter (MAPNAME). 

 redistribute connected  

 redistribute connected route-map MAPNAME 

! Redistribute routes from OSPFv3 to RIPng or with a route map filter (MAPNAME). 

 redistribute ospf6 

 redistribute ospf6 route-map MAPNAME 

! Redistribute routes from BGP to RIPng or with a route map filter (MAPNAME). 

 redistribute bgp 

 redistribute bgp route-map MAPNAME

 

! SECTION 2: Configure route redistribution filters with route maps and access lists.

! Create an ipv6 access list to only allow network 3000::/64. 

ipv6 access-list LISTNAME permit 3000::/64 	

ipv6 access-list LISTNAME deny any 

! SECTION 3: Create a route map.

! Create a route map with name MAPNAME and allow with a priority of 10 (1-199). 	

route-map MAPNAME permit 10 		

match interface eth1		

Related Topics

About Routing Information Protocol (RIP and RIPng)

RIPng Commands (FRR)

Configure IPv6 Routing with RIPng