Sample RIPng Routing Configuration File

To use any of the dynamic routing protocols with Fireware XTM, you must import or copy and paste a configuration file for the dynamic routing daemon. This topic includes a sample configuration file for the RIP routing daemon. If you want to use this configuration file as a base for your own configuration file, copy the text into an application such as Notepad or Wordpad and save it with a new name. You can then edit the parameters to meet the requirements of your organization.

Optional commands are commented with the "!" character. To enable a command, delete the "!" and modify variables as necessary.

!! SECTION 1: Configure global RIPng daemon properties.
!! Enable RIPng daemon. Must be enabled for all RIPng configurations.
! router ripng

!!! SECTION 2: 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

!! SECTION 3: Redistribute RIPng routes to peers and inject OSPFv3 or BGP routes to RIPng routing table.
!! Share route of last resort (default route) from kernel routing table with RIPng peers.
! default-information originate
!! 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 4: Configure route redistribution filters with route maps and access lists.
!!Filter networks in incoming routing updates
! distribute-list LISTNAME in
!! Create an ipv6 access list to only allow network 3000::/64.
! ipv6 access-list LISTNAME permit 3000::/64
! ipv6 access-list LISTNAME deny any
!! Create a route map with name MAPNAME and allow with a priority of 10.
! route-map MAPNAME permit 10
! match interface eth1

See Also

About Routing Information Protocol (RIP and RIPng)

RIPng Commands

Configure IPv6 Routing with RIPng

Give Us Feedback  •   Get Support  •   All Product Documentation  •   Technical Search

© 2018 WatchGuard Technologies, Inc. All rights reserved. WatchGuard, the WatchGuard logo, WatchGuard Dimension, Firebox, Core, Fireware, and LiveSecurity are registered trademarks or trademarks of WatchGuard Technologies in the United States and/or other countries.