Помогите с настройкой роутера

Тема в разделе "Чёрная дыра", создана пользователем Disolate, 6 сен 2013.

  1. Disolate

    Disolate Новичок

    Суть в чем: Запускаю игру выбираю героя все грузится норм пинг 29-50. Потом спустя секунд 30 (примерно во время запуска крипов) пинг поднимается до 500 и пишет отсутствие ответа сервера. И так каждый раз (в доте 2, лоле, даже айсикап).
    Интернет билайн безлимитный: (роутер кинетик гига)
    Результаты проверки http://www.speedtest.net/ и Natalyzr (http://www.ismyportblocked.com/?pc=lol показывает что все нормально)
    ping 3 ms
    download speed: 44.63 mbps
    upload speed 25.13 mbps


    Потом проверил порты Natalyzr
    Summary of Noteworthy Events
    + [​IMG]
    Minor Aberrations
    Address-based Tests
    + [​IMG]
    NAT detection (?): NAT Detected
    +
    Local Network Interfaces (?): OK
    +
    DNS-based host information (?): OK
    +
    NAT support for Universal Plug and Play (UPnP) (?): Not found
    +
    Reachability Tests
    + [​IMG]
    TCP connectivity (?): Note
    Direct TCP access to remote FTP servers (port 21) is allowed.
    Direct TCP access to remote SSH servers (port 22) is allowed.
    Direct TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.
    This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system. This is probably a countermeasure against malware abusing infected machines for generating spam. You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.
    The client received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
    Direct TCP access to remote DNS servers (port 53) is allowed.
    Direct TCP access to remote HTTP servers (port 80) is allowed.
    Direct TCP access to remote POP3 servers (port 110) is allowed.
    Direct TCP access to remote RPC servers (port 135) is allowed.
    Direct TCP access to remote NetBIOS servers (port 139) is allowed.
    Direct TCP access to remote IMAP servers (port 143) is allowed.
    Direct TCP access to remote SNMP servers (port 161) is allowed.
    Direct TCP access to remote HTTPS servers (port 443) is allowed.
    Direct TCP access to remote SMB servers (port 445) is allowed.
    Direct TCP connections to remote SMTP/SSL servers (port 465) succeed, but do not receive the expected content.
    The client received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
    Direct TCP access to remote secure IMAP servers (port 585) is allowed.
    Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
    Direct TCP connections to remote IMAP/SSL servers (port 993) succeed, but do not receive the expected content.
    The client received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
    Direct TCP connections to remote POP/SSL servers (port 995) succeed, but do not receive the expected content.
    The client received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
    Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
    Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
    Direct TCP access to remote SIP servers (port 5060) is allowed.
    Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
    Direct TCP access to remote TOR servers (port 9001) is allowed.
    UDP connectivity (?): OK
    +
    Traceroute (?): OK
    +
    Path MTU (?): OK
    +
    Hidden Proxy Detection (?): Warning
    Netalyzr detected the following proxies:
    • Port: 25 , Response Time: 3 ms
    • Port: 110 (POP3), Response Time: 3 ms
    • Port: 143 (IMAP), Response Time: 3 ms
    • Port: 465 (SMTP/SSL), Response Time: 3 ms
    • Port: 587 (Authenticated SMTP), Response Time: 3 ms
    • Port: 993 (IMAP/SSL), Response Time: 3 ms
    • Port: 995 (POP/SSL), Response Time: 4 ms
    Network Access Link Properties
    + [​IMG]
    Network performance (?): Latency: 130 ms, Loss: 0.0%
    +
    TCP connection setup latency (?): 110ms
    +
    Background measurement of network health (?): no transient outages
    +
    Network bandwidth (?): Note
    None of the bandwidth measurement packets sent between the server and client arrived at the client, which prevented us from measuring the available bandwidth. One possible reason for this is dynamic filtering by access gateway devices. Another possibility is simply a transient error.
    Network buffer measurements (?): Uplink is good, Downlink is good
    +
    HTTP Tests
    + [​IMG]
    Address-based HTTP proxy detection (?): OK
    +
    Content-based HTTP proxy detection (?): OK
    +
    HTTP proxy detection via malformed requests (?): OK
    +
    Filetype-based filtering (?): OK
    +
    HTTP caching behavior (?): OK
    +
    JavaScript-based tests (?): OK
    +
    DNS Tests
    + [​IMG]
    Restricted domain DNS lookup (?): OK
    +
    Unrestricted domain DNS lookup (?): OK
    +
    DNS resolver address (?): OK
    +
    DNS resolver properties (?): Lookup latency 210 ms
    +
    Direct probing of DNS resolvers (?)
    Your system is configured to use 1 DNS resolver(s).
    The resolver at 192.168.1.1 (hdns-be2) could not process the following tested types:
    • Medium (~1300B) TXT records
    • Large (~3000B) TXT records
    Requests from this resolver come from 85.21.192.4. This resolver requries 211 ms to fetch a result from our server and 188 ms to return a result from its cache. It does not validate DNSSEC. It does not provide requested DNSSEC records. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
    DNS glue policy (?): OK
    +
    DNS resolver port randomization (?): OK
    +
    DNS lookups of popular domains (?): OK
    +
    DNS external proxy (?): OK
    +
    DNS results wildcarding (?): OK
    +
    DNS-level redirection of specific sites (?): OK
    +
    Direct probing of DNS roots (?): OK
    +
    IPv6 Tests
    + [​IMG]
    DNS support for IPv6 (?): OK
    +
    IPv4, IPv6, and your web browser (?): No IPv6 support
    +
    IPv6 connectivity (?): No IPv6 support
    +
    Network Security Protocols
    + [​IMG]
    DNSSEC Support from the DNS Roots (?): OK
    +
    Host Properties
    + [​IMG]
    System clock accuracy (?): OK
    +
    Browser properties (?): OK
    +
    Uploaded data (?): OK



    +
    Подскажите что делать​
     
  2. Asprika

    Asprika Фаворит форума

    В тех поддержку то не обратиться :(