RIPng
RIPng provides a compact IPv6 distance-vector model. It is useful when a lab needs simple IPv6 dynamic routing without the complexity of OSPFv3 or BGP.
Support level
Section titled “Support level”| Area | Level | Notes |
|---|---|---|
| IPv6 RIP routes | Behaviour model | Computes IPv6 reachability with hop-count metrics. |
| Interface activation | Supported | RIPng is enabled on interfaces. |
| Hop-count metric | Supported | Lower metric wins; unreachable routes are suppressed. |
| Packet fidelity | Not modelled | Behaviour is solver-based. |
Standards coverage
Section titled “Standards coverage”| Standard | Coverage | Notes |
|---|---|---|
| RFC 2080 | Behaviour model | RIPng distance-vector semantics for IPv6. |
Feature matrix
Section titled “Feature matrix”| Feature | Status | Notes |
|---|---|---|
| RIPng process | Supported | Named process / interface activation where parsed. |
| Interface enable | Supported | Participating IPv6 interfaces advertise connected prefixes. |
| Route installation | Supported | Installs RIPng routes into the IPv6 RIB. |
| Authentication | Not modelled | RIPng authentication extension behaviour is out of scope. |
Vendor command matrix
Section titled “Vendor command matrix”| Command | IOS-style | Junos-style | VyOS-style | Notes |
|---|---|---|---|---|
ipv6 rip NAME enable | Supported | n/a | Partial | Interface activation. |
show ipv6 route rip | Supported | Partial | Partial | RIPng-learned routes. |
Behaviour notes
Section titled “Behaviour notes”RIPng routes are solved from the topology graph, not learned through a stream of multicast updates. This keeps training scenarios replayable.
Examples
Section titled “Examples”Canonical example
configure terminalinterface GigabitEthernet0/0 ipv6 address 2001:db8:12::1/64 ipv6 rip CORE enableendshow ipv6 route ripVendor styles
IOS-style
interface GigabitEthernet0/0 ipv6 rip CORE enableJunos-style
set protocols ripng group CORE neighbor ge-0/0/0.0VyOS-style
set protocols ripng interface eth0Known limits
Section titled “Known limits”Packet exchange fidelity, authentication extensions, and vendor timer details are not part of the current model.