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