RIPng
ripngd supports the RIPng protocol as described in RFC 2080. It’s an IPv6 reincarnation of the RIP protocol.
ripngd Configuration
Currently ripngd supports the following commands:
- router ripng
 Enable RIPng.
- flush_timer TIME
 Set flush timer.
- network NETWORK
 Set RIPng enabled interface by NETWORK.
- network IFNAME
 Set RIPng enabled interface by IFNAME.
- route NETWORK
 Set RIPng static routing announcement of NETWORK.
ripngd Terminal Mode Commands
- show ip ripng
 
- show debugging ripng
 
- debug ripng events
 
- debug ripng packet
 
- debug ripng zebra
 
ripngd Filtering Commands
RIPng routes can be filtered by a distribute-list.
- distribute-list [prefix] LIST <in|out> IFNAME
 You can apply access lists to the interface with a distribute-list command. If prefix is specified LIST is a prefix-list. If prefix is not specified then LIST is the access list name. in specifies packets being received, and out specifies outgoing packets. Finally if an interface is specified it will be applied against a specific interface.
The
distribute-listcommand can be used to filter the RIPNG path.distribute-listcan apply access-lists to a chosen interface. First, one should specify the access-list. Next, the name of the access-list is used in the distribute-list command. For example, in the following configurationeth0will permit only the paths that match the route 10.0.0.0/8! router ripng distribute-list private in ge0 ! access-list private permit 10.0.0.0/8 any deny any any !
distribute-list can be applied to both incoming and outgoing data.
Sample configuration
debug ripng events
debug ripng packet
router ripng
 network ge0
 route 3ffe:506::0/32
 distribute-list local-only out sit1
ipv6 access-list local-only
 permit 3ffe:506::0/32 any
 deny any any