RIP路由协议分析

最新推荐文章于 2024-07-11 00:33:30 发布

weixin_33774615

最新推荐文章于 2024-07-11 00:33:30 发布

阅读量222

点赞数

原文链接：http://blog.51cto.com/dnsdhcp/325018

版权

在刚启动的时候,RIP 从启用了RIP 的接口上向外广播请求信息,接下来RIP 进程进入一个循环状态:监听来自其
他路由器的请求信息和应答信息.当邻居收到请求信息以后,就发送应答信息给这个发出请求信息的路由器,这个应
答信息就包罗了它们的路由表。
RIP 定义了2 种信息类型:
Request message(请求信息)：用来向邻居请求发送一个update(更新),
Response message(应答信息)：运载着这个被请求的update.

RIPv1为有类路由，发送更新不包括掩码，通过广播255.255.255.255发送更新
RIPv2为无类路由，发送更新包括掩码，tag，通过组播224.0.0.9发送更新

为了防止更新同步,RIP 会以 15%的误差发送更新,即实际发送更新的周期的范围是

25.5-30 秒。

如下拓扑：

根据以上拓扑配置RIPv1协议：

连同后，开始试验：

分析1.RIP的工作周期 2.工作的工程

在R6上：

R6#debug ip rip

RIP protocol debugging is on

R6#

Feb 25 22:18:22.987: RIP: sending v1 update to 255.255.255.255 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:18:22.987: RIP: build update entries

Feb 25 22:18:22.987: network 192.168.2.0 metric 1

Feb 25 22:18:22.987: network 192.168.3.0 metric 2

Feb 25 22:18:23.007: RIP: sending v1 update to 255.255.255.255 via Serial1/2 (192.168.2.1)

Feb 25 22:18:23.007: RIP: build update entries

Feb 25 22:18:23.007: network 192.168.1.0 metric 1

Feb 25 22:18:29.747: RIP: ignored v1 update from bad source 192.168.3.1 on FastEthernet2/0

Feb 25 22:18:29.963: RIP: received v1 update from 192.168.2.2 on Serial1/2

Feb 25 22:18:29.963: 192.168.3.0 in 1 hops

Feb 25 22:18:29.963: RIP-DB: network_update with 192.168.3.0/24 succeeds

Feb 25 22:18:29.963: RIP-DB: adding 192.168.3.0/0 (metric 1) via 192.168.2.2 on Serial1/2 to RIP database

Feb 25 22:18:49.439: RIP: sending v1 update to 255.255.255.255 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:18:49.439: RIP: build update entries

Feb 25 22:18:49.439: network 192.168.2.0 metric 1

Feb 25 22:18:49.439: network 192.168.3.0 metric 2

Feb 25 22:18:51.159: RIP: sending v1 update to 255.255.255.255 via Serial1/2 (192.168.2.1)

Feb 25 22:18:51.159: RIP: build update entries

Feb 25 22:18:51.159: network 192.168.1.0 metric 1

Feb 25 22:18:56.631: RIP: ignored v1 update from bad source 192.168.3.1 on FastEthernet2/0

Feb 25 22:18:59.043: RIP: received v1 update from 192.168.2.2 on Serial1/2

Feb 25 22:18:59.043: 192.168.3.0 in 1 hops

Feb 25 22:18:59.043: RIP-DB: network_update with 192.168.3.0/24 succeeds

Feb 25 22:18:59.043: RIP-DB: adding 192.168.3.0/0 (metric 1) via 192.168.2.2 on Serial1/2 to RIP database

Feb 25 22:19:16.083: RIP: sending v1 update to 255.255.255.255 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:19:16.083: RIP: build update entries

Feb 25 22:19:16.083: network 192.168.2.0 metric 1

Feb 25 22:19:16.083: network 192.168.3.0 metric 2

R7:

R7#debug ip rip

RIP protocol debugging is on

R7#

Feb 25 22:18:22.463: RIP: ignored v1 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:18:22.483: RIP: received v1 update from 192.168.2.1 on Serial1/5

Feb 25 22:18:22.483: 192.168.1.0 in 1 hops

Feb 25 22:18:29.219: RIP: sending v1 update to 255.255.255.255 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:18:29.219: RIP: build update entries

Feb 25 22:18:29.219: network 192.168.1.0 metric 2

Feb 25 22:18:29.219: network 192.168.2.0 metric 1

Feb 25 22:18:29.455: RIP: sending v1 update to 255.255.255.255 via Serial1/5 (192.168.2.2)

Feb 25 22:18:29.455: RIP: build update entries

Feb 25 22:18:29.455: network 192.168.3.0 metric 1

Feb 25 22:18:48.855: RIP: ignored v1 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:18:50.559: RIP: received v1 update from 192.168.2.1 on Serial1/5

