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 .. clicmd:: router ripng [vrf NAME]
  26
  27    Enable RIPng.
  28
  29 .. clicmd:: network NETWORK
  30
  31    Set RIPng enabled interface by NETWORK.
  32
  33 .. clicmd:: network IFNAME
  34
  35    Set RIPng enabled interface by IFNAME.
  36
  37 .. clicmd:: route NETWORK
  38
  39    Set RIPng static routing announcement of NETWORK.
  40
  41 .. clicmd:: allow-ecmp [1-MULTIPATH_NUM]
  42
  43    Control how many ECMP paths RIPng can inject for the same prefix. If specified
  44    without a number, a maximum is taken (compiled with ``--enable-multipath``).
  45
  46 .. _ripngd-terminal-mode-commands:
  47
  48 ripngd Terminal Mode Commands
  49 =============================
  50
  51 .. clicmd:: show ipv6 ripng [vrf NAME] status
  52
  53 .. clicmd:: show debugging ripng
  54
  55 .. clicmd:: debug ripng events
  56
  57 .. clicmd:: debug ripng packet
  58
  59 .. clicmd:: debug ripng zebra
  60
  61
  62 ripngd Filtering Commands
  63 =========================
  64
  65 RIPng routes can be filtered by a distribute-list.
  66
  67 .. clicmd:: distribute-list [prefix] LIST <in|out> IFNAME
  68
  69    You can apply access lists to the interface with a `distribute-list` command.
  70    If prefix is specified LIST is a prefix-list.  If prefix is not specified
  71    then LIST is the access list name.  `in` specifies packets being received,
  72    and `out` specifies outgoing packets.  Finally if an interface is specified
  73    it will be applied against a specific interface.
  74
  75    The ``distribute-list`` command can be used to filter the RIPNG path.
  76    ``distribute-list`` can apply access-lists to a chosen interface.  First, one
  77    should specify the access-list. Next, the name of the access-list is used in
  78    the distribute-list command. For example, in the following configuration
  79    ``eth0`` will permit only the paths that match the route 10.0.0.0/8
  80
  81    .. code-block:: frr
  82
  83       !
  84       router ripng
  85        distribute-list private in eth0
  86       !
  87       access-list private permit 10 10.0.0.0/8
  88       access-list private deny any
  89       !
  90
  91
  92    `distribute-list` can be applied to both incoming and outgoing data.
  93
  94
  95 Sample configuration
  96 ====================
  97
  98 .. code-block:: frr
  99
 100    debug ripng events
 101    debug ripng packet
 102
 103    router ripng
 104     network sit1
 105     route 3ffe:506::0/32
 106     distribute-list local-only out sit1
 107
 108    ipv6 access-list local-only permit 3ffe:506::0/32
 109    ipv6 access-list local-only deny any