网络分析专家论坛 netexpert's Archiver

aizibin 发表于 2006-12-12 10:16

问有经验滴老鸟(开迅雷ping路由掉包)

大家好，这个本人的第一贴，有个问题想问大家，也不知道发的地方对不对。
[color=magenta]网络环境：[/color]
6人共享2M带宽，4口路由器拖3台PC+1交换机（+3台PC）
不知道上面的结构大家看懂了没有。:loveliness:

[color=red]问题是[/color]当LAN内有人用迅雷DOWNLOAD的时候，ping 路由器就会非常慢。
可是按道理来说，开迅雷的时候应该是ping外网慢，而ping内网正常啊！
希望各位高手给分析一下。
下面是ping的数据，上半部分是其他PC开迅雷DOWN的时候的数据，下半部分是迅雷关闭后的数据。

[color=red]C:\Documents and Settings\Administrator>ping 192.168.0.1 -t[/color]
[color=red]Pinging 192.168.0.1 with 32 bytes of data:[/color]
[color=red]Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=991ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=12ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=13ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=7ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.0.1: bytes=32 time=986ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=865ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1038ms TTL=255
Reply from 192.168.0.1: bytes=32 time=2103ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1835ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1746ms TTL=255
Request timed out.
Reply from 192.168.0.1: bytes=32 time=936ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=796ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1049ms TTL=255
Reply from 192.168.0.1: bytes=32 time=2109ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1999ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1774ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1612ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1411ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1051ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1984ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=719ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1033ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1747ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1126ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1065ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1747ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1170ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1035ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1970ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1851ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1036ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1066ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1718ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1302ms TTL=255
Reply from 192.168.0.1: bytes=32 time=947ms TTL=255
Request timed out.
Reply from 192.168.0.1: bytes=32 time=776ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1037ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=782ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1099ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1881ms TTL=255
Request timed out.
Reply from 192.168.0.1: bytes=32 time=936ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=773ms TTL=255
Request timed out.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255[/color]
[color=red]Ping statistics for 192.168.0.1:
    Packets: Sent = 158, Received = 124, Lost = 34 (21% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 2109ms, Average = 412ms
Control-C
^C
C:\Documents and Settings\Administrator>
[/color]

jingshne 发表于 2006-12-12 10:21

路由器性能太差,换一个好点的~

aizibin 发表于 2006-12-12 10:25

但是以前没有这种情况出现啊。
是最近才有的。
请问还可能有其他的原因吗？

jingshne 发表于 2006-12-12 10:32

那是路由器老化了,还是建意先换一个试试~~

aizibin 发表于 2006-12-12 10:34

:funk:
才用了半年的。
我看也只有换新的看看了。
郁闷ing
另外谢谢老大了。

yujingjing 发表于 2006-12-12 11:43

可能是这样的!!

迅雷下载有以下特点,并发连接数多,下载的同时要上传.
所以1.对路由器的性能要求高:路由器要做转发,还要做NAT所以性能不好的路由器响应时间会加大或丢包.
      2.你们可能是使HUB,所以共享式构中当数据流量过大时,也会出现掉包!

chenshowq 发表于 2006-12-12 20:08

换个性能好点的路由器,使用迅雷的话会占用所有的线程数,如果设备性能差,带宽少的话,容易造成网络掉包情况!!

rixtdm 发表于 2006-12-14 14:43

是网络出口的问题吧，看看交换机和路由器的端口模式是否匹配，还有路由器的CPU利用率为多少。一般掉包都是端口模式不匹配或CPU利用率过高引起的！

页: [1]

Powered by Discuz! Archiver 6.1.0  © 2001-2007 Comsenz Inc.