Configure IPv6 Routing with RIPng

This topic explains how to configure RIPng on your Firebox. Use RIPng for dynamic routing between IPv6 networks.

Free Range Routing (Fireware v12.9 or Higher)

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 a routing configuration file sample, go to Sample RIPng Routing Configuration File (FRR).

For a list of commands, see RIPng Commands (FRR).

Quagga (Fireware v12.8.x or Lower)

Quagga is the routing daemon in Fireware v12.8.x or lower.

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

For a list of commands, go to RIPng Commands (Quagga).

When you enable RIPng, a dynamic routing policy called DR-RIPng-Allow is automatically created. You can edit this policy to add authentication and restrict the policy to listen on only the correct interfaces. The DR-RIPng-Allow policy is configured to allow RIPng multicasts to the reserved multicast address for RIPng, FF02::9.

After you configure the Firebox and the BGP router, you can look at the routes table to verify that the Firebox has received route updates from the RIPng router.

To see the dynamic routes, from Firebox System Manager, select the Status Report tab.

To see the dynamic routes, from Fireware Web UI, select System Status > Routes.

Related Topics

About Routing Information Protocol (RIP and RIPng)