Дорогие пользователи! У нас появился новый форум на платформе tp-link.community (Сообщество)

Форум доступен по ссылке https://community.tp-link.com/ru

Если при регистрации в Сообществе Вы укажете адрес электронный почты, который используете на данном форуме, то Ваши данные будут перенесены на форум Сообщества автоматически.
Также, если на форуме Сообщества Ваш никнейм будет занят, то Вам предложат сменить его или оставить, но с приставкой "_RU".

Подробнее Вы можете прочитать тут: https://community.tp-link.com/ru/home/f ... pic/501542

Убедительная просьба не дублировать темы на старом/новом форуме.

LTE модем от ВайнахТелеком(ВТК) + TL-MR3220

Правила форума
Внимание!
Данные прошивки являются тестовыми, поэтому мы не можем гарантировать стабильную работу вашего устройства с данными прошивками.
Установка BETA прошивки НЕ лишает ваше устройство гарантии.
В процессе эксплуатации данных прошивок могут быть выявлены недоработки, которые позже будут устранены в официальных прошивках, выложенных на сайте.
Устанавливая данные версии прошивок, вы действуете на свой страх и риск


Правила форума TP-LINK lll ЧАВО lll Первичная настройка WAN роутера lll Настройка под провайдеров lll Официальные прошивки и драйверы
Ответить
magdenbt
Сообщения: 3
Зарегистрирован: 10 янв 2014, 15:35
Страна: Россия

LTE модем от ВайнахТелеком(ВТК) + TL-MR3220

Сообщение magdenbt » 10 янв 2014, 17:16

Добый день! У ВТК модемы 4G Quanta 1K3 с TL-MR3220 V2 на прошивке 3.17.1 Build 130716 Rel.70608n. В настройках модем нужно выбрать для YOTA.Я не смог найти ее тут на сайте. Где ее можно скачать? В добавок очень нестабильный интернет - то просто летает(30МБ), а через 5-10 мин работает хуже EDGE. В чем может быть проблема?

magdenbt
Сообщения: 3
Зарегистрирован: 10 янв 2014, 15:35
Страна: Россия

Re: LTE модем от ВайнахТелеком(ВТК) + TL-MR3220

Сообщение magdenbt » 10 янв 2014, 17:18

Выкладываю сам лог
####################################################################
# TL-MR3220 System Log
# Time = 2014-01-10 21:16:37 1140s
# H-Ver = MR3220 v2 00000000 : S-Ver = 3.17.1 Build 130716 Rel.70608n
# L = 192.168.1.1 : M = 255.255.255.0
# 3G : 3G = 10.100.104.114 : M = 255.255.255.252 : G = 10.100.104.114
####################################################################

