doc/user/ripngd.rst

   1 .. _RIPng:
   2
   3 *****
   4 RIPng
   5 *****
   6
   7 *ripngd* supports the RIPng protocol as described in :rfc:`2080`. It's an IPv6
   8 reincarnation of the RIP protocol.
   9
  10 .. _Invoking_ripngd:
  11
  12 Invoking ripngd
  13 ===============
  14
  15 There are no `ripngd` specific invocation options. Common options can be
  16 specified (:ref:`Common_Invocation_Options`).
  17
  18 .. _ripngd_Configuration:
  19
  20 ripngd Configuration
  21 ====================
  22
  23 Currently ripngd supports the following commands:
  24
  25 .. index:: router ripng
  26 .. clicmd:: router ripng
  27
  28    Enable RIPng.
  29
  30 .. index:: flush_timer TIME
  31 .. clicmd:: flush_timer TIME
  32
  33    Set flush timer.
  34
  35 .. index:: network NETWORK
  36 .. clicmd:: network NETWORK
  37
  38    Set RIPng enabled interface by NETWORK.
  39
  40 .. index:: network IFNAME
  41 .. clicmd:: network IFNAME
  42
  43    Set RIPng enabled interface by IFNAME.
  44
  45 .. index:: route NETWORK
  46 .. clicmd:: route NETWORK
  47
  48    Set RIPng static routing announcement of NETWORK.
  49
  50 .. index:: router zebra
  51 .. clicmd:: router zebra
  52
  53    This command is the default and does not appear in the configuration. With
  54    this statement, RIPng routes go to the *zebra* daemon.
  55
  56 .. _ripngd_Terminal_Mode_Commands:
  57
  58 ripngd Terminal Mode Commands
  59 =============================
  60
  61 .. index:: show ip ripng
  62 .. clicmd:: show ip ripng
  63
  64 .. index:: show debugging ripng
  65 .. clicmd:: show debugging ripng
  66
  67 .. index:: debug ripng events
  68 .. clicmd:: debug ripng events
  69
  70 .. index:: debug ripng packet
  71 .. clicmd:: debug ripng packet
  72
  73 .. index:: debug ripng zebra
  74 .. clicmd:: debug ripng zebra
  75
  76
  77 ripngd Filtering Commands
  78 =========================
  79
  80 .. index:: distribute-list ACCESS_LIST (in|out) IFNAME
  81 .. clicmd:: distribute-list ACCESS_LIST (in|out) IFNAME
  82
  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
  86    packets.::
  87
  88       distribute-list local-only out sit1
  89