实验 6：RIPv2 认证和触发更新
1.实验目的
通过本实验可以掌握：
（1）RIPv2 明文认证的配置和匹配原则
（2）RIPv2 MD5 认证的配置和匹配原则
（3）RIPv2 触发更新
2.拓扑结构
实验拓扑如图 1-1 所示。
3.实验步骤
（1）步骤 1：配置路由器 R1
R1(config)#key chain test //配置钥匙链
R1(config-keychain)#key 1 //配置 KEY ID
R1(config-keychain-key)#key-string cisco //配置 KEY ID 的密匙 R1(config)#interface s0/0/0
R1(config-if)#ip rip authentication mode text
//启用认证，认证模式为明文，默认认证模式就是明文，所以也可以不用指定 R1(config-if)#ip rip authentication key-chain test //在接口上调用钥匙链
R1(config-if)#ip rip triggered //在接口上启用触发更新
（2）步骤 2：配置路由器 R2
R2(config)#key chain test
R2(config-keychain)#key 1
R2(config-keychain-key)#key-string cisco
R2(config)#interface s0/0/0
R2(config-if)#ip rip triggered
R2(config-if)#ip rip authentication key-chain test
R2(config-if)#interface s0/0/1
R2(config-if)#ip rip authentication key-chain test
R2(config-if)#ip rip triggered
（3）步骤 3：配置路由器 R3
R3(config)#key chain test
R3(config-keychain)#key 1
R3(config-keychain-key)#key-string cisco
R3(config)#interface s0/0/0
R3(config-if)#ip rip authentication key-chain test
R3(config-if)#ip rip triggered
R3(config-if)#interface s0/0/1
R3(config-if)#ip rip authentication key-chain test
R3(config-if)#ip rip triggered
（4）步骤 4：配置路由器 R4
R4(config)#key chain test
R4(config-keychain)#key 1
R4(config-keychain-key)#key-string cisco
R4(config)#interface s0/0/0
R4(config-if)#ip rip authentication key-chain test
R4(config-if)#ip rip triggered
4.实验调试
（1）show ip protocols
R2#show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 4 seconds
Invalid after 180 seconds, hold down 0, flushed after 240
// 由于触发更新，hold down 计时器自动为 0
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 2 2 Yes test
Serial0/0/1 2 2 Yes test
//以上两行表明 s0/0/0 和 s0/0/1 接口启用了认证和触发更新
Automatic network summarization is not in effect Maximum
path: 4
Routing for Networks:
192.168.12.0
192.168.23.0
Routing Information Sources:
Gateway Distance Last Update
192.168.12.1 120 00:26:10
192.168.23.3 120 00:26:01
Distance: (default is 120)
（2）debug ip rip
R2#debug ip rip
RIP protocol debugging is on
R2#clear ip route *
*Feb 11 13:51:31.827: RIP: sending triggered request on Serial0/0/0 to 224.0.0.9
*Feb 11 13:51:31.831: RIP: sending triggered request on Serial0/0/1 to 224.0.0.9
*Feb 11 13:51:31.843: RIP: sending triggered request on Serial0/0/0 to 224.0.0.9
*Feb 11 13:51:31.847: RIP: sending triggered request on Serial0/0/1 to 224.0.0.9
*Feb 11 13:51:31.847: RIP: send v2 triggered flush update to 192.168.12.1 on Serial0/0/0 with no
route
*Feb 11 13:51:31.851: RIP: start retransmit timer of 192.168.12.1
*Feb 11 13:51:31.855: RIP: send v2 triggered flush update to 192.168.23.3 on Serial0/0/1 with no
route
*Feb 11 13:51:31.855: RIP: start retransmit timer of 192.168.23.3
*Feb 11 13:51:32.019: RIP: received packet with text authentication cisco
*Feb 11 13:51:32.019: RIP: received v2 triggered update from 192.168.12.1 on Serial0/0/0
*Feb 11 13:51:32.023: RIP: sending v2 ack to 192.168.12.1 via Serial0/0/0 (192.168.12.2),
flush, seq# 1
*Feb 11 13:51:32.027: 1.1.1.0/24 via 0.0.0.0 in 1 hops
*Feb 11 13:51:32.031: RIP: received packet with text authentication cisco
*Feb 11 13:51:32.035: RIP: received v2 triggered update from 192.168.23.3 on Serial0/0/1
*Feb 11 13:51:32.035: RIP: sending v2 ack to 192.168.23.3 via Serial0/0/1(192.168.23.2), flush,
seq# 2
*Feb 11 13:51:32.039: 192.168.34.0/24 via 0.0.0.0 in 1 hops
*Feb 11 13:51:32.043: 4.4.4.0/24 via 0.0.0.0 in 2 hops
*Feb 11 13:51:32.071: RIP: received packet with text authentication cisco
*Feb 11 13:51:32.071: RIP: received v2 triggered update from 192.168.23.3 on Serial0/0/1
*Feb 11 13:51:32.071: RIP: sending v2 ack to 192.168.23.3 via Serial0/0/1(192.168.23.2), flush,
seq# 3
*Feb 11 13:51:32.075: 192.168.34.0/24 via 0.0.0.0 in 1 hops
*Feb 11 13:51:32.079: 4.4.4.0/24 via 0.0.0.0 in 2 hops
*Feb 11 13:51:32.083: RIP: received packet with text authentication cisco
*Feb 11 13:51:32.083: RIP: received v2 triggered ack from 192.168.23.3 on Serial0/0/1 flush
seq# 2
*Feb 11 13:51:32.087: RIP: send v2 triggered update to 192.168.23.3 on Serial0/0/1
*Feb 11 13:51:32.087: RIP: build update entries
*Feb 11 13:51:32.091: route 176: 192.168.12.0/24 metric 1, tag 0
*Feb 11 13:51:32.091: route 181: 1.1.1.0/24 metric 2, tag 0
*Feb 11 13:51:32.095: RIP: Update contains 2 routes, start 176, end 188
*Feb 11 13:51:32.095: RIP: start retransmit timer of 192.168.23.3
*Feb 11 13:51:32.099: RIP: received packet with text authentication cisco
*Feb 11 13:51:32.099: RIP: received v2 triggered update from 192.168.12.1 on Serial0/0/0
*Feb 11 13:51:32.103: RIP: sending v2 ack to 192.168.12.1 via Serial0/0/0 (192.168.12.2),
flush, seq# 2
*Feb 11 13:51:32.107: 1.1.1.0/24 via 0.0.0.0 in 1 hops
*Feb 11 13:51:32.107: RIP: received packet with text authentication cisco
*Feb 11 13:51:32.111: RIP: received v2 triggered ack from 192.168.12.1 on Serial0/0/0 flush
seq# 3
*Feb 11 13:51:32.111: RIP: send v2 triggered update to 192.168.12.1 on Serial0/0/0
*Feb 11 13:51:32.115: RIP: build update entries
*Feb 11 13:51:32.115: route 178: 192.168.23.0/24 metric 1, tag 0
*Feb 11 13:51:32.119: route 184: 192.168.34.0/24 metric 2, tag 0
*Feb 11 13:51:32.123: route 187: 4.4.4.0/24 metric 3, tag 0
*Feb 11 13:51:32.123: RIP: Update contains 3 routes, start 178, end 188
*Feb 11 13:51:32.123: RIP: start retransmit timer of 192.168.12.1
*Feb 11 13:51:32.263: RIP: received packet with text authentication cisco
*Feb 11 13:51:32.263: RIP: received v2 triggered ack from 192.168.23.3 on Serial0/0/1 seq# 3
*Feb 11 13:51:32.267: RIP: received packet with text authentication cisco
*Feb 11 13:51:32.271: RIP: received v2 triggered ack from 192.168.12.1 on Serial0/0/0 seq# 4
从上面的输出可以看出，在路由器 R2 上，虽然我们打开了 debug ip rip，但是由于采 用触发更新，所以并没有看到每 30 秒更新一次的信息，而是清除了路由表这件事件触发了路由更新。而且所有的更新中都有“triggered”的字样，同时在接收的更新中带有“text authentication”的字样，证明接口 s0/0/0 和 s0/0/1 启用了触发更新和明文认证。
（3）show ip rip database
该命令可以查看 RIP 数据库。
R2#show ip rip database
1.0.0.0/8 auto-summary
1.1.1.0/24
[1] via 192.168.12.1, 00:12:22 (permanent), Serial0/0/0
* Triggered Routes:
- [1] via 192.168.12.1, Serial0/0/0
4.0.0.0/8 auto-summary
4.4.4.0/24
[2] via 192.168.23.3, 00:12:22 (permanent), Serial0/0/1
* Triggered Routes:
- [2] via 192.168.23.3, Serial0/0/1
192.168.12.0/24 auto-summary
192.168.12.0/24 directly connected, Serial0/0/0
192.168.23.0/24 auto-summary
192.168.23.0/24 directly connected, Serial0/0/1
192.168.34.0/24 auto-summary
192.168.34.0/24
[1] via 192.168.23.3, 00:12:22 (permanent), Serial0/0/1
* Triggered Routes:
- [1] via 192.168.23.3, Serial0/0/1
以上输出进一步说明了在 s0/0/0 和 s0/0/1 启用了触发更新。
（4）show run
R2#show run | begin router rip
router rip version 2
timers basic 30 180 0 240
//由于触发更新，在配置中自动加入上面一行，且 hold down 计时器被设置为 0 network 192.168.12.0
network 192.168.23.0 no auto-summary
关于 MD5 认证，只需要在接口下声明认证模式为 MD5 即可，例如在 R1 上的配置如下： R1(config)#key chain test //定义钥匙链
R1(config-keychain)#key 1
R1(config-keychain-key)#key-string cisco
R1(config)#interface s0/0/0
R1(config-if)#ip rip authentication mode md5 //认证模式为 MD5
R1(config-if)#ip rip authentication key-chain test
其他的配置和明文认证相同，这里不再赘述。当在 R2 上执行“debug ip rip”时显示
类似如下的信息：
*Feb 11 14:04:36.851: RIP: sending triggered request on Serial0/0/0 to 224.0.0.9
*Feb 11 14:04:36.855: RIP: sending triggered request on Serial0/0/1 to 224.0.0.9
*Feb 11 14:04:36.867: RIP: sending triggered request on Serial0/0/0 to 224.0.0.9
*Feb 11 14:04:36.871: RIP: sending triggered request on Serial0/0/1 to 224.0.0.9
*Feb 11 14:04:36.871: RIP: send v2 triggered flush update to 192.168.12.1 on Serial0/0/0 with no
route
*Feb 11 14:04:36.875: RIP: start retransmit timer of 192.168.12.1
*Feb 11 14:04:36.875: RIP: send v2 triggered flush update to 192.168.23.3 on Serial0/0/1 with no
route
*Feb 11 14:04:36.879: RIP: start retransmit timer of 192.168.23.3
*Feb 11 14:04:36.927: RIP: received packet with MD5 authentication
*Feb 11 14:04:36.931: RIP: received v2 triggered update from 192.168.23.3 on Serial0/0/1
*Feb 11 14:04:36.931: RIP: sending v2 ack to 192.168.23.3 via Serial0/0/1 (192.168.23.2),
flush, seq# 4
*Feb 11 14:04:36.935: 192.168.34.0/24 via 0.0.0.0 in 1 hops
*Feb 11 14:04:36.943: 4.4.4.0/24 via 0.0.0.0 in 2 hops
*Feb 11 14:04:36.947: RIP: received packet with MD5 authentication
*Feb 11 14:04:36.947: RIP: received v2 triggered update from 192.168.12.1 on Serial0/0/0
*Feb 11 14:04:36.951: RIP: sending v2 ack to 192.168.12.1 via Serial0/0/0 (192.168.12.2),
flush, seq# 3
*Feb 11 14:04:36.955: 1.1.1.0/24 via 0.0.0.0 in 1 hops
*Feb 11 14:04:36.959: RIP: received packet with MD5 authentication
*Feb 11 14:04:36.959: RIP: received v2 triggered update from 192.168.12.1 on Serial0/0/0
*Feb 11 14:04:36.963: RIP: sending v2 ack to 192.168.12.1 via Serial0/0/0 (192.168.12.2),
flush, seq# 4
*Feb 11 14:04:36.967: 1.1.1.0/24 via 0.0.0.0 in 1 hops
*Feb 11 14:04:36.967: RIP: received packet with MD5 authentication
*Feb 11 14:04:36.971: RIP: received v2 triggered ack from 192.168.12.1 on Serial0/0/0 flush
seq# 5
*Feb 11 14:04:36.971: RIP: send v2 triggered update to 192.168.12.1 on Serial0/0/0
*Feb 11 14:04:36.975: RIP: build update entries
*Feb 11 14:04:36.975: route 191: 192.168.23.0/24 metric 1, tag 0
*Feb 11 14:04:36.979: route 194: 192.168.34.0/24 metric 2, tag 0
*Feb 11 14:04:36.979: route 197: 4.4.4.0/24 metric 3, tag 0
*Feb 11 14:04:36.983: RIP: Update contains 3 routes, start 191, end 201
*Feb 11 14:04:36.983: RIP: start retransmit timer of 192.168.12.1
*Feb 11 14:04:36.991: RIP: received packet with MD5 authentication
*Feb 11 14:04:36.991: RIP: received v2 triggered update from 192.168.23.3 on Serial0/0/1
*Feb 11 14:04:36.991: RIP: sending v2 ack to 192.168.23.3 via Serial0/0/1 (192.168.23.2),
flush, seq# 5
*Feb 11 14:04:36.999: 192.168.34.0/24 via 0.0.0.0 in 1 hops
*Feb 11 14:04:36.999: 4.4.4.0/24 via 0.0.0.0 in 2 hops
*Feb 11 14:04:37.003: RIP: received packet with MD5 authentication
*Feb 11 14:04:37.003: RIP: received v2 triggered ack from 192.168.23.3 on Serial0/0/1
flush seq# 4
*Feb 11 14:04:37.007: RIP: send v2 triggered update to 192.168.23.3 on Serial0/0/1
*Feb 11 14:04:37.007: RIP: build update entries
*Feb 11 14:04:37.011: route 189: 192.168.12.0/24 metric 1, tag 0
*Feb 11 14:04:37.015: route 200: 1.1.1.0/24 metric 2, tag 0
*Feb 11 14:04:37.015: RIP: Update contains 2 routes, start 189, end 201
*Feb 11 14:04:37.019: RIP: start retransmit timer of 192.168.23.3
*Feb 11 14:04:37.059: RIP: received packet with MD5 authentication
*Feb 11 14:04:37.059: RIP: received v2 triggered ack from 192.168.12.1 on Serial0/0/0 seq# 6
*Feb 11 14:04:37.067: RIP: received packet with MD5 authentication
*Feb 11 14:04:37.071: RIP: received v2 triggered ack from 192.168.23.3 on Serial0/0/1
seq# 5
以上输出信息表明采用了 MD5 认证和触发更新。
【技术要点】
（1）在以太网接口下，不支持触发更新；
（2）触发更新需要协商，链路的两端都需要配置；
（3）在认证的过程中，如果定义多个 key ID，明文认证和 MD5 认证的匹配原则是不一
样的：
① 明文认证的匹配原则是：
A. 发送方发送最小Key ID的密钥 B. 不携带Key ID号码
C. 接收方会和所有 Key Chain 中的密钥匹配，如果匹配成功，则通过认证。
【实例 1】
路由器 R1 有一个 Key ID,key1=cisco；
路由器 R2 有两个 Key ID,key1=ccie，key2=cisco
根据上面的原则，R1 认证失败，R2 认证成功，所以在 RIP 中，出现单边路由并不 稀奇。
② MD5 认证的匹配原则是：
A. 发送方发送最小Key ID的密钥 B. 携带Key ID号码
C. 接收方首先会查找是否有相同的Key ID，如果有，只匹配一次，决定认证是否 成功。如果没有该Key ID，只向下查找下一跳，匹配，认证成功；不匹配，认证失败。
【实例 2】
路由器 R1 有三个 Key ID,key1=cisco，key3=ccie,key5=cisco ；
路由器 R2 有一个 Key ID,key2=cisco
根据上面的原则，R1 认证失败，R2 认证成功。
4.3.4 实验 7：浮动静态路由
1.实验目的
通过本实验可以掌握浮动静态路由原理、配置以及备份应用。
2.拓扑结构
实验拓扑如图 7-1 所示。
图7-1 浮动静态路由
3.实验步骤
本实验通过修改静态路由的管理距离为 130，使得路由器选路的时候优先选择 RIP，而
静态路由作为备份。
（1）步骤 1：配置路由器 R1
R1(config)#ip route 2.2.2.0 255.255.255.0 192.168.12.2 130
//将静态路由的管理距离设置为 130
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#no auto-summary
R1(config-router)#network 1.0.0.0
R1(config-router)#network 192.168.21.0
（2）步骤 2：配置路由器 R2
R2(config)#ip route 1.1.1.0 255.255.255.0 192.168.12.1 130
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#no auto-summary
R2(config-router)#network 192.168.21.0
R2(config-router)#network 2.0.0.0
4.实验调试
（1）在 R1 上查看路由表：
R1#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P -
periodic downloaded static route
Gateway of last resort is not set
C 192.168.12.0/24 is directly connected, Serial0/0/0
1.0.0.0/24 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Loopback0
2.0.0.0/24 is subnetted, 1 subnets
R 2.2.2.0 [120/1] via 192.168.21.2, 00:00:25, GigabitEthernet0/0
C 192.168.21.0/24 is directly connected, GigabitEthernet0/0
从以上输出可以看出，路由器将 RIP 的路由放入路由表中，因为 RIP 的管理距离为 120， 小于在静态路由中设定的 130，而静态路由处于备份的地位。
（2）在 R1 上将 g0/0 接口 shutdown，然后查看路由表： R1(config)#interface gigabitEthernet 0/0
R1(config-if)#shutdown
R1#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P -
periodic downloaded static route
Gateway of last resort is not set
C 192.168.12.0/24 is directly connected, Serial0/0/0
1.0.0.0/24 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Loopback0
2.0.0.0/24 is subnetted, 1 subnets
S 2.2.2.0 [130/0] via 192.168.12.2
以上输出说明，当主路由中断后，备份的静态路由被放入到路由表中，也很好地解释了 浮动静态路由作为备份的工作原理。
（3）在 R1 上将 g0/0 接口启动，然后查看路由表： R1(config)#interface gigabitEthernet 0/0
R1(config-if)#no shutdown
R1#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P -
periodic downloaded static route
Gateway of last resort is not set
C 192.168.12.0/24 is directly connected, Serial0/0/0
1.0.0.0/24 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Loopback0
2.0.0.0/24 is subnetted, 1 subnets
R 2.2.2.0 [120/1] via 192.168.21.2, 00:00:09, GigabitEthernet0/0
C 192.168.21.0/24 is directly connected, GigabitEthernet0/0
以上输出表明当主路由恢复后，浮动静态路由又恢复到备份的地位。
实验 8：ip default-network
1.实验目的
通过本实验可以掌握如何通过 ip default-network 向网络中注入一条默认路由。
2.拓扑结构
实验拓扑如图 8-1所示。
图 8-1 ip default-network 向 RIP 网络中注入默认路由
3.实验步骤
（1）步骤 1：配置路由器 R1
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#no auto-summary
R1(config-router)#network 192.168.12.0
R1(config)#ip default-network 1.0.0.0
（2）步骤 2：配置路由器 R2
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#no auto-summary
R2(config-router)#network 192.168.12.0
R2(config-router)#network 2.0.0.0
4.实验调试
（1）在 R2 上查看路由表：
R2#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 192.168.12.1 to network 0.0.0.0
//表明默认路由的网关为 192.168.12.1
C 192.168.12.0/24 is directly connected, Serial0/0/0
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Loopback0
R* 0.0.0.0/0 [120/1] via 192.168.12.1, 00:00:22, Serial0/0/0
从以上输出可以看出 R1 上的“ip default-network”命令确实向 RIP 网络中注入一条 “R*”的默认路由。
（2）在 R2 上 ping 1.1.1.1；
R2#ping 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/14/16 ms
以上输出表明在路由器 R2 上可以 ping 通地址 1.1.1.1，虽然在 R1 的 RIP 进程中没有 通告该网络，也恰恰说明是默认路由起了作用。否则，因为在 R2 的路由表中没有
1.1.1.0 的路由条目，是不可能 ping 通的。
【技术要点】
（1）ip default-network 后面的网络一定要是主类网络；
（2）ip default-network 后面的网络可以是直连的或者通过其它协议学到的网络。
RIP 命令汇总
下列表列出了本次学习内容涉及到的主要的命令
表4-2本章命令汇总
命令 | 作用 |
show ip route | 查看路由表 |
show ip protocols | 查看IP路由协议配置和统计信息 |
show ip ripdatabase | 查看RIP数据库 |
debug ip rip | 动态查看RIP的更新过程 |
clear ip route* | 清除路由表 |
routerrip | 启动RIP进程 |
network | 通告网络 |
version | 定义RIP的版本 |
no auto-summary | 关闭自动汇总 |
ip rip sendversion | 配置RIP发送的版本 |
ip rip receive version | 配置RIP接收的版本 |
passive-interface | 配置被动接口 |
neighbor | 配置单播更新的目标 |
ip summary-addre***ip | 配置RIP手工汇总 |
keychain | 定义钥匙链 |
keykey-id | 配置KeyID |
key-string | 配置KeyID的密匙 |
ip rip triggered | 配置触发更新 |
ip rip authenticationmode | 配置认证模式 |
ip rip authenticationkey-chain | 配置认证使用的钥匙链 |
timersbasic | 配置更新的计时器 |
maximum-paths | 配置等价路径的最大值 |
ip default-network | 向网络中注入默认路由 |
转载于:https://blog.51cto.com/455752/1438536
3984
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
