Jump to content

vasek00

Forum Members
  • Posts

    3,224
  • Joined

  • Last visited

  • Days Won

    31

Posts posted by vasek00

  1. На 4pda написали, возможно

    Цитата

    Проблема связана с багом в прошивке, который проявляется при повреждении файла в кеше сервера сборки, т.е. кинетику приходит битый ответ от сервера, и он перезагружается. (Ошибка исправлена в текущей 3.7.) На текущий момент, на сервере кеш почистили и предотвратили повторное возникновение проблемы.

    ....проблема была в кэш-сервере из-за загрузки листинга файлов на кэш-сервере прошивок.

    т.е. как я понял имеем авто обновление, так как пост который выше в моем случае оно авто обновление выключено

  2. 16 часов назад, Ole сказал:

    Схема расположения

    Мне не понятно как giga может подключаться к 3.1, вариант использовать взаимный wan не помогает, или я делаю не то...

    Я бы пошел другим путем - принципиально ли резервирование или устроит переключение в ручном варианте? PPPoE провод и он надежен и скорость выше.

    Инет1-----(WAN)Giga(LAN)----------(LAN)Viva(WAN)-ADSL------Инет2

    Для переключения Giga на канал Инет2 достаточно прописать маршрут на Giga по умолчанию default на Viva, после восстановления Инет1 вернуть обратно, ручной вариант это 1-2минуты. Ремарка - при пропадание Инет1 тут все просто, при его восстановление (нужно проверить) возможно маршрут default сменится автоматом на Инет1 функционалом прошивки Giga.

    Если нужен автомат то установить Entware на внутр.память и создать скрипт на Giga для контроля Инет1 и переключение default маршрута либо на Viva либо опять на Инет1.

    Пример

    на Giga default на pppoe, Giga 192.168.1.1 Viva 192.168.1.2
    
    default dev ppp0  scope link 
    
    
    
    смена default маршрута на шлюз в локальной сети
    
    default via 192.168.1.2 dev br0

     

  3. 1 час назад, kokos сказал:

    роутер Keenetic Extra II , что можно сделать что бы усилить сигнал ? роутер находится в комнате, и через стену на балконе бывает часто теряет связь с ноутбуком. Может подключить ретранслятор какой ни будь или роутер поменять?

    1. Как на счет других клиентов в данной точке и на какой частоте

    2. Расположение роутера (плюс/минус 1м от данной точки установки) и его антенны вертикально вверх

  4. Только что, Alexey Lyahkov сказал:

    без разницы. Не работает.

    Network::RoutingTable: renewed static route: 0.0.0.0/0 via 192.168.1.1 (Home).
    Окт 16 22:03:06 ndm
    Core::Ndss: [22013] no internet connection.
    Окт 16 22:03:27 ndm
    Core::Ndss: [22113] no internet connection.
    Окт 16 22:03:38 ndm
    Core::Ndss: [22147] no internet connection.
    Окт 16 22:03:50 ndm
    Core::Ndss: [22179] no internet connection.

     

    Там написано две команды и это работает из покон веков.

  5. Для вашего контроллера Ultra шлюзом для выхода в интернет являеться микротик, следовательно для Ultra маршрут по умолчание должен быть на микротик через интерфейс br0 по обозначению Keenetic это скорей всего у вас home. Данную команду можно ввести на Ultra только через cli, пример ниже

    ip route default 192.168.130.97 Home

    где ip адрес это шлюз микротика а Home это интерфейс через который посылать эти пакетики для микротика (он же br0)

    Страница 85 ссылки ниже последний пост

     

  6. 1 час назад, sasa2001 сказал:

    Скачал все конфиги, ни где упоминания о SkyDNS нет, буду сбрасывать до заводских настоек, хотя когда покупал, продавец уже сбросил его 

    Для начало лог после перезагрузки роутера, а сбросить  всегда можно успеть.

  7. 23 часа назад, Andrew Voronkov сказал:

    nf_conntrack: unable to save third interface 20, already has 24 and 8 (protonum 17)

    В selftet есть раздел "<file name="proc:driver/nacct/stats">" и чуток по ниже "<file name="proc:driver/hwnatacct/stats">" можно найти номера интерфейсов ifindex этот к чему у вас относиться

    • Thanks 1
  8. Скрытый текст
    access-list _WEBADMIN_Wireguard0
        permit ip 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
        permit description Warp
    
    
    interface Wireguard0
        description Cloud-warp
        security-level public
        ip address 10.10.13.10 255.255.255.0
        ip mtu 1324
        ip access-group _WEBADMIN_Wireguard0 in
        ip global 65522
        ip tcp adjust-mss pmtu
        wireguard listen-port 60100
        wireguard peer bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo= !Cloudflare-warp
            endpoint engage.cloudflareclient.com:2408
            keepalive-interval 30
            allow-ips 0.0.0.0 0.0.0.0
            allow-ips 10.10.13.0 255.255.255.0
        !
        up

     

     

  9. 5 минут назад, Sim-Sim сказал:

    Если это возможно было бы отлично добавить поддержку Cloudflare WARP client

    Так он и так работает уже давно, только генерация ключа не из WEB роутера

     

  10. 1 минуту назад, Andrew Voronkov сказал:

    Нет, у меня основное подключение - витая пара, резерв тоже витая пара, второй резерв wisp. Sfp вообще не использую. 

    Ну что ж отпадает догадка.

    • Thanks 1
  11. 3 часа назад, Legoos сказал:

     что оно криво работает с каким-то Вашим или провайдеровским оборудованием. У меня это проявляется на процессоре MT7621 со встроенным свитчём. На пике другой процессор 7622 на другом ядре и внешний свитч.

    В Peak думаю такой же свитч (10 x 1 Гбит/с: 9 x  RJ-45, 1 x SFP ) как и в KN2610 (9 x 1 Гбит/с: 8 x  RJ-45, 1 x Combo RJ-45/SFP) оличие  в подключение SFP

    Скрытый текст
    [I] Jan  1 03:00:07 kernel: mt7622_eth: NDM Ethernet Switch Driver for MediaTek MT7622, v1.1.2
    [I] Jan  1 03:00:07 kernel: mt7622_eth: MT7622 SoC, TX/RX descriptors: 2048/1024, NAPI weight 64, LRO, DMA hw-coherent
    [I] Jan  1 03:00:07 kernel: mt7622_eth: eth2 created for GMAC1 (хх:хх:хх:хх:хх:0d address, 8 EPHY ports)
    [I] Jan  1 03:00:07 kernel: mt7622_eth: eth3 created for GMAC2 (хх:хх:хх:хх:хх:0e address, 1 EPHY port)
    [I] Jan  1 03:00:07 kernel: mt7622_eth: RTL8370MB switch, ID: 6368, Ver: 0010
    [I] Jan  1 03:00:07 kernel: mt7622_eth: RTL8370MB switch configured with SGMII-2.5G
    [I] Jan  1 03:00:07 kernel: mt7622_eth: RTL8370MB switch initialized
    
    [I] Sep 25 17:24:29 ndm: Network::Interface::Mac: "GigabitEthernet0/Vlan2": MAC address reset to хх:хх:хх:хх:хх:0e.
    
    [I] Sep 25 17:24:30 ndm: Network::Interface::Mac: "GigabitEthernet1": MAC address reset to хх:хх:хх:хх:хх:0e.
    
    
    interface GigabitEthernet0/0
        rename 1
    interface GigabitEthernet0/1
        rename 2
    interface GigabitEthernet0/2
        rename 3
    interface GigabitEthernet0/4
        rename 5
    interface GigabitEthernet0/5
        rename 6
    interface GigabitEthernet0/6
        rename 7
    interface GigabitEthernet0/7
        rename 8
        switchport access vlan 1
    
    interface GigabitEthernet0/8
        rename SFP
        role inet for GigabitEthernet0/Vlan2
        switchport mode access
        switchport access vlan 2
    
    interface Bridge0
        inherit GigabitEthernet0/Vlan1
        include AccessPoint
        include AccessPoint_5G
    
    interface GigabitEthernet1
        rename ISP
        mac address factory wan

    Selftest KN2610 не видел, тут в данном случае выше SFP нет только провод на WAN подключен

    Опять же исходя только из догадок и того что выше

    Цитата

    Неожиданно пропадает интернет. Проводные клиенты пишут "без доступа к сети интернет". При переподключении появляется Неопознанная сеть. Беспроводные тоже без интернета, но при отключении-подключении они получают ip без проблем, но доступа к сети нет.
    Пинг по беспроводной сети идёт, по проводной - не находит узел. Телнет доступа нет ни в одном варианте.

    Они не совсем продолжают работать, они подключаются, получают ip, но без доступа к интернету и даже к локальной сети.

    А при наличии у меня двух резервных каналов (второй проводной и wisp)

    думаю тут основное подключение по оптике (SFP) тогда возможно бзик свитча.

    • Thanks 1
  12. 37B3 но возможно и ранее, есть ли необходимость рестарта сервиса TSMB, да интерфейсы wifi сидят в br0 и произошло изменение.

    [I] Oct  3 21:00:00 kernel: br0: port 2(ra0) entered disabled state
    [I] Oct  3 21:00:00 ndm: Network::Interface::Base: "WifiMaster0/AccessPoint0": disabled by "schedule0". 
    [I] Oct  3 21:00:02 kernel: TSMB module stopped.
    [I] Oct  3 21:00:04 kernel: TSMB module version 3020.9.24.11 started from process 15461!
    [I] Oct  3 21:00:08 ndm: Cifs::ServerTsmb: service started. 
    
    [I] Oct  4 00:00:00 ndm: Network::Interface::Base: "WifiMaster1/AccessPoint0": disabled by "schedule1". 
    [I] Oct  4 00:00:01 kernel: TSMB module stopped.
    [I] Oct  4 00:00:03 kernel: TSMB module version 3020.9.24.11 started from process 23807!
    [I] Oct  4 00:00:07 ndm: Cifs::ServerTsmb: service started. 
    
    [I] Oct  4 07:00:00 ndm: Network::Interface::Base: "WifiMaster1/AccessPoint0": enabled by "schedule1". 
    [I] Oct  4 07:00:00 kernel: br0: port 3(rai0) entered blocking state
    [I] Oct  4 07:00:00 kernel: br0: port 3(rai0) entered listening state
    [I] Oct  4 07:00:02 kernel: TSMB module stopped.
    [I] Oct  4 07:00:03 kernel: br0: port 3(rai0) entered learning state
    [I] Oct  4 07:00:04 kernel: TSMB module version 3020.9.24.11 started from process 11537!
    [I] Oct  4 07:00:06 kernel: br0: port 3(rai0) entered forwarding state
    [I] Oct  4 07:00:06 kernel: br0: topology change detected, propagating
    [I] Oct  4 07:00:08 ndm: Cifs::ServerTsmb: service started. 
    
    [I] Oct  4 08:00:00 ndm: Network::Interface::Base: "WifiMaster0/AccessPoint0": enabled by "schedule0". 
    [I] Oct  4 08:00:03 kernel: br0: port 2(ra0) entered learning state
    [I] Oct  4 08:00:03 kernel: TSMB module stopped.
    [I] Oct  4 08:00:05 kernel: TSMB module version 3020.9.24.11 started from process 14347!
    [I] Oct  4 08:00:06 kernel: br0: port 2(ra0) entered forwarding state
    [I] Oct  4 08:00:06 kernel: br0: topology change detected, propagating
    [I] Oct  4 08:00:09 ndm: Cifs::ServerTsmb: service started. 

     

  13. 39 минут назад, SySOPik сказал:

    Ну и как сказал, в идеале, видеть кроме устройств онлайн/офлайн, еще карту устройств с поднятым VPN, желательно графически как в Network Assistant Cisco, очень удобно моментально видеть отвалившийся линк IP/Sec сразу

    Так же интересно.

  14. 7 часов назад, YuriV сказал:

    @karimovrt

    Вопрос был немного в другом.

    Как мне настроить чтобы весь трафик шёл через AGH? Проброска портов, всякие тонкости вроде "dns-proxy intercept enable" и т.п.

    Я пытался сделать это по информации в этом треде, но в результате поломал всё и мне пришлось делать сброс до заводских настроек.

    Нужна инструкция по шагам, как это всё настроить на "чистой" инсталяции. 

    Про вариант настройки уже расписано несколько раз. Профиль основной.

    1. Наличие двух записей, в WEB команда с DNS 192.168.1.1 не прокатит, только cli.

    interface Bridge0
        rename Home
        description HomeLan
    
    
    
    ----------------------------------------
    ip name-server 192.168.1.1 "" on Home
    opkg dns-override

    2. AdGuardHome

    bind_host: 192.168.1.1
    bind_port: 8181
    beta_bind_port: 0
    
    dns:
      bind_hosts:
      - 127.0.0.1
      - 192.168.1.1
      port: 53
    

    3. В итоге

    / # netstat -ntulp | grep AdGuard
    tcp        0      0 192.168.1.1:8181		0.0.0.0:*               LISTEN      1116/AdGuardHome
    tcp        0      0 192.168.1.1:53		    0.0.0.0:*               LISTEN      1116/AdGuardHome
    tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1116/AdGuardHome
    udp        0      0 192.168.1.1:53          0.0.0.0:*                           1116/AdGuardHome
    udp        0      0 127.0.0.1:53            0.0.0.0:*                           1116/AdGuardHome
    / # 

    4.

    / # nslookup mail.ru
    Server:    192.168.1.1
    Address 1: 192.168.1.1
    
    Name:      mail.ru
    Address 1: 217.69.139.202 mail.ru
    Address 2: 217.69.139.200 mail.ru
    Address 3: 94.100.180.201 mail.ru
    Address 4: 94.100.180.200 mail.ru
    Address 5: 2a00:1148:db00:0:b0b0::1 mail.ru
    / # 

    5. На клиенте

    Сервер:  UnKnown
    Address:  192.168.1.1
    
    Имя:     yandex.ru
    Addresses:  213.180.193.56
    	  213.180.193.56

    6. При наличие других интерфейсов

    ip name-server 192.168.1.1 "" on OpenVPN1
    ip name-server 192.168.1.1 "" on OpenVPN2
    ip name-server 192.168.1.1 "" on GigabitEthernet0/Vlan9
    ip name-server 192.168.1.1 "" on Wireguard1
    ip name-server 192.168.1.1 "" on Wireguard0

     

    • Thanks 1
  15. 2 часа назад, Роман Сапегин сказал:

    После обновления до 3.7 Beta 3 загрузка ЦП выросла на 100%.

    Система стала заметно подвисать при обращении к системному монитору.

    Вы поставили какую то хитрую загрузку торрент качалкой что он не как ее не осилит вот уже несколько дней.

    Скрытый текст
    Скрытый текст
    [I] Sep 27 23:07:51 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 27 23:07:51 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 27 23:08:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 27 23:08:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 27 23:08:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 27 23:08:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 344 seconds.
    
    
    [I] Sep 28 00:02:10 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:02:10 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 00:02:30 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:02:30 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 327 seconds.
    [I] Sep 28 00:02:31 ndhcpc: GigabitEthernet1: received ACK for 37.145.58.164 from 78.107.125.125 lease 600 sec.
    [I] Sep 28 00:02:33 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Could not connect to tracker
    [I] Sep 28 00:02:33 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying announce in 20 seconds.
    [I] Sep 28 00:03:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:03:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 00:03:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:03:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 335 seconds.
    [I] Sep 28 00:04:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:04:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 00:05:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:05:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 330 seconds.
    [I] Sep 28 00:06:45 transmissiond: Saved "/tmp/mnt/01D6A0B3B44306D0/transmission/resume/2e2fa7c27cf660d715152571448434f085d62c64.resume"
    [I] Sep 28 00:06:45 transmissiond: Saved "/tmp/mnt/01D6A0B3B44306D0/transmission/stats.json"
    [I] Sep 28 00:06:51 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Starting IPv4 DHT announce (good, 392 nodes)
    [I] Sep 28 00:08:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:08:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 00:08:21 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:08:21 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 336 seconds.
    [I] Sep 28 00:09:01 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:09:01 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 00:09:22 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv IPv4 DHT announce done
    [I] Sep 28 00:09:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:09:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 324 seconds.
    [I] Sep 28 00:09:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Could not connect to tracker
    [I] Sep 28 00:09:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying announce in 20 seconds.
    [I] Sep 28 00:10:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:10:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 00:11:02 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:11:02 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 00:11:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 00:11:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 353 seconds.
    
    [I] Sep 28 01:14:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 01:14:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 01:14:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 01:14:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 01:14:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 01:14:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 306 seconds.
    [I] Sep 28 01:15:30 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 01:15:30 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 01:15:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 01:15:40 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 01:15:50 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 01:15:50 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 303 seconds.
    [I] Sep 28 01:16:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 01:16:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 334 seconds.
    
    [I] Sep 28 04:43:10 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 04:43:10 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 04:43:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 04:43:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 04:43:50 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 04:43:50 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 332 seconds.
    [I] Sep 28 04:46:11 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 04:46:11 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 04:46:27 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Could not connect to tracker
    [I] Sep 28 04:46:27 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying announce in 20 seconds.
    [I] Sep 28 04:46:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 04:46:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 04:46:51 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 04:46:51 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 318 seconds.
    [I] Sep 28 04:47:01 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 04:47:01 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    
    [I] Sep 28 07:33:57 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Could not connect to tracker
    [I] Sep 28 07:33:57 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying announce in 20 seconds.
    [I] Sep 28 07:35:50 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 07:35:50 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 07:36:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 07:36:00 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 07:36:10 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 07:36:10 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 308 seconds.
    [I] Sep 28 07:36:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 07:36:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 354 seconds.
    [I] Sep 28 07:36:22 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Starting IPv4 DHT announce (firewalled, 387 nodes)
    
    [I] Sep 28 11:28:30 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Pausing
    [I] Sep 28 11:28:30 transmissiond: Saved "/tmp/mnt/01D6A0B3B44306D0/transmission/resume/2e2fa7c27cf660d715152571448434f085d62c64.resume"
    [I] Sep 28 11:28:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv user not found
    [I] Sep 28 11:28:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying announce in 7205 seconds.
    [I] Sep 28 11:28:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv user not found
    [I] Sep 28 11:28:31 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying announce in 7201 seconds.
    
    [I] Sep 28 11:30:10 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 11:30:10 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 11:30:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 11:30:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 11:30:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 11:30:20 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 20 seconds.
    [I] Sep 28 11:30:30 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Scrape error: Tracker gave HTTP response code 404 (Not Found)
    [I] Sep 28 11:30:30 transmissiond: Foundation.S01E01.1080p.rus.LostFilm.TV.mkv Retrying scrape in 319 seconds.

     

     

    Скрытый текст
      PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
      823 root       20   0  4524  3056  2620 S  0.0  0.6  0:00.70 |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      849 root       20   0  4676  2508  1948 S  0.0  0.5  0:07.04 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      850 root       20   0  4676  2508  1948 S  0.0  0.5  0:07.36 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      851 root       20   0  4676  2508  1948 S  0.0  0.5  0:07.13 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      852 root       20   0  4676  2508  1948 S  0.0  0.5  0:06.95 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      853 root       20   0  4676  2508  1948 S  0.0  0.5  0:07.04 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      854 root       20   0  4676  2508  1948 S  0.0  0.5  0:07.52 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      855 root       20   0  4676  2508  1948 S  0.0  0.5  0:07.06 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      856 root       20   0  4676  2508  1948 S  0.0  0.5  0:06.85 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      857 root       20   0  4948  3072  2264 S  0.0  0.6  0:09.08 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf
      858 root       20   0  4676  2508  1948 S  0.0  0.5  0:07.12 |  |  `- /usr/sbin/lighttpd -D -f /tmp/lighttpd/lighttpd.conf    
    
    
    Pid выше от другого роутера, показывают кол-во дочерних процессов lighttpd, если некоторые в SLEEP то есть и 
    в <state>R (running)</state> у которых в вашем <cpu> = <max>23</max> и <cur>18</cur>
      
    
    <process>
            <name>lighttpd</name>
            <oom-adj>4</oom-adj>
            <oom-score>254</oom-score>
            <oom-score-adj>250</oom-score-adj>
            <arg>-D</arg>
            <arg>-f</arg>
            <arg>/tmp/lighttpd/lighttpd.conf</arg>
            <state>R (running)</state>
            <pid>8066</pid>
            <ppid>8061</ppid>
            <vm-size>4988 kB</vm-size>
            <vm-rss>2724 kB</vm-rss>
            <vm-data>900 kB</vm-data>
            <vm-stk>132 kB</vm-stk>
            <vm-exe>312 kB</vm-exe>
            <vm-lib>3632 kB</vm-lib>
            <vm-swap>0 kB</vm-swap>
            <threads>1</threads>
            <fds>7</fds>
            <statistics>
                <interval>30</interval>
                <cpu>
                    <now>150336.591234</now>
                    <min>11</min>
                    <max>22</max>
                    <avg>17</avg>
                    <cur>11</cur>
                </cpu>
            </statistics>
        </process>
        <process>
            <name>lighttpd</name>
            <oom-adj>4</oom-adj>
            <oom-score>254</oom-score>
            <oom-score-adj>250</oom-score-adj>
            <arg>-D</arg>
            <arg>-f</arg>
            <arg>/tmp/lighttpd/lighttpd.conf</arg>
            <state>R (running)</state>
            <pid>8067</pid>
            <ppid>8061</ppid>
            <vm-size>4968 kB</vm-size>
            <vm-rss>2720 kB</vm-rss>
            <vm-data>880 kB</vm-data>
            <vm-stk>132 kB</vm-stk>
            <vm-exe>312 kB</vm-exe>
            <vm-lib>3632 kB</vm-lib>
            <vm-swap>0 kB</vm-swap>
            <threads>1</threads>
            <fds>7</fds>
            <statistics>
                <interval>30</interval>
                <cpu>
                    <now>150336.591263</now>
                    <min>11</min>
                    <max>23</max>
                    <avg>16</avg>
                    <cur>18</cur>
                </cpu>
            </statistics>
        </process>
        <process>
            <name>lighttpd</name>
            <oom-adj>4</oom-adj>
            <oom-score>255</oom-score>
            <oom-score-adj>250</oom-score-adj>
            <arg>-D</arg>
            <arg>-f</arg>
            <arg>/tmp/lighttpd/lighttpd.conf</arg>
            <state>R (running)</state>
            <pid>8068</pid>
            <ppid>8061</ppid>
            <vm-size>5092 kB</vm-size>
            <vm-rss>2928 kB</vm-rss>
            <vm-data>1004 kB</vm-data>
            <vm-stk>132 kB</vm-stk>
            <vm-exe>312 kB</vm-exe>
            <vm-lib>3632 kB</vm-lib>
            <vm-swap>0 kB</vm-swap>
            <threads>1</threads>
            <fds>7</fds>
            <statistics>
                <interval>30</interval>
                <cpu>
                    <now>150336.591291</now>
                    <min>8</min>
                    <max>23</max>
                    <avg>16</avg>
                    <cur>14</cur>
                </cpu>
            </statistics>
        </process>
        <process>
            <name>lighttpd</name>
            <oom-adj>4</oom-adj>
            <oom-score>255</oom-score>
            <oom-score-adj>250</oom-score-adj>
            <arg>-D</arg>
            <arg>-f</arg>
            <arg>/tmp/lighttpd/lighttpd.conf</arg>
            <state>R (running)</state>
            <pid>8069</pid>
            <ppid>8061</ppid>
            <vm-size>4984 kB</vm-size>
            <vm-rss>2904 kB</vm-rss>
            <vm-data>896 kB</vm-data>
            <vm-stk>132 kB</vm-stk>
            <vm-exe>312 kB</vm-exe>
            <vm-lib>3632 kB</vm-lib>
            <vm-swap>0 kB</vm-swap>
            <threads>1</threads>
            <fds>7</fds>
            <statistics>
                <interval>30</interval>
                <cpu>
                    <now>150336.591321</now>
                    <min>12</min>
                    <max>23</max>
                    <avg>17</avg>
                    <cur>18</cur>
                </cpu>
            </statistics>
        </process>
        <process>
            <name>lighttpd</name>
            <oom-adj>4</oom-adj>
            <oom-score>255</oom-score>
            <oom-score-adj>250</oom-score-adj>
            <arg>-D</arg>
            <arg>-f</arg>
            <arg>/tmp/lighttpd/lighttpd.conf</arg>
            <state>R (running)</state>
            <pid>8070</pid>
            <ppid>8061</ppid>
            <vm-size>5076 kB</vm-size>
            <vm-rss>2916 kB</vm-rss>
            <vm-data>988 kB</vm-data>
            <vm-stk>132 kB</vm-stk>
            <vm-exe>312 kB</vm-exe>
            <vm-lib>3632 kB</vm-lib>
            <vm-swap>0 kB</vm-swap>
            <threads>1</threads>
            <fds>7</fds>
            <statistics>
                <interval>30</interval>
                <cpu>
                    <now>150336.591352</now>
                    <min>11</min>
                    <max>23</max>
                    <avg>16</avg>
                    <cur>18</cur>
                </cpu>
            </statistics>
        </process>
        <process>
            <name>lighttpd</name>
            <oom-adj>4</oom-adj>
            <oom-score>255</oom-score>
            <oom-score-adj>250</oom-score-adj>
            <arg>-D</arg>
            <arg>-f</arg>
            <arg>/tmp/lighttpd/lighttpd.conf</arg>
            <state>S (sleeping)</state>
            <pid>8071</pid>
            <ppid>8061</ppid>
            <vm-size>5120 kB</vm-size>
            <vm-rss>2968 kB</vm-rss>
            <vm-data>1032 kB</vm-data>
            <vm-stk>132 kB</vm-stk>
            <vm-exe>312 kB</vm-exe>
            <vm-lib>3632 kB</vm-lib>
            <vm-swap>0 kB</vm-swap>
            <threads>1</threads>
            <fds>7</fds>
            <statistics>
                <interval>30</interval>
                <cpu>
                    <now>150336.591381</now>
                    <min>0</min>
                    <max>0</max>
                    <avg>0</avg>
                    <cur>0</cur>
                </cpu>
            </statistics>
        </process>

     

     

     

  16. 11 час назад, Alex Lu сказал:

    Разобрался - теперь фалы настройки синхронизации лежат в /opt/etc/syncthing

    Но вот как подмонтировать диск с ntfs к диску с системой, что б писалось на раздел с ntfs так и не разобрался :( Если кто понимает - прошу помочь.

    Скрытый текст

    1042856129_-2.thumb.jpg.e8f4df03607be068921049ed2cec12b1.jpg

     

  17. 3 часа назад, vzaharoff сказал:

    Такая же проблема  с отваливанием началась спустя полтора года работы роутера! WI-FI вообще пропадает, подключил по кабелю, такая же песня! Уже и прошивки менял, и сбрасывал к заводским, ни чего не помогает!

    К LAN порту роутера подключен кабель от ТВ (давно это было уж несколько лет как проложен кабель). В один прекрасный день (недели 2 назад) решил посмотреть кино на ТВ и как итог нету сети, переключаю данный кабель в соседний порт роутера - работает, а если обратно в тот LAN и не работает. Думаю пипец LAN порту роутера. Повторил данную процедуру на следующий день, все повторилось.

    Решил проверить на другом кабеле, даже через "бочонки" соединил якобы с плохим портом и как не странно все заработало => меняю разъем (два раза делал замену) на плохом кабеле у роутера и ни каких проблем все работает.

    Странно конечно это но все же.

  18. 1 час назад, MDP сказал:

    Я вручную на все интерфейсы прописал, кроме портов для связи контроллера и экстендера. 

    Тут вопрос в другом - всего 4 цикла по 6 сек. и так же на 22 сек якобы не было интернета,

    12:49:11 ndm: Network::InternetChecker: Internet access lost (status: 0x0000).
    
    ....
    
    12:49:33 ndm: Network::InternetChecker: Internet access detected. 

    Сами 4 цикла

    Скрытый текст
    1 раз
    
    [I] Sep 22 12:49:05 ndm: Network::Interface::Switch: "GigabitEthernet0/1": switch link down at port 2. 
    [I] Sep 22 12:49:05 kernel: br0: port 1(eth2.1) entered blocking state
    [I] Sep 22 12:49:05 kernel: br0: port 1(eth2.1) entered listening state
    [I] Sep 22 12:49:08 ndm: Network::Interface::Switch: "GigabitEthernet0/1": switch link up at port 2 (1000FD/AN). 
    [I] Sep 22 12:49:08 kernel: br0: port 1(eth2.1) entered blocking state
    [I] Sep 22 12:49:08 kernel: br0: port 1(eth2.1) entered listening state
    [W] Sep 22 12:49:11 ndm: Dhcp::Client: DHCP server is not responding. 
    [I] Sep 22 12:49:11 ndm: Network::Interface::Ip: "Bridge0": IP address is 192.168.1.3/24. 
    [I] Sep 22 12:49:11 mtkiappd: stopped. 
    [I] Sep 22 12:49:11 kernel: br0: port 1(eth2.1) entered learning state
    [I] Sep 22 12:49:11 ndm: Network::InternetChecker: Internet access lost (status: 0x0000). 
    [I] Sep 22 12:49:12 ndm: Http::Nginx: loaded SSL certificate for "*****************813.keenetic.io". 
    [I] Sep 22 12:49:12 ndm: Http::Nginx: loaded SSL certificate for "sk*******8.keenetic.pro". 
    [I] Sep 22 12:49:12 ndm: Http::Nginx: loaded SSL certificate for MWS. 
    
    2 раз
    
    [I] Sep 22 12:49:13 mtkiappd: MediaTek IAPP daemon v2.0.5 started on br0. 
    [I] Sep 22 12:49:14 kernel: br0: port 1(eth2.1) entered forwarding state
    [I] Sep 22 12:49:14 kernel: br0: topology change detected, sending tcn bpdu
    [I] Sep 22 12:49:15 coalagent: version 0.4.32 starting. 
    [I] Sep 22 12:49:18 ndhcpc: Bridge0: received OFFER for 192.168.130.253 from 192.168.130.101. 
    [I] Sep 22 12:49:18 ndhcpc: Bridge0: received ACK for 192.168.130.253 from 192.168.130.101 lease 36600 sec. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: configuring interface Home. 
    [I] Sep 22 12:49:18 ndm: Network::Interface::Ip: "Bridge0": IP address is 192.168.130.253/24. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: obtained IP address 192.168.130.253/24. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: interface "Home" is global, priority 1. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: adding a default route via 192.168.130.101. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: adding name server 192.168.130.101. 
    [I] Sep 22 12:49:18 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
    [I] Sep 22 12:49:18 mtkiappd: stopped. 
    [I] Sep 22 12:49:19 ndm: Http::Nginx: loaded SSL certificate for "*****************813.keenetic.io".  
    [I] Sep 22 12:49:19 ndm: Http::Nginx: loaded SSL certificate for "sk*******8.keenetic.pro".
    [I] Sep 22 12:49:19 ndm: Network::Interface::Switch: "GigabitEthernet0/1": switch link down at port 2. 
    [I] Sep 22 12:49:19 ndm: Http::Nginx: loaded SSL certificate for MWS. 
    
    3 раз 
    
    [I] Sep 22 12:49:20 mtkiappd: MediaTek IAPP daemon v2.0.5 started on br0. 
    [I] Sep 22 12:49:22 ndm: Network::Interface::Switch: "GigabitEthernet0/1": switch link up at port 2 (1000FD/AN). 
    [I] Sep 22 12:49:22 kernel: br0: port 1(eth2.1) entered blocking state
    [I] Sep 22 12:49:22 kernel: br0: port 1(eth2.1) entered listening state
    [I] Sep 22 12:49:22 coalagent: version 0.4.32 starting. 
    [W] Sep 22 12:49:25 ndm: Dhcp::Client: DHCP server is not responding. 
    [I] Sep 22 12:49:25 ndm: Network::Interface::Ip: "Bridge0": IP address is 192.168.1.3/24. 
    [I] Sep 22 12:49:25 mtkiappd: stopped. 
    [I] Sep 22 12:49:25 kernel: br0: port 1(eth2.1) entered learning state
    [I] Sep 22 12:49:26 ndm: Http::Nginx: loaded SSL certificate for "*****************813.keenetic.io".  
    [I] Sep 22 12:49:26 ndm: Http::Nginx: loaded SSL certificate for "sk*******8.keenetic.pro". 
    [I] Sep 22 12:49:26 ndm: Http::Nginx: loaded SSL certificate for MWS. 
    
    4 раз 
    
    [I] Sep 22 12:49:27 mtkiappd: MediaTek IAPP daemon v2.0.5 started on br0. 
    [I] Sep 22 12:49:28 kernel: br0: port 1(eth2.1) entered forwarding state
    [I] Sep 22 12:49:28 kernel: br0: topology change detected, sending tcn bpdu
    [W] Sep 22 12:49:28 ndm: Process: "Coala Agent" has been killed. 
    [I] Sep 22 12:49:30 coalagent: version 0.4.32 starting. 
    [I] Sep 22 12:49:32 ndhcpc: Bridge0: received OFFER for 192.168.130.253 from 192.168.130.101. 
    [I] Sep 22 12:49:32 ndhcpc: Bridge0: received ACK for 192.168.130.253 from 192.168.130.101 lease 36600 sec. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: configuring interface Home. 
    [I] Sep 22 12:49:32 ndm: Network::Interface::Ip: "Bridge0": IP address is 192.168.130.253/24. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: obtained IP address 192.168.130.253/24. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: interface "Home" is global, priority 1. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: adding a default route via 192.168.130.101. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: adding name server 192.168.130.101. 
    [I] Sep 22 12:49:32 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
    [I] Sep 22 12:49:32 mtkiappd: stopped. 
    [I] Sep 22 12:49:33 ndm: Network::InternetChecker: Internet access detected. 
    [I] Sep 22 12:49:33 ndm: Http::Nginx: loaded SSL certificate for "*****************813.keenetic.io".   
    [I] Sep 22 12:49:33 ndm: Http::Nginx: loaded SSL certificate for "sk*******8.keenetic.pro".  
    [I] Sep 22 12:49:33 ndm: Http::Nginx: loaded SSL certificate for MWS. 

     

     

  19. Имеем 37B2 и схему

    Keenetic(LAN)-----(LAN)KN3010(LAN)------ПК

    Момент включения ПК

    Скрытый текст
    [I] Sep 22 12:42:51 mtkiappd: MediaTek IAPP daemon v2.0.5 started on br0. 
    [I] Sep 22 12:42:52 coalagent: version 0.4.32 starting. 
    
    В 12-46 ПК отключил и в 12-49 ПК включил, где 192...101 контроллер и он же DHCP для клиентов
    Порт 2 LAN - ПК, порт 3 LAN к контроллеру. Ретранслятору назначен IP - 192....253
    
    [I] Sep 22 12:42:53 ndm: Network::InternetChecker: Internet access detected. 
    [I] Sep 22 12:49:05 ndm: Network::Interface::Switch: "GigabitEthernet0/1": switch link down at port 2. 
    [I] Sep 22 12:49:05 kernel: br0: port 1(eth2.1) entered blocking state
    [I] Sep 22 12:49:05 kernel: br0: port 1(eth2.1) entered listening state
    [I] Sep 22 12:49:08 ndm: Network::Interface::Switch: "GigabitEthernet0/1": switch link up at port 2 (1000FD/AN). 
    [I] Sep 22 12:49:08 kernel: br0: port 1(eth2.1) entered blocking state
    [I] Sep 22 12:49:08 kernel: br0: port 1(eth2.1) entered listening state
    [W] Sep 22 12:49:11 ndm: Dhcp::Client: DHCP server is not responding. 
    [I] Sep 22 12:49:11 ndm: Network::Interface::Ip: "Bridge0": IP address is 192.168.1.3/24. 
    [I] Sep 22 12:49:11 mtkiappd: stopped. 
    [I] Sep 22 12:49:11 kernel: br0: port 1(eth2.1) entered learning state
    [I] Sep 22 12:49:11 ndm: Network::InternetChecker: Internet access lost (status: 0x0000). 
    [I] Sep 22 12:49:12 ndm: Http::Nginx: loaded SSL certificate for "*****************813.keenetic.io". 
    [I] Sep 22 12:49:12 ndm: Http::Nginx: loaded SSL certificate for "sk*******8.keenetic.pro". 
    [I] Sep 22 12:49:12 ndm: Http::Nginx: loaded SSL certificate for MWS. 
    [I] Sep 22 12:49:12 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
    [I] Sep 22 12:49:12 ndm: Core::Session: client disconnected. 
    [I] Sep 22 12:49:12 ndm: Http::Manager: updated configuration. 
    [I] Sep 22 12:49:12 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
    [I] Sep 22 12:49:12 ndm: Core::Session: client disconnected. 
    [W] Sep 22 12:49:13 ndm: Core::Server: client disconnected. 
    [I] Sep 22 12:49:13 mtkiappd: MediaTek IAPP daemon v2.0.5 started on br0. 
    [I] Sep 22 12:49:14 kernel: br0: port 1(eth2.1) entered forwarding state
    [I] Sep 22 12:49:14 kernel: br0: topology change detected, sending tcn bpdu
    [I] Sep 22 12:49:15 coalagent: version 0.4.32 starting. 
    [I] Sep 22 12:49:18 ndhcpc: Bridge0: received OFFER for 192.168.130.253 from 192.168.130.101. 
    [I] Sep 22 12:49:18 ndhcpc: Bridge0: received ACK for 192.168.130.253 from 192.168.130.101 lease 36600 sec. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: configuring interface Home. 
    [I] Sep 22 12:49:18 ndm: Network::Interface::Ip: "Bridge0": IP address is 192.168.130.253/24. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: obtained IP address 192.168.130.253/24. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: interface "Home" is global, priority 1. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: adding a default route via 192.168.130.101. 
    [I] Sep 22 12:49:18 ndm: Dhcp::Client: adding name server 192.168.130.101. 
    [I] Sep 22 12:49:18 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
    [I] Sep 22 12:49:18 mtkiappd: stopped. 
    [I] Sep 22 12:49:19 ndm: Http::Nginx: loaded SSL certificate for "*****************813.keenetic.io".  
    [I] Sep 22 12:49:19 ndm: Http::Nginx: loaded SSL certificate for "sk*******8.keenetic.pro".
    [I] Sep 22 12:49:19 ndm: Network::Interface::Switch: "GigabitEthernet0/1": switch link down at port 2. 
    [I] Sep 22 12:49:19 ndm: Http::Nginx: loaded SSL certificate for MWS. 
    [I] Sep 22 12:49:19 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
    [I] Sep 22 12:49:19 ndm: Core::Session: client disconnected. 
    [I] Sep 22 12:49:20 ndm: Http::Manager: updated configuration. 
    [I] Sep 22 12:49:20 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
    [I] Sep 22 12:49:20 kernel: br0: port 1(eth2.1) entered blocking state
    [I] Sep 22 12:49:20 kernel: br0: port 1(eth2.1) entered listening state
    [I] Sep 22 12:49:20 ndm: Core::Session: client disconnected. 
    [I] Sep 22 12:49:20 mtkiappd: MediaTek IAPP daemon v2.0.5 started on br0. 
    [I] Sep 22 12:49:22 ndm: Network::Interface::Switch: "GigabitEthernet0/1": switch link up at port 2 (1000FD/AN). 
    [I] Sep 22 12:49:22 kernel: br0: port 1(eth2.1) entered blocking state
    [I] Sep 22 12:49:22 kernel: br0: port 1(eth2.1) entered listening state
    [I] Sep 22 12:49:22 coalagent: version 0.4.32 starting. 
    [W] Sep 22 12:49:25 ndm: Dhcp::Client: DHCP server is not responding. 
    [I] Sep 22 12:49:25 ndm: Network::Interface::Ip: "Bridge0": IP address is 192.168.1.3/24. 
    [I] Sep 22 12:49:25 mtkiappd: stopped. 
    [I] Sep 22 12:49:25 kernel: br0: port 1(eth2.1) entered learning state
    [I] Sep 22 12:49:26 ndm: Http::Nginx: loaded SSL certificate for "*****************813.keenetic.io".  
    [I] Sep 22 12:49:26 ndm: Http::Nginx: loaded SSL certificate for "sk*******8.keenetic.pro". 
    [I] Sep 22 12:49:26 ndm: Http::Nginx: loaded SSL certificate for MWS. 
    [I] Sep 22 12:49:26 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
    [I] Sep 22 12:49:26 ndm: Core::Session: client disconnected. 
    [I] Sep 22 12:49:26 ndm: Http::Manager: updated configuration. 
    [I] Sep 22 12:49:26 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
    [I] Sep 22 12:49:26 ndm: Core::Session: client disconnected. 
    [I] Sep 22 12:49:27 mtkiappd: MediaTek IAPP daemon v2.0.5 started on br0. 
    [I] Sep 22 12:49:28 kernel: br0: port 1(eth2.1) entered forwarding state
    [I] Sep 22 12:49:28 kernel: br0: topology change detected, sending tcn bpdu
    [W] Sep 22 12:49:28 ndm: Process: "Coala Agent" has been killed. 
    [I] Sep 22 12:49:30 coalagent: version 0.4.32 starting. 
    [I] Sep 22 12:49:32 ndhcpc: Bridge0: received OFFER for 192.168.130.253 from 192.168.130.101. 
    [I] Sep 22 12:49:32 ndhcpc: Bridge0: received ACK for 192.168.130.253 from 192.168.130.101 lease 36600 sec. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: configuring interface Home. 
    [I] Sep 22 12:49:32 ndm: Network::Interface::Ip: "Bridge0": IP address is 192.168.130.253/24. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: obtained IP address 192.168.130.253/24. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: interface "Home" is global, priority 1. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: adding a default route via 192.168.130.101. 
    [I] Sep 22 12:49:32 ndm: Dhcp::Client: adding name server 192.168.130.101. 
    [I] Sep 22 12:49:32 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
    [I] Sep 22 12:49:32 mtkiappd: stopped. 
    [I] Sep 22 12:49:33 ndm: Network::InternetChecker: Internet access detected. 
    [I] Sep 22 12:49:33 ndm: Http::Nginx: loaded SSL certificate for "*****************813.keenetic.io".   
    [I] Sep 22 12:49:33 ndm: Http::Nginx: loaded SSL certificate for "sk*******8.keenetic.pro".  
    [I] Sep 22 12:49:33 ndm: Http::Nginx: loaded SSL certificate for MWS. 
    [I] Sep 22 12:49:33 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
    [I] Sep 22 12:49:33 ndm: Core::Session: client disconnected. 
    [I] Sep 22 12:49:34 ndm: Http::Manager: updated configuration. 
    [I] Sep 22 12:49:34 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
    [I] Sep 22 12:49:34 ndm: Core::Session: client disconnected. 
    [I] Sep 22 12:49:34 mtkiappd: MediaTek IAPP daemon v2.0.5 started on br0. 
    [I] Sep 22 12:49:36 coalagent: version 0.4.32 starting. 
     

     

    Вопрос в необходимости такой "перестройки/настройки" - в данном случае аж 4 раза которая вылилась в 30сек., возможно ли авто. определить порт контроллера, а на других портах ставить команду "iseq". Как видно сам ретранслятор так же передергивается - 192.168.1.3 и потом получил 192.168.130.253. Так же видно гашения индикатора Интернета после включения ПК и через некоторое время индикатор включается.

    • Upvote 3
  20. 2 часа назад, AlVik сказал:

    У себя планирую схему:
    TV--LAN--Роутер--5GHz--Buddy--LAN--NAS

    на NAS поднят: DLNA, TorrServ ну и конечно хранилки разные... Смотреть планирую 4K в стриминге с NAS, т.е. ставить на закачку 4K торрент и сразу его проигрывать... вот тут у меня возникает вопрос, а как у меня канал распределяться будет... по сути не плохо было бы QoS напилить, но игра врядли стоит свеч... вот и думаю, имеет смысл в этом девайсе, или с моими запросами легче кабель протянуть.

    В данном случае на ТВ при просмотре даже 4К тяжелых c NAS проблем не возникло бы, но так как на NAS вы поднимаете 4К закачку (прием) и сразу отдачу (передача) на ТV, а wifi это дуплекс то будут затыки.

    Однозначно "TV--LAN--Роутер--LAN--NAS"

     

     

    Если бы было

    NAS--LAN--Роутер--5GHz--Buddy--LAN--ТV

    то имеет право на жизнь.

    • Thanks 1
×
×
  • Create New...