Feb 25 22:18:50.559: 192.168.1.0 in 1 hops

Feb 25 22:18:55.951: RIP: sending v1 update to 255.255.255.255 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:18:55.951: RIP: build update entries

Feb 25 22:18:55.951: network 192.168.1.0 metric 2

Feb 25 22:18:55.951: network 192.168.2.0 metric 1

Feb 25 22:18:58.351: RIP: sending v1 update to 255.255.255.255 via Serial1/5 (192.168.2.2)

Feb 25 22:18:58.351: RIP: build update entries

Feb 25 22:18:58.351: network 192.168.3.0 metric 1

Feb 25 22:19:15.315: RIP: ignored v1 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:19:19.719: RIP: received v1 update from 192.168.2.1 on Serial1/5

Feb 25 22:19:19.719: 192.168.1.0 in 1 hops

Feb 25 22:19:23.671: RIP: sending v1 update to 255.255.255.255 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:19:23.671: RIP: build update entries

Feb 25 22:19:23.671: network 192.168.1.0 metric 2

Feb 25 22:19:23.671: network 192.168.2.0 metric 1

Feb 25 22:19:27.835: RIP: sending v1 update to 255.255.255.255 via Serial1/5 (192.168.2.2)

Feb 25 22:19:27.835: RIP: build update entries

Feb 25 22:19:27.835: network 192.168.3.0 metric 1

计算机A上一直ping测试计算机B:

Reply from 192.168.3.2: bytes=32 time=177ms TTL=126

Reply from 192.168.3.2: bytes=32 time=126ms TTL=126

Reply from 192.168.3.2: bytes=32 time=171ms TTL=126

Reply from 192.168.3.2: bytes=32 time=175ms TTL=126

Reply from 192.168.3.2: bytes=32 time=159ms TTL=126

Reply from 192.168.3.2: bytes=32 time=249ms TTL=126

Reply from 192.168.3.2: bytes=32 time=233ms TTL=126

Reply from 192.168.3.2: bytes=32 time=136ms TTL=126

Reply from 192.168.3.2: bytes=32 time=185ms TTL=126

Reply from 192.168.3.2: bytes=32 time=198ms TTL=126

Reply from 192.168.3.2: bytes=32 time=120ms TTL=126

Reply from 192.168.3.2: bytes=32 time=171ms TTL=126

Reply from 192.168.3.2: bytes=32 time=138ms TTL=126

在R6上，修改协议的版本：

R6>

R6>enable

R6#config t

Enter configuration commands, one per line. End with CNTL/Z.

R6(config)#router rip

R6(config-router)#version 2

R6(config-router)#end

R6#

在R6上分析：

R6#debug ip rip

RIP protocol debugging is on

R6#

Feb 25 22:19:52.867: %SYS-5-CONFIG_I: Configured from console by console

Feb 25 22:19:56.743: RIP: ignored v1 packet from 192.168.2.2 (illegal version) ignored—被忽略 illegal：非法

Feb 25 22:20:11.223: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.1.1) 该路由RIP协议版本为2，所有接口都发

Feb 25 22:20:11.223: RIP: build update entries

Feb 25 22:20:11.223: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:20:11.223: 192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:20:20.419: RIP: sending v2 update to 224.0.0.9 via Serial1/2 (192.168.2.1)

Feb 25 22:20:20.419: RIP: build update entries

Feb 25 22:20:20.419: 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:20:22.291: RIP: ignored v1 packet from 192.168.3.1 (illegal version)

Feb 25 22:20:24.167: RIP: ignored v1 packet from 192.168.2.2 (illegal version)

Feb 25 22:20:38.207: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:20:38.207: RIP: build update entries

Feb 25 22:20:38.207: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:20:38.207: 192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:20:47.655: RIP: sending v2 update to 224.0.0.9 via Serial1/2 (192.168.2.1)

Feb 25 22:20:47.655: RIP: build update entries

Feb 25 22:20:47.655: 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:20:49.199: RIP: ignored v1 packet from 192.168.3.1 (illegal version)

Feb 25 22:20:51.895: RIP: ignored v1 packet from 192.168.2.2 (illegal version)

在R7上：

R7#debug ip rip

RIP protocol debugging is on

R7#

Feb 25 22:20:00.703: %SYS-5-CONFIG_I: Configured from console by console

Feb 25 22:20:10.043: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:20:19.187: RIP: received v2 update from 192.168.2.1 on Serial1/5

Feb 25 22:20:19.187: 192.168.1.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:20:21.039: RIP: sending v1 update to 255.255.255.255 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:20:21.039: RIP: build update entries

Feb 25 22:20:21.039: network 192.168.1.0 metric 2

Feb 25 22:20:21.039: network 192.168.2.0 metric 1

