Jump to content

exeigor

Forum Members
 View Profile  See their activity

  • Posts

    15

  • Joined

  • Last visited

 Content Type 

Posts posted by exeigor

    AdGuardHome

    in Каталог готовых решений Opkg

    Posted

    17 часов назад, Denis P сказал:

    А к чему эта некрофилия? 107.37 уже давным давно доступна для установки, 107.44 на подходе

    Да дело в том, что при каждой настройки конфигурации с веб-интерфейса цп упирается в полотом и DNS сервер ломается. Может сутки поработать и сломаться. Поэтому я хотел понизить версию как это ранее писали. Только вот что-то не запускается 

    AdGuardHome

    in Каталог готовых решений Opkg

    Posted · Edited by exeigor

    Пробовал ставить данную версию на Keenetic Viva (KN-1910), но Adguard Home не стартует. Эта версия вообще рабочая 0.106.3-1 ? 

      

    https://bin.entware.net/mipselsf-k3.4/keenetic/archive/adguardhome-go_v0.106.3-1_mipsel-3.4.ipk

     

     

    minidlna - DLNA-сервер

    in Каталог готовых решений Opkg

    Posted · Edited by exeigor

    Надо подключиться по ssh (можно через pytty) указав ip адрес роутера и порт если менялся. Редактировать конфигурацию можно через nano или vi (установить opkg install nano). Дальше открываешь путь конференции nano /opt/etc/minodlna.conf

    Часовой пояс Entware

    in Вопросы по сборке и настройке Opkg

    Posted · Edited by exeigor

    Всем привет!

    Помогите разобрать с проблемой. Никак не могу настроить корректное время в entware, в роутере выставлено автоматически. 



    Пробовал делать следующие команды:
      

    ~ # echo CST+03 > /opt/etc/TZ
~ # cat /opt/etc/TZ
CST+03
~ # date
Sun Aug 11 07:34:34 UTC 2019

    P.S. Очень не удобно смотреть в логах с разным временем 

     

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

    1.jpg2.JPG3.JPG4.jpg 

     

     

     

    Защищаем DNS запросы с помощью dnscrypt-proxy2. Бонусом блокировка рекламы.

    in Каталог готовых решений Opkg

    Posted · Edited by exeigor

    В последнее время интернет стал тупить. Решил посмотреть в логах dnscrypt, а там ошибки сервера. Что делать ?

     

    Скрытый текст 
    
