]>
Commit | Line | Data |
---|---|---|
0efdf0fe | 1 | .. _ripng: |
42fc5d26 QY |
2 | |
3 | ***** | |
4 | RIPng | |
5 | ***** | |
6 | ||
c1a54c05 QY |
7 | *ripngd* supports the RIPng protocol as described in :rfc:`2080`. It's an IPv6 |
8 | reincarnation of the RIP protocol. | |
42fc5d26 | 9 | |
0efdf0fe | 10 | .. _invoking-ripngd: |
42fc5d26 QY |
11 | |
12 | Invoking ripngd | |
13 | =============== | |
14 | ||
c1a54c05 | 15 | There are no `ripngd` specific invocation options. Common options can be |
0efdf0fe | 16 | specified (:ref:`common-invocation-options`). |
42fc5d26 | 17 | |
0efdf0fe | 18 | .. _ripngd-configuration: |
42fc5d26 QY |
19 | |
20 | ripngd Configuration | |
21 | ==================== | |
22 | ||
23 | Currently ripngd supports the following commands: | |
24 | ||
e71a9424 | 25 | .. clicmd:: router ripng [vrf NAME] |
42fc5d26 | 26 | |
c1a54c05 | 27 | Enable RIPng. |
42fc5d26 | 28 | |
c1a54c05 | 29 | .. clicmd:: network NETWORK |
42fc5d26 | 30 | |
c1a54c05 | 31 | Set RIPng enabled interface by NETWORK. |
42fc5d26 | 32 | |
c1a54c05 | 33 | .. clicmd:: network IFNAME |
42fc5d26 | 34 | |
c1a54c05 | 35 | Set RIPng enabled interface by IFNAME. |
42fc5d26 | 36 | |
c1a54c05 | 37 | .. clicmd:: route NETWORK |
42fc5d26 | 38 | |
c1a54c05 | 39 | Set RIPng static routing announcement of NETWORK. |
42fc5d26 | 40 | |
42fc5d26 | 41 | |
0efdf0fe | 42 | .. _ripngd-terminal-mode-commands: |
42fc5d26 QY |
43 | |
44 | ripngd Terminal Mode Commands | |
45 | ============================= | |
46 | ||
e71a9424 | 47 | .. clicmd:: show ipv6 ripng [vrf NAME] status |
42fc5d26 | 48 | |
c1a54c05 | 49 | .. clicmd:: show debugging ripng |
42fc5d26 | 50 | |
c1a54c05 | 51 | .. clicmd:: debug ripng events |
42fc5d26 | 52 | |
c1a54c05 | 53 | .. clicmd:: debug ripng packet |
42fc5d26 | 54 | |
c1a54c05 | 55 | .. clicmd:: debug ripng zebra |
42fc5d26 | 56 | |
42fc5d26 QY |
57 | |
58 | ripngd Filtering Commands | |
59 | ========================= | |
60 | ||
8a7be4dd | 61 | RIPng routes can be filtered by a distribute-list. |
42fc5d26 | 62 | |
8a7be4dd | 63 | .. clicmd:: distribute-list [prefix] LIST <in|out> IFNAME |
a8c90e15 | 64 | |
8a7be4dd DS |
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. | |
42fc5d26 | 89 | |
b832909b QY |
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 |