Feb 25 22:20:22.907: RIP: sending v1 update to 255.255.255.255 via Serial1/5 (192.168.2.2)

Feb 25 22:20:22.907: RIP: build update entries

Feb 25 22:20:22.907: network 192.168.3.0 metric 1

Feb 25 22:20:36.955: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:20:46.359: RIP: received v2 update from 192.168.2.1 on Serial1/5

Feb 25 22:20:46.359: 192.168.1.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:20:47.891: RIP: sending v1 update to 255.255.255.255 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:20:47.891: RIP: build update entries

Feb 25 22:20:47.891: network 192.168.1.0 metric 2

Feb 25 22:20:47.891: network 192.168.2.0 metric 1

Feb 25 22:20:50.575: RIP: sending v1 update to 255.255.255.255 via Serial1/5 (192.168.2.2)

Feb 25 22:20:50.575: RIP: build update entries

Feb 25 22:20:50.575: network 192.168.3.0 metric 1

Feb 25 22:21:06.283: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

计算机A上：

Request timed out.

Reply from 192.168.1.1: Destination host unreachable.

Request timed out.

Reply from 192.168.1.1: Destination host unreachable.

Request timed out.

Reply from 192.168.1.1: Destination host unreachable.

Request timed out.

Reply from 192.168.1.1: Destination host unreachable.

Request timed out.

Reply from 192.168.1.1: Destination host unreachable. 没有路由

Request timed out.

网络已经无法连同了。

在R7上也修改RIP版本 RIPv2

在R6上查看：

R6#

Feb 25 22:22:05.567: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:22:05.567: RIP: build update entries

Feb 25 22:22:05.567: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:22:05.567: 192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:22:10.783: RIP: sending v2 update to 224.0.0.9 via Serial1/2 (192.168.2.1)

Feb 25 22:22:10.783: RIP: build update entries

Feb 25 22:22:10.783: 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:22:12.499: RIP: ignored v2 update from bad source 192.168.3.1 on FastEthernet2/0

Feb 25 22:22:16.831: RIP: received v2 update from 192.168.2.2 on Serial1/2

Feb 25 22:22:16.831: 192.168.3.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:22:34.759: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:22:34.759: RIP: build update entries

Feb 25 22:22:34.759: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:22:34.759: 192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:22:39.467: RIP: ignored v2 update from bad source 192.168.3.1 on FastEthernet2/0

Feb 25 22:22:40.247: RIP: sending v2 update to 224.0.0.9 via Serial1/2 (192.168.2.1)

Feb 25 22:22:40.247: RIP: build update entries

Feb 25 22:22:40.247: 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:22:44.611: RIP: received v2 update from 192.168.2.2 on Serial1/2

Feb 25 22:22:44.611: 192.168.3.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:23:02.463: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:23:02.463: RIP: build update entries

Feb 25 22:23:02.463: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:02.463: 192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:23:07.435: RIP: ignored v2 update from bad source 192.168.3.1 on FastEthernet2/0

Feb 25 22:23:09.027: RIP: sending v2 update to 224.0.0.9 via Serial1/2 (192.168.2.1)

Feb 25 22:23:09.027: RIP: build update entries

Feb 25 22:23:09.027: 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:13.387: RIP: received v2 update from 192.168.2.2 on Serial1/2

Feb 25 22:23:13.387: 192.168.3.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:23:31.331: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:23:31.331: RIP: build update entries

Feb 25 22:23:31.331: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:31.331: 192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:23:34.543: RIP: ignored v2 update from bad source 192.168.3.1 on FastEthernet2/0

Feb 25 22:23:35.079: RIP: sending v2 update to 224.0.0.9 via Serial1/2 (192.168.2.1)

Feb 25 22:23:35.079: RIP: build update entries

Feb 25 22:23:35.079: 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:41.307: RIP: received v2 update from 192.168.2.2 on Serial1/2

Feb 25 22:23:41.307: 192.168.3.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:23:58.511: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:23:58.511: RIP: build update entries

Feb 25 22:23:58.511: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:58.511: 192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:24:01.523: RIP: sending v2 update to 224.0.0.9 via Serial1/2 (192.168.2.1)

Feb 25 22:24:01.523: RIP: build update entries

Feb 25 22:24:01.523: 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:24:02.079: RIP: ignored v2 update from bad source 192.168.3.1 on FastEthernet2/0

Feb 25 22:24:10.759: RIP: received v2 update from 192.168.2.2 on Serial1/2

Feb 25 22:24:10.759: 192.168.3.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:24:26.999: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.1.1)

Feb 25 22:24:26.999: RIP: build update entries

Feb 25 22:24:26.999: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:24:26.999: 192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:24:27.807: RIP: sending v2 update to 224.0.0.9 via Serial1/2 (192.168.2.1)