Jan 10 20:57:45 OTHER INFO System started
Jan 10 20:57:55 DHCP NOTICE DHCP server started
Jan 10 20:57:55 SECURITY INFO PPTP Passthrough enabled
Jan 10 20:57:55 SECURITY INFO L2TP Passthrough enabled
Jan 10 20:57:55 SECURITY INFO IPSEC Passthrough enabled
Jan 10 20:57:55 SECURITY INFO FTP ALG enabled
Jan 10 20:57:55 SECURITY INFO TFTP ALG enabled
Jan 10 20:57:55 SECURITY INFO H323 ALG enabled
Jan 10 20:57:55 SECURITY INFO RTSP ALG enabled
Jan 10 20:58:08 3G/4G NOTICE handle_card start
Jan 10 20:58:08 3G/4G INFO LTE MODEM = 0, status = 1, targetVendorID = 0x0, targetProductID = 0x0
Jan 10 20:58:14 3G/4G INFO Before Mode switch VendorID = 0x0408, ProductID = 0xea25
Jan 10 20:58:14 3G/4G DEBUG =>
Jan 10 20:58:14 3G/4G DEBUG =>T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
Jan 10 20:58:14 3G/4G DEBUG =>B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
Jan 10 20:58:14 3G/4G DEBUG =>D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
Jan 10 20:58:14 3G/4G DEBUG =>P: Vendor=1d6b ProdID=0002 Rev= 2.06
Jan 10 20:58:14 3G/4G DEBUG =>S: Manufacturer=Linux 2.6.31--LSDK-9.2.0.312 ehci_hcd
Jan 10 20:58:14 3G/4G DEBUG =>S: Product=ATH EHCI
Jan 10 20:58:14 3G/4G DEBUG =>S: SerialNumber=platform
Jan 10 20:58:14 3G/4G DEBUG =>C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
Jan 10 20:58:14 3G/4G DEBUG =>I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
Jan 10 20:58:14 3G/4G DEBUG =>E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
Jan 10 20:58:14 3G/4G DEBUG =>
Jan 10 20:58:14 3G/4G DEBUG =>T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
Jan 10 20:58:14 3G/4G DEBUG =>D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
Jan 10 20:58:14 3G/4G DEBUG =>P: Vendor=0408 ProdID=ea25 Rev= 0.00
Jan 10 20:58:14 3G/4G DEBUG =>S: Manufacturer=Qualcomm, Incorporated
Jan 10 20:58:14 3G/4G DEBUG =>S: Product=Qualcomm CDMA Technologies MSM
Jan 10 20:58:14 3G/4G DEBUG =>S: SerialNumber=357264040332604
Jan 10 20:58:14 3G/4G DEBUG =>C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=500mA
Jan 10 20:58:14 3G/4G DEBUG =>I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
Jan 10 20:58:14 3G/4G DEBUG =>E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Jan 10 20:58:14 3G/4G DEBUG =>E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Jan 10 20:58:14 3G/4G INFO This is a LTE modem which needs mode switch.
Jan 10 20:58:14 3G/4G INFO Memory command is matched.
Jan 10 20:58:19 DHCP NOTICE DHCPS:Recv REQUEST from 00:37:6D:EF:7A:69
Jan 10 20:58:20 DHCP NOTICE DHCPS:Send ACK to 192.168.1.101
Jan 10 20:58:26 3G/4G DEBUG 537: Found modem type:
Jan 10 20:58:26 3G/4G DEBUG go to lte_modem_switched
Jan 10 20:58:27 3G/4G NOTICE after switch modem vid is 0x0408 pid is 0xea26
Jan 10 20:58:27 3G/4G DEBUG card_add 877 minfo.modeswitchcmd = /tmp/3G/0408_f003_0 minfo.simLock = 16, minfo.modemChipTyp = 0
Jan 10 20:58:27 3G/4G DEBUG 883: Before judgeModemTypeByTargetID index = 9, targetPid = 0xea26
Jan 10 20:58:27 3G/4G DEBUG 3GEther is 0
Jan 10 20:58:27 3G/4G DEBUG After judgeModemTypeByTargetID, modem type = 1
Jan 10 20:58:27 3G/4G INFO LTE MODEM = 1, status = 2, targetVendorID = 0x408, targetProductID = 0xea26
Jan 10 20:58:27 3G/4G NOTICE #### ENTER ####
Jan 10 20:58:27 3G/4G NOTICE >>>> LINKLIST_Start 199 <<<<.
Jan 10 20:58:27 3G/4G NOTICE >>>> hasNextLinkElement 215 <<<<.
Jan 10 20:58:27 3G/4G NOTICE >>>>lteDevicesList_search 166 : modemType = 1, device name = LG_VL600, vendor = 0x1004, product = 0x61aa .
Jan 10 20:58:27 3G/4G NOTICE >>>> hasNextLinkElement 215 <<<<.
Jan 10 20:58:27 3G/4G NOTICE >>>>lteDevicesList_search 166 : modemType = 1, device name = USB551L, vendor = 0x1410, product = 0xb001 .
Jan 10 20:58:27 3G/4G NOTICE >>>> hasNextLinkElement 215 <<<<.
Jan 10 20:58:27 3G/4G NOTICE >>>>lteDevicesList_search 166 : modemType = 1, device name = QmiLte, vendor = 0x 0, product = 0x 0 .
Jan 10 20:58:27 3G/4G NOTICE #### LEAVE ####
Jan 10 20:58:27 3G/4G NOTICE >>>>process_msg 301 : pLteModemDev = 1
Jan 10 20:58:28 3G/4G DEBUG =>
Jan 10 20:58:28 3G/4G DEBUG =>T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
Jan 10 20:58:28 3G/4G DEBUG =>B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0
Jan 10 20:58:28 3G/4G DEBUG =>D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
Jan 10 20:58:28 3G/4G DEBUG =>P: Vendor=1d6b ProdID=0002 Rev= 2.06
Jan 10 20:58:28 3G/4G DEBUG =>S: Manufacturer=Linux 2.6.31--LSDK-9.2.0.312 ehci_hcd
Jan 10 20:58:28 3G/4G DEBUG =>S: Product=ATH EHCI
Jan 10 20:58:28 3G/4G DEBUG =>S: SerialNumber=platform
Jan 10 20:58:28 3G/4G DEBUG =>C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
Jan 10 20:58:28 3G/4G DEBUG =>I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
Jan 10 20:58:28 3G/4G DEBUG =>
Jan 10 20:58:28 3G/4G DEBUG =>T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
Jan 10 20:58:28 3G/4G DEBUG =>D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
Jan 10 20:58:28 3G/4G DEBUG =>P: Vendor=0408 ProdID=ea26 Rev= 0.00
Jan 10 20:58:28 3G/4G DEBUG =>S: Manufacturer=Qualcomm, Incorporated
Jan 10 20:58:28 3G/4G DEBUG =>S: Product=Qualcomm CDMA Technologies MSM
Jan 10 20:58:28 3G/4G DEBUG =>S: SerialNumber=357264040332604
Jan 10 20:58:28 3G/4G DEBUG =>C:* #Ifs= 5 Cfg#= 1 Atr=c0 MxPwr=500mA
Jan 10 20:58:28 3G/4G DEBUG =>I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbserial_generic
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
Jan 10 20:58:28 3G/4G DEBUG =>I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbserial_generic
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
Jan 10 20:58:28 3G/4G DEBUG =>I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbserial_generic
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=2ms
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
Jan 10 20:58:28 3G/4G DEBUG =>I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=85(I) Atr=03(Int.) MxPS= 64 Ivl=2ms
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
Jan 10 20:58:28 3G/4G DEBUG =>I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usbserial_generic
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Jan 10 20:58:28 3G/4G DEBUG =>E: Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Jan 10 20:58:32 3G/4G DEBUG lteModemATCommandGetPinStatus 197 modem name is /dev/ttyUSB2
Jan 10 20:58:33 3G/4G DEBUG lteModemATCommandGetPinStatus 215 ret = 0, bufPinMsg = at+cpin?^M^M +CME ERROR: SIM busy^M
Jan 10 20:58:33 3G/4G DEBUG process_msg 336 minfo->simLock is 16
Jan 10 20:58:33 3G/4G INFO USB modem is ready
Jan 10 20:58:33 3G/4G DEBUG resetSimInfo 1163 simInfo.simStatus is 16
Jan 10 20:58:34 3G/4G DEBUG indexCountry is 341 indexISP is 4
Jan 10 20:58:34 3G/4G DEBUG mobileCfg->countryIndex is 341
Jan 10 20:58:34 3G/4G DEBUG mobileCfg->ISPIndex is 4
Jan 10 20:58:34 3G/4G DEBUG mobileCfg->dialNumber is
Jan 10 20:58:34 3G/4G DEBUG mobileCfg->APN is
Jan 10 20:58:34 3G/4G DEBUG mobileCfg->username is
Jan 10 20:58:34 3G/4G DEBUG mobileCfg->password is
Jan 10 20:58:34 3G/4G DEBUG set mobile config
Jan 10 20:58:35 3G/4G DEBUG mobileAutoDial 635 LTE dial automaticly
Jan 10 20:58:35 3G/4G DEBUG swLteMobileCmdReq 454 lteLinkStatus == 0
Jan 10 20:58:35 3G/4G DEBUG swLteMobileCmdReq 463 result is 0
Jan 10 20:58:35 3G/4G DEBUG swLteMobileCmdReq 504 pLteModemDev->connect()
Jan 10 20:58:35 3G/4G NOTICE 3G/4G start connecting...
Jan 10 20:58:44 3G/4G DEBUG swLteMobileCmdReq 509 call dhcpcLteModemStart
Jan 10 20:58:44 DHCP INFO dhcpc_ipc_data_rcv_router 660 : current network type = 1
Jan 10 20:58:44 DHCP NOTICE DHCPC Send DISCOVER with request ip 0 and unicast flag 0
Jan 10 20:58:44 DHCP DEBUG dhcpc_ipc_data_rcv_lte 211 lte_net_info.status = 0x1, lte_net_info.ip = 0x0, lte_net_info.mask = 0x0, lte_net_info.gw = 0x0
Jan 10 20:58:44 DHCP NOTICE DHCPC Recv OFFER from server a646871 with ip a646872
Jan 10 20:58:44 DHCP NOTICE DHCPC Send REQUEST to server a646871 with request ip a646872
Jan 10 20:58:45 DHCP NOTICE DHCPC Recv ACK from server a646871 with ip a646872 lease time 7200
Jan 10 20:58:45 DHCP NOTICE DHCPC:GET ip:a646872 mask:fffffffc gateway:a646871 dns1:5bd7dc05 dns2:5bd7dc07 static route:0
Jan 10 20:58:45 DHCP INFO dhcpc_ipc_data_rcv_router 660 : current network type = 1
Jan 10 20:58:45 DHCP DEBUG dhcpc_ipc_data_rcv_lte 211 lte_net_info.status = 0x0, lte_net_info.ip = 0xa646872, lte_net_info.mask = 0xfffffffc, lte_net_info.gw = 0xa646871
Jan 10 20:58:45 DHCP NOTICE DHCPS:Recv REQUEST from 50:EA:D6:23:F9:11
Jan 10 20:58:45 DHCP INFO Update DNS1 = 0x5bd7dc05, DNS2=0x5bd7dc07
Jan 10 20:58:46 DHCP WARNING LTE Network connected.
Jan 10 20:58:46 DHCP NOTICE DHCPS:Send ACK to 192.168.1.102
Jan 10 20:58:47 3G/4G DEBUG minfo->ISP is 0x1550004
Jan 10 20:58:47 3G/4G INFO Modem information is updated
Jan 10 20:58:55 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 20:59:16 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 20:59:37 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 20:59:56 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:00:16 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:00:37 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:00:51 DHCP NOTICE DHCPS:Recv REQUEST from 4C:21:D0:3E:80:8C
Jan 10 21:00:53 DHCP NOTICE DHCPS:Send ACK to 192.168.1.103
Jan 10 21:00:58 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:01:17 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:01:37 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:01:58 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:02:19 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:02:40 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:02:58 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:03:19 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:03:40 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:04:01 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:04:21 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:04:40 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:05:01 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:05:22 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:05:42 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:06:03 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:06:24 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:06:45 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:07:03 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:07:24 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:07:45 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:08:06 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:08:26 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:08:47 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:09:06 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:09:27 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:13:20 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:13:41 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:14:01 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:14:20 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:14:41 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:15:02 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:15:22 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:15:43 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:16:02 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12
Jan 10 21:16:23 3G/4G DEBUG name is /dev/ttyUSB0, LEN = 12

