Jump to content

IPV6 + KeenDNS

VOG V

By VOG V
in 2.16 [legacy]

 Share

Recommended Posts

VOG V Member

VOG V

Posted
Posted

Замечена следующая проблема:

Если на Кинетике настроен IPV6, то:

1. При вводе в адресной строке браузера my.keenetic.net редирект на адрес вида 123456.keenetic.io завершается ошибкой

2. При переходе на свой (настроен IPV6) домен myname.keenetic.pro - все ОК 

3. При переходе на домен второго роутера на котором также настроен IPV6 - все ОК

4. При переходе на домен третьего роуетра а котором не нестроен IPV6 - ошибка

 

При отключении IPV6 все домены становятся вновь доступными

Opera Снимок.png

  • Thanks 3
Link to comment
Share on other sites
rustrict Advanced Member

rustrict

Posted
Posted
7 часов назад, VOG V сказал:

4. При переходе на домен третьего роуетра а котором не нестроен IPV6 - ошибка

@Le ecureuil, подтверждаю: то же самое. Версия 2.16.D.1.0-0. Ставится галочка у Режим работы (IPv6), подключаешься по IPv6 к *.keenetic.pro на кинетик с IPv4-only и вылетает ошибка 0x22 (34) [ошибка определения IPv4 адреса клиента]. Пробуешь по IPv4 — всё ок:

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

Mac-mini:~ rustrict$ curl -v https://*.keenetic.pro
* Rebuilt URL to: https://*.keenetic.pro/
*   Trying 2a01:4f8:d1:1d00::103...
* TCP_NODELAY set
* Connected to *.keenetic.pro (2a01:4f8:d1:1d00::103) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=keenetic.pro
*  start date: Aug 11 21:56:20 2019 GMT
*  expire date: Nov  9 21:56:20 2019 GMT
*  subjectAltName: host "*.keenetic.pro" matched cert's "*.keenetic.pro"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
> GET / HTTP/1.1
> Host: *.keenetic.pro
> User-Agent: curl/7.54.0
> Accept: */*
> 
< HTTP/1.1 403 Forbidden
< Content-Length: 20950
< Content-Type: text/html
< Server: NDM NDNS
< X-Detail: Unclassified (0x22)
< Date: Wed, 18 Sep 2019 22:59:47 GMT
<...>

Mac-mini:~ rustrict$ curl -4v https://*.keenetic.pro
* Rebuilt URL to: https://*.keenetic.pro/
*   Trying 23.105.235.71...
* TCP_NODELAY set
* Connected to *.keenetic.pro (23.105.235.71) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.keenetic.pro
*  start date: Sep 12 17:40:24 2019 GMT
*  expire date: Dec 11 17:40:24 2019 GMT
*  subjectAltName: host "*.keenetic.pro" matched cert's "*.keenetic.pro"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7f8a71806c00)
> GET / HTTP/2
> Host: *.keenetic.pro
> User-Agent: curl/7.54.0
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200 
< server: Web server
< date: Wed, 18 Sep 2019 23:03:55 GMT
< content-type: text/html; charset=utf-8
< content-length: 3004
< last-modified: Mon, 16 Sep 2019 19:11:54 GMT
< vary: Accept-Encoding
< etag: "5d7fde7a-bbc"
< expires: Wed, 18 Sep 2019 23:03:55 GMT
< cache-control: max-age=0
< cache-control: private
< cache-control: must-revalidate
< accept-ranges: bytes
<...>

 

 

  • Thanks 2
Link to comment
Share on other sites
  • 4 months later...
VOG V Member

VOG V

Posted
  • Author
Posted
1 минуту назад, Le ecureuil сказал:

Да, я про него забыл - все же куча исправлений была.

В следующем выпуске будет.

Очень надеюсь!
Заранее спасибо

image.png.7adde230e52e72fde6322bd1eb0481bb.png

Link to comment
Share on other sites
  • 4 weeks later...
Mamay Honored Flooder

Mamay

Posted
Posted
7 минут назад, Иван Петров сказал:

2.16.D.1.0-2 где можно скачать?

Файлом вряд-ли. В cli:

> components list draft

> components commit

Link to comment
Share on other sites
krass Honored Flooder

krass

Posted
Posted
2 часа назад, Иван Петров сказал:

Стоит 2.16.D.1.0-1 включено автообновление - 2.16.D.1.0-2 не прилетело.

У вас KN-1910 ?

Если да,то:

> components list legacy
> components commit

  • Thanks 1
Link to comment
Share on other sites
Mamay Honored Flooder

Mamay

Posted
Posted
2 часа назад, Иван Петров сказал:

Стоит 2.16.D.1.0-1 включено автообновление - 2.16.D.1.0-2 не прилетело. Через

Файлом вряд-ли. В cli:

> components list draft

> components commit    -  появляется  2.16.D.1.0-1

С утра у вас в подписи стоял Keenetic 4G III. Для той модели я указал верное решение.

Для viva вам указал верное решение @krass

Link to comment
Share on other sites
krass Honored Flooder

krass

Posted
Posted (edited)
1 минуту назад, Иван Петров сказал:

Да у меня Viva (KN-1910).   Не помогло  > components list legacy
> components commit. Может провайдер  стоит IPv6-адрес

А что происходит после ввода 2 команды?

Edited by krass
Link to comment
Share on other sites
  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...