RIP
RIP tests route exchange in simple IPv4 networks and in testbeds that verify whether a DUT correctly accepts, propagates, or filters RIP advertisements. In Peresvet ST, RIP is a separate instance bound to a Control Plane network interface.
Table 203 — RIP Parameters
| Name | Description | Value |
|---|---|---|
| Instance ID | RIP instance identifier | Specify the number that will be selected in the interface settings |
| Update interval | Routing-update interval | 30 seconds by default |
| Timeout interval | Time without updates before a route becomes unavailable | 180 seconds by default |
| GC interval | Time an invalid route is retained before removal | 120 seconds by default |
| Split horizon | Prevent advertising a route back through the interface on which it was learned | Leave enabled for standard scenarios |
| Poison reverse | Advertise a reverse route with an unreachable metric | Enable to test poison-reverse handling |
| Default metric | Default metric for added routes | 1 by default |
| Authentication | RIP authentication type | none or the mode used on the testbed |
| Auth key | Authentication key | Set when authentication is enabled |
| Teardown time | Graceful RIP teardown time after the task stops | 0 means no additional delay |
| Routes | Advertised routes | Add the prefix, metric, and next hop for each route |
The route list specifies the prefix, metric, and next hop. Add multiple entries to test how a router reacts to a set of client or service networks. To test resiliency, run tasks with different route sets and compare how quickly the DUT updates its routing table.