About the rip sending and receiving Mechanism

AboutRipTransmission Mechanism

The topology is as follows:

650) This. width = 650; "width =" 553 "Height =" 247 "src ="/e/u261/themes/default/images/spacer.gif "style =" Background: URL ("/e/u261/lang/ZH-CN/images/localimage.png") No-repeat center; Border: 1px solid # DDD; "alt =" spacer.gif "/>

1: the first one is Rip rt1 and rt2 respectively, and then view the route table of rt2.

In this case, the subnet mask of all networks is 24.

650) This. width = 650; "width =" 553 "Height =" 114 "src ="/e/u261/themes/default/images/spacer.gif "style =" Background: URL ("/e/u261/lang/ZH-CN/images/localimage.png") No-repeat center; Border: 1px solid # DDD; "alt =" spacer.gif "/>

We can see that there are two rip entries in the rt2 route table.

Cause: When the sender's primary network address and the sender's outbound interface address are not in the same CIDR block, it is summarized as its primary network address, that is, pC1 was originally 172.16.1.1, after the summary, the route table in rt2 is 172.16.0.0/16. summarized into Class B addresses. When the master network address is the same as the master network address of the sender, the original address is sent to rt2, that is, 172.17.1.0/24.

 

2: Change the subnet mask of G0/0/0 of rt1 to 25, and then view the route table of rt2.

650) This. width = 650; "width =" 553 "Height =" 97 "src ="/e/u261/themes/default/images/spacer.gif "style =" Background: URL ("/e/u261/lang/ZH-CN/images/localimage.png") No-repeat center; Border: 1px solid # DDD; "alt =" spacer.gif "/>

Cause: the route table shows that there is only one rip route, because when the sender's primary network address and the sender's outbound interface are in the same primary network, but the mask is different, this route is not sent by default. Therefore, only pc1.

 

3: Change the mask of the G0/0/1 interface of rt2 to 28. Then, view the route table of rt2.

650) This. width = 650; "width =" 554 "Height =" 117 "src ="/e/u261/themes/default/images/spacer.gif "style =" Background: URL ("/e/u261/lang/ZH-CN/images/localimage.png") No-repeat center; Border: 1px solid # DDD; "alt =" spacer.gif "/>

Cause: in this case, check the port number of the receiver of rt2, and the port number of the receiver of rt2 is 172.16.1.1. The port number of the receiver of rt1 is 172.16.0.0/16. 172.17.1.1 of G0/0/0 of rt1 is sent to rt2. at this time, the G0/0/1 of rt2 is sent to the receiver. the receiving port of the receiver receives messages from different network segments from the interface. However, when the received IP address ranges are the same as those of the interface, the interface mask of the receiver shall prevail, so it becomes 172.17.1.0/28.

 

4: Add 172.16.2.1 to the G0/0/3 of rt2. At this time, the rt2 route table

650) This. width = 650; "width =" 553 "Height =" 139 "src ="/e/u261/themes/default/images/spacer.gif "style =" Background: URL ("/e/u261/lang/ZH-CN/images/localimage.png") No-repeat center; Border: 1px solid # DDD; "alt =" spacer.gif "/>

Cause: When the receiver interface of rt2 is port G0/0/1 and a route entry of different network segments is received, check whether the neighbor has the same network segment, at this time, the G0/0/3 of rt2 is the same as the received network segment. At this time, this route is not received, so only the rip of 172.17.1.0 is left.

 

This article is from the "crayon shinner 1995" blog, please be sure to keep this source http://152255644.blog.51cto.com/8704796/1561863

About the rip sending and receiving Mechanism