Experiment on support for Discontinuous subnets in two versions of the RIP Protocol:
The following content is taken from my new recorded video course: http://edu.51cto.com/lesson/id-22481.html (currently can watch for free), full lab demonstration, repeated verification.
1. Continuous subnet and discontinuous Subnet
We often see that r12001 does not support discontinuous subnets and only supports continuous subnets. What is a continuous subnet and what is a non-consecutive subnet?
L discontinuous subnet: in a network, several subnets consecutively divided by the same primary network are separated by subnets or networks of multiple other network segments in the middle.
[Note] If only one network is located in the middle, it is not a non-consecutive subnet. r1_1 is supported.
L continuous subnet: multiple subnets are consecutively divided by one primary network and are not separated by other networks.
2. r12001 does not support experiments with Discontinuous subnets
R12001 automatically summarizes the routes between subnets of a class network. Therefore, r12001 does not support discontinuous subnets. The topology of the experiment is as follows:
Because r12001 only advertises class network routes, two isolated continuous subnets (divided by the same master Network) route table entries that arrive at the same aggregation type (192.168.1.0/24) are generated on the same vro, but in different directions. When a host on either side sends a packet to the destination network host, the packet will be returned to the local subnet according to the aggregation route table items generated by the local subnet in the route table when the router is reached, it does not reach the host of the target network at all. Therefore, the hosts in the subnet of the same master network cannot communicate with each other.
[Note] If the following structure is used, R1 can ping R4 again, because at this time, 192.168.1.0/24 aggregation routes will not be on the same vro (R2 or R3) generate two route table entries in different directions, because the route table entry that arrives at the current region on R1 and R3 is a specific subnet directly connected route with a higher priority, not a RIP route, it will not be aggregated into 192.168.1.0/24 with class network routes.
Iii. r12002 support experiment for Discontinuous subnets
If r12002 is used, all detailed routes are displayed. The subnet does not generate (can be forced to generate) a class-type aggregation route for the same master network. Therefore, in r12002, The subnet is not consecutive, two subnet-side hosts divided by the same primary network can also communicate normally.
<Full text, detailed experiment process Please watch video> (free) http://edu.51cto.com/lesson/id-22481.html
Appendix: My online on-demand video course life-long membership card (
You can also buy a local player from me
Video file version for permanent members
):
Purchase and deliver before on January 1, July 31
Triple gift (1000 reduction, 7 books worth more than 700 yuan, and a set of books worth more than 1500 yuan), click to view: http://edu.51cto.com/member/id-9.html, can be added to my QQ detail: 462506490("Member consultation" is specified when you join)
Which of the following routing protocols can effectively support discontinuous subnets? ARIPV1 br1_2 CIGRP DEIGRP
Answer to the first question BD
AB is a universal protocol v2 that supports a variable-length subnet mask network.
CD is a Cisco dedicated protocol, and is an improved IGRP. It also supports a variable-length subnet mask network.
I chose B for 2nd questions.
The exclusion method is used.
1. the target machine can be shared only when the "file and print sharing" service is enabled.
2. Target machine: server Service. Local Machine: workstation Service. shared only when the service is enabled
3. The host name is the same as that of the network computer. access with the computer name will also affect access.
How does RIP not support continuous subnets?
Yes. You can configure the subnet address for the interface. RIP matches the received network entries Based on the Interface mask. If the interface address and the received network entry mask cannot match, at that time, the received entries were summarized as the primary network.