7 *ripngd* supports the RIPng protocol as described in :rfc:`2080`. It's an IPv6
8 reincarnation of the RIP protocol.
15 There are no `ripngd` specific invocation options. Common options can be
16 specified (:ref:`common-invocation-options`).
18 .. _ripngd-configuration:
23 Currently ripngd supports the following commands:
25 .. index:: router ripng
26 .. clicmd:: router ripng
30 .. index:: flush_timer TIME
31 .. clicmd:: flush_timer TIME
35 .. index:: network NETWORK
36 .. clicmd:: network NETWORK
38 Set RIPng enabled interface by NETWORK.
40 .. index:: network IFNAME
41 .. clicmd:: network IFNAME
43 Set RIPng enabled interface by IFNAME.
45 .. index:: route NETWORK
46 .. clicmd:: route NETWORK
48 Set RIPng static routing announcement of NETWORK.
50 .. index:: router zebra
51 .. clicmd:: router zebra
53 This command is the default and does not appear in the configuration. With
54 this statement, RIPng routes go to the *zebra* daemon.
56 .. _ripngd-terminal-mode-commands:
58 ripngd Terminal Mode Commands
59 =============================
61 .. index:: show ip ripng
62 .. clicmd:: show ip ripng
64 .. index:: show debugging ripng
65 .. clicmd:: show debugging ripng
67 .. index:: debug ripng events
68 .. clicmd:: debug ripng events
70 .. index:: debug ripng packet
71 .. clicmd:: debug ripng packet
73 .. index:: debug ripng zebra
74 .. clicmd:: debug ripng zebra
77 ripngd Filtering Commands
78 =========================
80 .. index:: distribute-list ACCESS_LIST (in|out) IFNAME
81 .. clicmd:: distribute-list ACCESS_LIST (in|out) IFNAME
83 You can apply an access-list to the interface using the `distribute-list`
84 command. ACCESS_LIST is an access-list name. `direct` is ``in`` or
85 ``out``. If `direct` is ``in``, the access-list is applied only to incoming
88 distribute-list local-only out sit1