Detailed explanation of RIP version and the difference with OSPF protocol
`
Article directory
1. RIP protocol version difference
RIPV1 | RIPV2 |
---|---|
Classful routing protocol (advertised without netmask, will be automatically summarized) | Classless routing protocol (netmask is carried when announcing, and the summarization function is automatically turned off when summarizing) |
Does not support VLSM (Variable Length Subnet Mask) | Support VLSM |
Authentication function is not supported | Support authentication function |
Broadcast Updates (255.255.255.255) | Multicast update (224.0.0.9) |
Automatic aggregation cannot be turned off | It can be automatically aggregated or manually aggregated (only one of the two aggregates can be enabled) |
No authentication function | With authentication function (MD5 and plaintext) |
Unable to mark route | Routing can be marked (flexible control of routing according to tag in routing policy) |
2. The difference between RIP and OSPF
RIP | OSPF | |
---|---|---|
name | Based on distance vector | Based on link state |
layer | transport layer | Network layer |
protocol and port number | UDP 520 | IP 89 |
working core | Number of lines (0-16/unlimited) | Computing Metrics for Links |
priority | 100 | Internal: 10' External: 150 |
to whom | Adjacent routers send | Send to all OSPF routers in the autonomous system |
send what | The exchange information is all the information currently known by this router, that is, its current routing table | Link status of all routers adjacent to this router |
when to post | Fixed time interval (30s) | Flooding occurs only when the link state changes |
scope of application | Suitable for small and medium networks, relatively simple | Suitable for larger networks |
Usage | Takes more time to reach equilibrium on the network than OSPF | The actual link bandwidth and CPU time occupied are less than RIP, and the memory is larger than RIP |
subnet mask | v1 does not support subnetting, v2 version supports subnetting | Include subnet mask in routing packet, support variable length subnetting and classless addressing CIDR |
----------------- This article is a technical question asked in the original factory interview. I hope it can be helpful to write this article. If there are other deficiencies, you can comment and supplement ------------------------