Feb 25 22:24:27.807: RIP: build update entries

Feb 25 22:24:27.807: 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:24:28.275: RIP: ignored v2 update from bad source 192.168.3.1 on FastEthernet2/0

Feb 25 22:24:39.647: RIP: received v2 update from 192.168.2.2 on Serial1/2

Feb 25 22:24:39.647: 192.168.3.0/24 via 0.0.0.0 in 1 hops

R6#

在R7上查看：

R7#

Feb 25 22:22:03.895: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:22:09.083: RIP: received v2 update from 192.168.2.1 on Serial1/5

Feb 25 22:22:09.083: 192.168.1.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:22:10.783: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:22:10.783: RIP: build update entries

Feb 25 22:22:10.783: 192.168.1.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:22:10.783: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:22:15.067: RIP: sending v2 update to 224.0.0.9 via Serial1/5 (192.168.2.2)

Feb 25 22:22:15.067: RIP: build update entries

Feb 25 22:22:15.067: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:22:32.975: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:22:37.651: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:22:37.651: RIP: build update entries

Feb 25 22:22:37.651: 192.168.1.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:22:37.651: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:22:38.463: RIP: received v2 update from 192.168.2.1 on Serial1/5

Feb 25 22:22:38.463: 192.168.1.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:22:42.807: RIP: sending v2 update to 224.0.0.9 via Serial1/5 (192.168.2.2)

Feb 25 22:22:42.807: RIP: build update entries

Feb 25 22:22:42.807: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:00.651: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:23:05.571: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:23:05.571: RIP: build update entries

Feb 25 22:23:05.571: 192.168.1.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:23:05.571: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:07.139: RIP: received v2 update from 192.168.2.1 on Serial1/5

Feb 25 22:23:07.139: 192.168.1.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:23:11.427: RIP: sending v2 update to 224.0.0.9 via Serial1/5 (192.168.2.2)

Feb 25 22:23:11.427: RIP: build update entries

Feb 25 22:23:11.427: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:29.307: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:23:32.483: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:23:32.483: RIP: build update entries

Feb 25 22:23:32.483: 192.168.1.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:23:32.483: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:33.027: RIP: received v2 update from 192.168.2.1 on Serial1/5

Feb 25 22:23:33.027: 192.168.1.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:23:39.155: RIP: sending v2 update to 224.0.0.9 via Serial1/5 (192.168.2.2)

Feb 25 22:23:39.155: RIP: build update entries

Feb 25 22:23:39.155: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:23:56.275: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:23:59.259: RIP: received v2 update from 192.168.2.1 on Serial1/5

Feb 25 22:23:59.259: 192.168.1.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:23:59.787: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:23:59.787: RIP: build update entries

Feb 25 22:23:59.787: 192.168.1.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:23:59.787: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:24:08.319: RIP: sending v2 update to 224.0.0.9 via Serial1/5 (192.168.2.2)

Feb 25 22:24:08.319: RIP: build update entries

Feb 25 22:24:08.319: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:24:24.599: RIP: ignored v2 update from bad source 192.168.1.1 on FastEthernet2/0

Feb 25 22:24:25.371: RIP: received v2 update from 192.168.2.1 on Serial1/5

Feb 25 22:24:25.371: 192.168.1.0/24 via 0.0.0.0 in 1 hops

Feb 25 22:24:25.819: RIP: sending v2 update to 224.0.0.9 via FastEthernet2/0 (192.168.3.1)

Feb 25 22:24:25.819: RIP: build update entries

Feb 25 22:24:25.819: 192.168.1.0/24 via 0.0.0.0, metric 2, tag 0

Feb 25 22:24:25.819: 192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

Feb 25 22:24:37.127: RIP: sending v2 update to 224.0.0.9 via Serial1/5 (192.168.2.2)

Feb 25 22:24:37.127: RIP: build update entries

Feb 25 22:24:37.127: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0

这个时候在计算机A上：

Request timed out.

Reply from 192.168.3.2: bytes=32 time=126ms TTL=126

Reply from 192.168.3.2: bytes=32 time=174ms TTL=126

Reply from 192.168.3.2: bytes=32 time=157ms TTL=126

Reply from 192.168.3.2: bytes=32 time=144ms TTL=126

Reply from 192.168.3.2: bytes=32 time=194ms TTL=126

Reply from 192.168.3.2: bytes=32 time=215ms TTL=126

Reply from 192.168.3.2: bytes=32 time=199ms TTL=126

Reply from 192.168.3.2: bytes=32 time=163ms TTL=126

在都运行V2的情况下网络继续连通。

转载于:https://blog.51cto.com/dnsdhcp/325018

weixin_33774615

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
复制链接

分享到 QQ

分享到新浪微博

扫一扫