[2019-04-06 11:43:45] [NOTICE] Source [/opt/etc/dnscrypt/quad9-resolvers.md] loaded
[2019-04-06 11:43:50] [NOTICE] Source [/opt/etc/dnscrypt/opennic.md] loaded
[2019-04-06 11:43:50] [NOTICE] dnscrypt-proxy 2.0.21
[2019-04-06 11:43:50] [NOTICE] Loading the set of forwarding rules from [/opt/etc/dnscrypt/forwarding-rules.txt]
[2019-04-06 11:43:50] [NOTICE] Now listening to 192.168.1.1:53 [UDP]
[2019-04-06 11:43:50] [NOTICE] Now listening to 192.168.1.1:53 [TCP]
[2019-04-06 11:43:50] [INFO] [2.dnscrypt-cert.quad9.net.] the key validity period for this server is excessively long (367 days), significantly reducing reliability and forward security.
[2019-04-06 11:43:50] [NOTICE] [quad9-dnscrypt-ip4-nofilter-pri] OK (crypto v1) - rtt: 45ms
[2019-04-06 11:43:50] [INFO] [2.dnscrypt-cert.quad9.net.] the key validity period for this server is excessively long (367 days), significantly reducing reliability and forward security.
[2019-04-06 11:43:50] [NOTICE] [quad9-dnscrypt-ip4-nofilter-alt] OK (crypto v1) - rtt: 47ms
[2019-04-06 11:43:57] [NOTICE] [ibksturm] OK (crypto v2) - rtt: 787ms
[2019-04-06 11:43:57] [INFO] [2.dnscrypt-cert.opennic2.eth-services.de.] the key validity period for this server is excessively long (3650 days), significantly reducing reliability and forward security.
[2019-04-06 11:43:57] [NOTICE] [opennic-ethservices2] OK (crypto v1) - rtt: 36ms
[2019-04-06 11:43:57] [INFO] [2.dnscrypt-cert.ns3.ca.luggs.co.] the key validity period for this server is excessively long (3650 days), significantly reducing reliability and forward security.
[2019-04-06 11:43:57] [NOTICE] [opennic-luggs] OK (crypto v1) - rtt: 139ms
[2019-04-06 11:43:58] [INFO] [2.dnscrypt-cert.ns4.ca.luggs.co.] the key validity period for this server is excessively long (3650 days), significantly reducing reliability and forward security.
[2019-04-06 11:43:58] [NOTICE] [opennic-luggs2] OK (crypto v1) - rtt: 137ms
[2019-04-06 11:43:58] [NOTICE] [publicarray-au] OK (crypto v2) - rtt: 334ms
[2019-04-06 11:44:05] [NOTICE] [opennic-bongobow] TIMEOUT
[2019-04-06 11:44:05] [NOTICE] [opennic-R4SAS] OK (crypto v2) - rtt: 79ms
[2019-04-06 11:44:05] [INFO] [CloudFlare] TLS version: 304 - Protocol: h2 - Cipher suite: 4867
[2019-04-06 11:44:05] [NOTICE] [CloudFlare] OK (DoH) - rtt: 8ms
[2019-04-06 11:44:05] [NOTICE] Server with the lowest initial latency: CloudFlare (rtt: 8ms)
[2019-04-06 11:44:05] [NOTICE] dnscrypt-proxy is ready - live servers: 9
[2019-04-06 12:30:43] [INFO] Server [CloudFlare] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:30:43] [INFO] Server [CloudFlare] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:30:43] [INFO] Server [CloudFlare] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:30:43] [INFO] Server [CloudFlare] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:30:43] [INFO] Server [opennic-ethservices2] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:30:43] [INFO] Server [opennic-ethservices2] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:30:49] [INFO] Server [quad9-dnscrypt-ip4-nofilter-pri] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:30:49] [INFO] Server [quad9-dnscrypt-ip4-nofilter-pri] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:30:50] [INFO] Server [quad9-dnscrypt-ip4-nofilter-pri] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
[2019-04-06 12:44:05] [INFO] [2.dnscrypt-cert.quad9.net.] the key validity period for this server is excessively long (367 days), significantly reducing reliability and forward security.
[2019-04-06 12:44:05] [INFO] [quad9-dnscrypt-ip4-nofilter-pri] OK (crypto v1) - rtt: 43ms
[2019-04-06 12:44:05] [INFO] [2.dnscrypt-cert.quad9.net.] the key validity period for this server is excessively long (367 days), significantly reducing reliability and forward security.
[2019-04-06 12:44:05] [INFO] [quad9-dnscrypt-ip4-nofilter-alt] OK (crypto v1) - rtt: 43ms
[2019-04-06 12:44:07] [INFO] [doh-ibksturm] TLS version: 304 - Protocol: h2 - Cipher suite: 4866
[2019-04-06 12:44:07] [NOTICE] [doh-ibksturm] OK (DoH) - rtt: 86ms
[2019-04-06 12:44:08] [INFO] [ibksturm] OK (crypto v2) - rtt: 713ms
[2019-04-06 12:44:08] [INFO] [2.dnscrypt-cert.opennic2.eth-services.de.] the key validity period for this server is excessively long (3650 days), significantly reducing reliability and forward security.
[2019-04-06 12:44:08] [INFO] [opennic-ethservices2] OK (crypto v1) - rtt: 40ms
[2019-04-06 12:44:08] [INFO] [2.dnscrypt-cert.ns3.ca.luggs.co.] the key validity period for this server is excessively long (3650 days), significantly reducing reliability and forward security.
[2019-04-06 12:44:08] [INFO] [opennic-luggs] OK (crypto v1) - rtt: 137ms
[2019-04-06 12:44:09] [INFO] [2.dnscrypt-cert.ns4.ca.luggs.co.] the key validity period for this server is excessively long (3650 days), significantly reducing reliability and forward security.
[2019-04-06 12:44:09] [INFO] [opennic-luggs2] OK (crypto v1) - rtt: 141ms
[2019-04-06 12:44:09] [INFO] [publicarray-au] OK (crypto v2) - rtt: 337ms
[2019-04-06 12:44:11] [INFO] [publicarray-au-doh] TLS version: 304 - Protocol: h2 - Cipher suite: 4867
[2019-04-06 12:44:11] [NOTICE] [publicarray-au-doh] OK (DoH) - rtt: 835ms
[2019-04-06 12:44:13] [NOTICE] [opennic-bongobow] TIMEOUT
[2019-04-06 12:44:14] [INFO] [opennic-R4SAS] OK (crypto v2) - rtt: 83ms
[2019-04-06 12:44:14] [INFO] [CloudFlare] TLS version: 304 - Protocol: h2 - Cipher suite: 4867
[2019-04-06 12:44:14] [INFO] [CloudFlare] OK (DoH) - rtt: 8ms

     

    IPSec попытка подключения

    in Вопросы по сборке и настройке Opkg

    Posted · Edited by exeigor

    Добрый день!

    Сегодня обнаружил в логах попытку подключения. Почти каждый день с таким диапазоном ip кто-то пытаются подключиться через IPSec. Есть ли какие нибудь варианты ограничить диапазон ip 216.218.206.0 ? 

    Feb  9 05:20:03 10.10.0.1 ipsec: 08[IKE] 216.218.206.86 is initiating a Main Mode IKE_SA 
Feb  9 05:20:03 10.10.0.1 ipsec: 08[CFG] received proposals: IKE:CAST_CBC 
Feb  9 05:20:03 10.10.0.1 ipsec: [truncated] 08[CFG] configured proposals: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024, IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_768, IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/ECP_384, IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/ECP_256, IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_2048, IKE:3DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/MODP_1024, IKE:3DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/MODP_768, IKE:3DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/ECP_384, IKE:3DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/ECP_256, IKE:3DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/MODP_2048, IKE:DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024, IKE:DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_768, IKE:DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/ECP_384, IKE:DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/ECP_256, IKE:DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_2048, IKE:DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/MODP_1024, IKE:DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/MODP_768, IKE:DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/ECP_384, IKE:DES_CBC/HMAC_MD5_96/PRF_HMAC_MD5/ECP_256, IKE:DES_CBC/HMAC_MD5_96/PRF_HMA
Feb  9 05:20:03 10.10.0.1 ipsec: 08[IKE] no proposal

     

×
×
  • Create New...