DigiTurk (7Е)
#22
Отправлено 28 November 2012 - 23:30
#23
Отправлено 28 November 2012 - 23:32
в сл.раз за кодом прячьте лог
мы просили только на дигитурк,а не на многое другое
проверим пакет
спасибо за инфо.
я только смотрел дигитурк когдя снял лог.
если не трудно укажите как снят пинг
спасибо заранее
#24
Отправлено 28 November 2012 - 23:33
пинг к серверу без потерь? другие пакеты работают без проблем?
а как пинговать?
да другие пакеты работают без проблем
#26
Отправлено 28 November 2012 - 23:56
в командной стоке наберите
ping 89.149.254.97 -n 100
не идет пинг
[root@stlinux]#ping 89.149.254.97 n 100[J
-n 100[5D
n 100
ping: invalid option -- n
BusyBox v1.18.2 (2011-07-13 20:52:52 CST) multi-call binary.
Usage: ping [OPTIONS] HOST
Send ICMP ECHO_REQUEST packets to network hosts
Options:
-4,-6 Force IP or IPv6 name resolution
-c CNT Send only CNT pings
-s SIZE Send SIZE data bytes in packets (default:56)
-I IFACE/IP Use interface or IP address as source
-W SEC Seconds to wait for the first response (default:10)
(after all -c CNT packets are sent)
-w SEC Seconds until ping exits (default:infinite)
(can exit earlier with -c CNT)
-q Quiet, only displays output at start
and when finished
[root@stlinux]#
#27
Отправлено 29 November 2012 - 00:04
Сообщение отредактировал sniper: 29 November 2012 - 00:06
#28
Отправлено 29 November 2012 - 00:09
ping 89.149.254.97 -t
остановка- Ctrl+C
тоже самое. На DCC не идет пинг а через cmd пингуется
проверил на DCC пинг для cserv15.net. Пинг идет
вот результат от cmd
C:\Users\Nicat>ping 89.149.254.97 -t
Pinging 89.149.254.97 with 32 bytes of data:
Reply from 89.149.254.97: bytes=32 time=570ms TTL=52
Reply from 89.149.254.97: bytes=32 time=685ms TTL=52
Reply from 89.149.254.97: bytes=32 time=401ms TTL=52
Reply from 89.149.254.97: bytes=32 time=556ms TTL=52
Reply from 89.149.254.97: bytes=32 time=515ms TTL=52
Ping statistics for 89.149.254.97:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 401ms, Maximum = 685ms, Average = 545ms
Control-C
^C
C:\Users\Nicat>
Сообщение отредактировал mnijat: 29 November 2012 - 00:13
#29
Отправлено 29 November 2012 - 00:13
#30
Отправлено 29 November 2012 - 00:18
пингуйте с командной строки через cmd
C:\Users\Nicat>ping 89.149.254.97 -n 100
Pinging 89.149.254.97 with 32 bytes of data:
Reply from 89.149.254.97: bytes=32 time=217ms TTL=52
Reply from 89.149.254.97: bytes=32 time=212ms TTL=52
Reply from 89.149.254.97: bytes=32 time=227ms TTL=52
Reply from 89.149.254.97: bytes=32 time=202ms TTL=52
Reply from 89.149.254.97: bytes=32 time=237ms TTL=52
Reply from 89.149.254.97: bytes=32 time=231ms TTL=52
Reply from 89.149.254.97: bytes=32 time=237ms TTL=52
Reply from 89.149.254.97: bytes=32 time=220ms TTL=52
Reply from 89.149.254.97: bytes=32 time=267ms TTL=52
Reply from 89.149.254.97: bytes=32 time=210ms TTL=52
Reply from 89.149.254.97: bytes=32 time=285ms TTL=52
Reply from 89.149.254.97: bytes=32 time=200ms TTL=52
Reply from 89.149.254.97: bytes=32 time=235ms TTL=52
Reply from 89.149.254.97: bytes=32 time=230ms TTL=52
Reply from 89.149.254.97: bytes=32 time=236ms TTL=52
Reply from 89.149.254.97: bytes=32 time=219ms TTL=52
Reply from 89.149.254.97: bytes=32 time=214ms TTL=52
Reply from 89.149.254.97: bytes=32 time=209ms TTL=52
Reply from 89.149.254.97: bytes=32 time=204ms TTL=52
Reply from 89.149.254.97: bytes=32 time=199ms TTL=52
Reply from 89.149.254.97: bytes=32 time=246ms TTL=52
Ping statistics for 89.149.254.97:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 199ms, Maximum = 285ms, Average = 225ms
Control-C
^C
C:\Users\Nicat>
#31
Отправлено 29 November 2012 - 00:38
#32
Отправлено 29 November 2012 - 00:41
при проблемах пингуйте во время затыков, пинг весь копировать не надо, только статистику. пакет проверяют
ниже статистика во время затыков
Ping statistics for 89.149.254.97:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 225ms, Maximum = 259ms, Average = 241ms
#33
Отправлено 29 November 2012 - 00:47
#34
Отправлено 29 November 2012 - 00:52
4 пакета-4 секунды. смена ключа- 10 сек. пинг 4/10 смены ключа никакой информации кроме доступности сервера не дает
так проблема у меня или у вас? можно ли решить эту проблему?
#35
Отправлено 29 November 2012 - 00:53
4.8е, 13.е, 19е, 36.е, 75е, 0.8w, 4w, 5w
#36
Отправлено 29 November 2012 - 01:04
пинг побольше покажите
этого достаточно?
Ping statistics for 89.149.254.97:
Packets: Sent = 100, Received = 100, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 726ms, Average = 258ms
#37
Отправлено 29 November 2012 - 02:10
свежий лог покажите нам с пакета
Ситуация тоже самая .. Ничего не поменялось ..
tuxbox mgcamd v1.33 by mixvt (compiled May 31 2009 19:41:08) [mg] Net:1:3:2:2s Show ecm:0, emm:0 Up:0 Au:0 Dir:0 Osd:no:80:0 Cache:0 Log:7:192.168.1.4:514 Reread:0 [mg] Ecm cache time: 15 Box type: dbox2 Conax.Key error 2: No such file or directory Keys readed Conax.Key error 2: No such file or directory [config] newcamd route = username:servak-16:3022 newcamd keep alive: 0, incoming port: 0 [mgcamd] tps update started. [mgcam] emm thread started /var/keys/tps.bin error 2: No such file or directory [newcamd] Connecting to servak-16:3022... [newcamd] Login to servak-16:3022 as username accepted (88ms) got 62 cmd 9F [mg0] namespace 460000 t-id C738 on-id 7E [mg0] descramble on 1, source 0 [mg0] service 1C85 index 0 pmt pid 1F5 (1), pids: video 0x0884, audio 0x0C6C [mg0] ECM: CaID: 0x0D00 -> CaPID: 0x184C ProvID: 000000 [mg0] ECM: CaID: 0x0664 -> CaPID: 0x1C34 ProvID: 000000 [newcamd] Card data from servak-16:3022 (165ms): Userid 24 caid D00 providers 2 Idents: 000000 0000C0 [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (214ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (287ms) [mg0] WARNING, both cws changed ! [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (293ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (282ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (305ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (308ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (282ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (277ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (275ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (370ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (499ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (287ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (271ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (294ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (272ms) [mg0] -> ECM to newcamd servak-16:3022 [mg0] <- CW from newcamd servak-16:3022 (277ms)
#39
Отправлено 29 November 2012 - 13:11
этого достаточно?
Ping statistics for 89.149.254.97:
Packets: Sent = 100, received = 100, lost = 0 (0% l
approximate round trip times in milli-seconds:
Minimum = 173ms, maximum = 726ms, average = 258ms
добрый день уважаемые админы
есть какие то новости?
заранее спасибо
#40
Отправлено 30 November 2012 - 12:39
можно узнать ориентировочную срок исправление данной проблемы?
Количество пользователей, читающих эту тему: 0
0 пользователей, 0 гостей, 0 анонимных