Merge pull request #11749 from ad8-bdl/patch-1

doc/user/ripd: clarify unicast behaviour
This commit is contained in:
Donald Sharp 2022-08-05 07:37:44 -04:00 committed by GitHub
commit aa9fbdf485
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -119,14 +119,14 @@ RIP Configuration
.. clicmd:: neighbor A.B.C.D .. clicmd:: neighbor A.B.C.D
Specify RIP neighbor. When a neighbor doesn't understand multicast, this Specify a RIP neighbor to send updates to. This is required when a neighbor
command is used to specify neighbors. In some cases, not all routers will be is connected via a network that does not support multicast, or when it is
able to understand multicasting, where packets are sent to a network or a desired to statically define a neighbor. RIP updates will be sent via unicast
group of addresses. In a situation where a neighbor cannot process multicast to each neighbour. Neighbour updates are in addition to any multicast updates
packets, it is necessary to establish a direct link between routers. The sent when an interface is not in passive mode (see the `passive-interface`
neighbor command allows the network administrator to specify a router as a command). RIP will continue to process updates received from both the
RIP neighbor. The `no neighbor a.b.c.d` command will disable the RIP neighbor and any received via multicast. The `no neighbor a.b.c.d` command
neighbor. will disable the RIP neighbor.
Below is very simple RIP configuration. Interface `eth0` and interface which Below is very simple RIP configuration. Interface `eth0` and interface which
address match to `10.0.0.0/8` are RIP enabled. address match to `10.0.0.0/8` are RIP enabled.