magdenbt
Сообщения: 3
Зарегистрирован: 10 янв 2014, 15:35
Страна: Россия

Re: LTE модем от ВайнахТелеком(ВТК) + TL-MR3220

Сообщение magdenbt » 10 янв 2014, 17:59

Интересно еще вот что- чтобы понять, что именно плохо работает (сеть оператора или роутер) провел эксперимент - запустил на роутере пинг яндекса(50 пакетов) и одновременно открывал яндекс в браузере. Результат- по пингу
Pinging 213.180.204.11 with 64 bytes of data:

Reply from 213.180.204.11: bytes=64 time=58 TTL=55 seq=1
Reply from 213.180.204.11: bytes=64 time=63 TTL=57 seq=2
Reply from 213.180.204.11: bytes=64 time=48 TTL=57 seq=3
Reply from 213.180.204.11: bytes=64 time=52 TTL=55 seq=4
Reply from 213.180.204.11: bytes=64 time=61 TTL=55 seq=5
Reply from 213.180.204.11: bytes=64 time=52 TTL=55 seq=6
Reply from 213.180.204.11: bytes=64 time=61 TTL=55 seq=7
Reply from 213.180.204.11: bytes=64 time=53 TTL=57 seq=8
Reply from 213.180.204.11: bytes=64 time=69 TTL=55 seq=9
Reply from 213.180.204.11: bytes=64 time=74 TTL=55 seq=10
Reply from 213.180.204.11: bytes=64 time=63 TTL=55 seq=11
Reply from 213.180.204.11: bytes=64 time=59 TTL=57 seq=12
Reply from 213.180.204.11: bytes=64 time=59 TTL=57 seq=13
Reply from 213.180.204.11: bytes=64 time=51 TTL=55 seq=14
Reply from 213.180.204.11: bytes=64 time=59 TTL=55 seq=15
Reply from 213.180.204.11: bytes=64 time=48 TTL=55 seq=16
Reply from 213.180.204.11: bytes=64 time=52 TTL=57 seq=17
Reply from 213.180.204.11: bytes=64 time=62 TTL=57 seq=18
Reply from 213.180.204.11: bytes=64 time=52 TTL=55 seq=19
Reply from 213.180.204.11: bytes=64 time=62 TTL=55 seq=20
Reply from 213.180.204.11: bytes=64 time=52 TTL=55 seq=21
Reply from 213.180.204.11: bytes=64 time=61 TTL=55 seq=22
Reply from 213.180.204.11: bytes=64 time=51 TTL=55 seq=23
Reply from 213.180.204.11: bytes=64 time=80 TTL=55 seq=24
Reply from 213.180.204.11: bytes=64 time=75 TTL=55 seq=25
Reply from 213.180.204.11: bytes=64 time=55 TTL=55 seq=26
Reply from 213.180.204.11: bytes=64 time=49 TTL=55 seq=27
Reply from 213.180.204.11: bytes=64 time=55 TTL=55 seq=28
Reply from 213.180.204.11: bytes=64 time=58 TTL=57 seq=29
Reply from 213.180.204.11: bytes=64 time=52 TTL=55 seq=30
Reply from 213.180.204.11: bytes=64 time=61 TTL=55 seq=31
Reply from 213.180.204.11: bytes=64 time=67 TTL=55 seq=32
Reply from 213.180.204.11: bytes=64 time=50 TTL=57 seq=33
Reply from 213.180.204.11: bytes=64 time=56 TTL=55 seq=34
Reply from 213.180.204.11: bytes=64 time=56 TTL=55 seq=35
Reply from 213.180.204.11: bytes=64 time=53 TTL=57 seq=36
Reply from 213.180.204.11: bytes=64 time=60 TTL=55 seq=37
Reply from 213.180.204.11: bytes=64 time=55 TTL=55 seq=38
Reply from 213.180.204.11: bytes=64 time=58 TTL=55 seq=39
Reply from 213.180.204.11: bytes=64 time=72 TTL=55 seq=40
Reply from 213.180.204.11: bytes=64 time=52 TTL=57 seq=41
Reply from 213.180.204.11: bytes=64 time=62 TTL=57 seq=42
Reply from 213.180.204.11: bytes=64 time=52 TTL=55 seq=43
Reply from 213.180.204.11: bytes=64 time=61 TTL=55 seq=44
Reply from 213.180.204.11: bytes=64 time=56 TTL=57 seq=45
Reply from 213.180.204.11: bytes=64 time=58 TTL=55 seq=46
Reply from 213.180.204.11: bytes=64 time=51 TTL=57 seq=47
Reply from 213.180.204.11: bytes=64 time=66 TTL=55 seq=48
Reply from 213.180.204.11: bytes=64 time=51 TTL=55 seq=49
Reply from 213.180.204.11: bytes=64 time=56 TTL=57 seq=50

Ping statistics for 213.180.204.11
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milliseconds:
Minimum = 48, Maximum = 80, Average = 57
, а яндекс открывается иногда очень быстро, но гораздо чаще почти открывается

Ответить

Вернуться в «TL-MR3220»