Jump to content
  • 2
Никита Юрьев

Keenetic DSL (KN-2010) SNR проблема с изменением!

Question

Всем привет! Прошу помощи в решении проблемы, не могу изменить SNR через telnet, ввожу команду adsl start --snr 1 пишет - Command::Base error[7405600]: no such command может кто сталкивался?Текущая версия KeeneticOS: 3.3 Beta 6

Edited by Никита Юрьев

Share this post


Link to post
Share on other sites

25 answers to this question

Recommended Posts

  • 0
1 час назад, Никита Юрьев сказал:

не могу изменить SNR через telnet

А вам оно точно-точно надо?

Share this post


Link to post
Share on other sites
  • 0
1 hour ago, Le ecureuil said:

А с чего вы взяли, что такая команда вообще существует?

Даже на дешёвых dlink есть такая возможность, я полагаю и здесь должна быть?

  • Upvote 1
  • Confused 1

Share this post


Link to post
Share on other sites
  • 0
2 часа назад, Никита Юрьев сказал:

Даже на дешёвых dlink есть такая возможность, я полагаю и здесь должна быть?

Вы имеете  в виду команду аналогичную:

adsl start --mod m --snr 10  ?

на кинетиках такого нет...

P.S. По какой причине вам потребовалась такая команда? нестабильный сигнал?

Edited by krass

Share this post


Link to post
Share on other sites
  • 0
15 часов назад, Никита Юрьев сказал:

ввожу команду adsl start --snr 1 пишет - Command::Base error[7405600]: no such command может кто сталкивался?

Вам же английским написало - нет такой команды. Допустимые команды ищите в CLI GUIDE для вашего девайса (скачать на оф. сайте).

Share this post


Link to post
Share on other sites
  • 0
39 minutes ago, krass said:

Вы имеете  в виду команду аналогичную:

adsl start --mod m --snr 10  ?

на кинетиках такого нет...

P.S. По какой причине вам потребовалась такая команда? нестабильный сигнал?

Спасибо за инфу! открыл CLI GUIDE удостоверился что нет возможности изменить на моей стороне этот параметр, обидно.

  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0
Только что, Никита Юрьев сказал:

пасибо за инфу! открыл CLI GUIDE удостоверился что нет возможности изменить на моей стороне этот параметр, обидно.

Попробуйте создать  тему с подробным описанием в разделе развитие. Если наберется нужное число голосов - то могут и ввести...

Share this post


Link to post
Share on other sites
  • 0
2 minutes ago, krass said:

Попробуйте создать  тему с подробным описанием в разделе развитие. Если наберется нужное число голосов - то могут и ввести...

спасибо ! попробую.

Share this post


Link to post
Share on other sites
  • 0
2 минуты назад, Никита Юрьев сказал:

Ещё один глупый вопрос , можно ли подключить вайфай адаптер, и подключить его к другой сети ?

Поподробней опишите, что , куда и к какой сети?

Share this post


Link to post
Share on other sites
  • 0
4 minutes ago, krass said:

Поподробней опишите, что , куда и к какой сети?

Имеется WI-FI адаптер Atheros AR9271 имеется 2-я сеть wi-fi  (по мимо моего основного adsl подключения )  задался вопросом подружить адаптер с маршрутизатором, вопрос? есть ли  такая возможность что бы использовать это подключение как резервное или объединить каналы по типу как на mikrotik?

Share this post


Link to post
Share on other sites
  • 0
13 минуты назад, Никита Юрьев сказал:

Точно! спасибо! Пару дней только являюсь обладателем устройства, суммирования каналов нет функции?

 

https://help.keenetic.com/hc/ru/articles/360000384340

 

 

Share this post


Link to post
Share on other sites
  • 0

 

Dec 18 15:01:53 ndhcpc: WifiMaster0/WifiStation0: NDM DHCP client stopped (exit status 0).
Dec 18 15:01:55 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:01:56 ndm: kernel: Wi-Fi client: probe response: SSID=GVD, BSSID=ec:41:18:b8:a4:01, channel=1
Dec 18 15:01:56 ndm: kernel: Wi-Fi client: authenticated
Dec 18 15:01:56 ndm: Ntp::Client: unable to communicate with "3.pool.ntp.org".
Dec 18 15:01:56 ndm: kernel: Wi-Fi client: associated
Dec 18 15:01:56 ndm: Ntp::Client: could not synchronize, waiting...
Dec 18 15:01:58 ndm: Network::Interface::Dsl: "Dsl0": ADSL line idle.
[W] Dec 18 15:01:58 ndm: kernel: Wi-Fi client: disconnected by peer
Dec 18 15:02:00 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:02:01 ndm: kernel: Wi-Fi client: probe response: SSID=GVD, BSSID=ec:41:18:b8:a4:01, channel=2
Dec 18 15:02:01 ndm: kernel: Wi-Fi client: authenticated
Dec 18 15:02:01 ndm: kernel: Wi-Fi client: associated
Dec 18 15:02:02 ndm: Network::Interface::Dsl: "Dsl0": ADSL line handshake.
Dec 18 15:02:04 ndhcpc: WifiMaster0/WifiStation0: NDM DHCP client (version 3.2.37) started.
Dec 18 15:02:04 ndhcpc: WifiMaster0/WifiStation0: created PID file "/var/run/ndhcpc-apcli0.pid".
Dec 18 15:02:05 ndhcpc: WifiMaster0/WifiStation0: received OFFER for 192.168.3.16 from 192.168.3.1.
Dec 18 15:02:07 ndm: Network::Interface::Dsl: "Dsl0": ADSL line training.
Dec 18 15:02:08 ndm: Ntp::Client: unable to communicate with "0.pool.ntp.org".
Dec 18 15:02:08 ndm: Ntp::Client: could not synchronize, waiting...
Dec 18 15:02:20 ndm: kernel: qdma_wan: WAN MAC type is ATM
Dec 18 15:02:20 ndm: kernel: mt7510sar: MT7510 ATM SAR driver 1.0
Dec 18 15:02:20 ndm: kernel: device nas0 entered promiscuous mode
Dec 18 15:02:20 ndm: kernel: br2: port 2(ubr_nas0) entered blocking state
Dec 18 15:02:20 ndm: kernel: br2: port 2(ubr_nas0) entered forwarding state
Dec 18 15:02:21 ndm: kernel: Init VC 0 MPOA Function
Dec 18 15:02:21 ndm: kernel: MPOA Mode: MODE_ROUTER
Dec 18 15:02:21 ndm: kernel: encapType: CON_PPPOA
Dec 18 15:02:21 ndm: Network::Interface::Dsl: "Dsl0": ADSL line showtime.
Dec 18 15:02:21 ndm: Network::Interface::Dsl: "Dsl0": ADSL link up.
Dec 18 15:02:21 ndm: Network::Interface::Tc3262::Dsl: ADSL link speed: 20417/1138 kbps.
[W] Dec 18 15:02:21 ndm: Dhcp::Client: DHCP server is not responding.
Dec 18 15:02:21 ndhcpc: WifiMaster0/WifiStation0: NDM DHCP client stopped (exit status 0).
Dec 18 15:02:22 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:02:23 ndhcpc: Bridge2: NDM DHCP client (version 3.2.37) started.
Dec 18 15:02:23 ndhcpc: Bridge2: created PID file "/var/run/ndhcpc-br2.pid".
Dec 18 15:02:23 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:02:23 pppd[503]: Plugin rp-pppoe.so loaded.
Dec 18 15:02:23 pppd[503]: pppd 2.4.4-4 started by root, uid 0
Dec 18 15:02:23 pppd[503]: Found unterminated session: 34275:90:17:ac:be:9a:d6
Dec 18 15:02:23 pppd[503]: Sent PADT
Dec 18 15:02:24 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:02:24 pppd[503]: PPP session is 16198
Dec 18 15:02:24 pppd[503]: Using interface ppp0
Dec 18 15:02:24 pppd[503]: Connect: ppp0 <--> br2
Dec 18 15:02:24 pppd[503]: CHAP authentication succeeded: Authentication success,Welcome!
Dec 18 15:02:24 pppd[503]: CHAP authentication succeeded
Dec 18 15:02:24 pppd[503]: peer from calling number 90:17:AC:BE:9A:D6 authorized
Dec 18 15:02:24 pppd[503]: local  IP address 100.113.133.196
Dec 18 15:02:24 pppd[503]: remote IP address 100.113.128.1
Dec 18 15:02:24 pppd[503]: primary   DNS address 195.34.224.1
Dec 18 15:02:24 pppd[503]: secondary DNS address 195.34.224.2
Dec 18 15:02:24 ndm: Network::Interface::Base: "PPPoE0": interface is up.
Dec 18 15:02:24 ndm: Network::Interface::Base: "PPPoE0": interface is up.
Dec 18 15:02:24 ndm: Network::Interface::Ppp: "PPPoE0": interface "PPPoE0" is global, priority 57342.
Dec 18 15:02:24 ndm: Network::Interface::Ppp: "PPPoE0": adding default route via PPPoE0.
Dec 18 15:02:24 ndm: Network::Interface::Ppp: "PPPoE0": adding nameserver 195.34.224.1.
Dec 18 15:02:24 ndm: Dns::Manager: name server 195.34.224.1 added, domain (default).
Dec 18 15:02:24 ndm: Network::Interface::Ppp: "PPPoE0": adding nameserver 195.34.224.2.
Dec 18 15:02:24 ndm: Dns::Manager: name server 195.34.224.2 added, domain (default).
Dec 18 15:02:24 ndm: Network::Interface::Ip: "PPPoE0": IP address is 100.113.133.196/32.
Dec 18 15:02:25 ndm: Network::InterfaceFlusher: flushed conntrack and route cache.
Dec 18 15:02:25 ndm: Network::InternetChecker: Internet access detected.
Dec 18 15:02:25 ndm: kernel: Wi-Fi client: probe response: SSID=GVD, BSSID=ec:41:18:b8:a4:01, channel=1
Dec 18 15:02:25 ndm: Http::Nginx: loaded SSL certificate for "a24b99a95cf26c71f2984fd7.keenetic.io".
Dec 18 15:02:25 ndm: Core::Server: started Session /var/run/ndm.core.socket.
Dec 18 15:02:26 ndm: Core::Session: client disconnected.
Dec 18 15:02:26 ndm: Http::Manager: updated configuration.
Dec 18 15:02:26 ndm: Core::Server: started Session /var/run/ndm.core.socket.
Dec 18 15:02:26 ndm: Core::Session: client disconnected.
Dec 18 15:02:27 ndm: Core::Server: started Session /var/run/ndm.core.socket.
Dec 18 15:02:27 upnp: HTTP listening on port 49053
Dec 18 15:02:27 upnp: Listening for NAT-PMP/PCP traffic on port 5351
Dec 18 15:02:30 ndm: Acme::Client: obtained default domain: "a24b99a95cf26c71f2984fd7.keenetic.io".
Dec 18 15:02:30 ndm: Dns::Manager: added static record for "a24b99a95cf26c71f2984fd7.keenetic.io", address 78.47.125.180.
Dec 18 15:04:42 ndm: Core::System::Clock: system time has been changed.
Dec 18 15:04:42 ndm: Ntp::Client: time synchronized with "0.pool.ntp.org".
Dec 18 15:04:42 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:04:42 ndm: Http::Nginx: loaded SSL certificate for "a24b99a95cf26c71f2984fd7.keenetic.io".
Dec 18 15:04:42 ndm: Core::Server: started Session /var/run/ndm.core.socket.
Dec 18 15:04:42 ndm: Core::Session: client disconnected.
Dec 18 15:04:42 ndm: Http::Manager: updated configuration.
Dec 18 15:04:42 ndm: Core::Server: started Session /var/run/ndm.core.socket.
Dec 18 15:04:42 pppd[503]: System time change detected.
Dec 18 15:04:42 ndm: Core::Session: client disconnected.
Dec 18 15:04:43 ndm: kernel: Wi-Fi client: probe response: SSID=GVD, BSSID=ec:41:18:b8:a4:01, channel=1
Dec 18 15:04:43 ndm: kernel: Wi-Fi client: authenticated
Dec 18 15:04:43 ndm: kernel: Wi-Fi client: associated
[W] Dec 18 15:04:45 ndm: kernel: Wi-Fi client: disconnected by peer
Dec 18 15:04:46 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:04:47 ndm: kernel: Wi-Fi client: probe response: SSID=GVD, BSSID=ec:41:18:b8:a4:01, channel=2
Dec 18 15:04:47 ndm: kernel: Wi-Fi client: authenticated
Dec 18 15:04:47 ndm: kernel: Wi-Fi client: associated
Dec 18 15:04:50 ndhcpc: WifiMaster0/WifiStation0: NDM DHCP client (version 3.2.37) started.
Dec 18 15:04:50 ndhcpc: WifiMaster0/WifiStation0: created PID file "/var/run/ndhcpc-apcli0.pid".
Dec 18 15:04:59 ndhcpc: WifiMaster0/WifiStation0: received OFFER for 192.168.3.16 from 192.168.3.1.
[W] Dec 18 15:05:33 ndm: kernel: Wi-Fi client: disconnected by peer
Dec 18 15:05:34 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
[W] Dec 18 15:05:35 ndm: Dhcp::Client: DHCP server is not responding.
Dec 18 15:05:35 ndhcpc: WifiMaster0/WifiStation0: NDM DHCP client stopped (exit status 0).
Dec 18 15:05:35 ndm: kernel: Wi-Fi client: probe response: SSID=GVD, BSSID=ec:41:18:b8:a4:01, channel=1
Dec 18 15:05:36 ndm: kernel: Wi-Fi client: authenticated
Dec 18 15:05:36 ndm: kernel: Wi-Fi client: associated
[W] Dec 18 15:05:37 ndm: kernel: Wi-Fi client: disconnected by peer
Dec 18 15:05:39 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:05:40 ndm: kernel: Wi-Fi client: probe response: SSID=GVD, BSSID=ec:41:18:b8:a4:01, channel=2
Dec 18 15:05:40 ndm: kernel: Wi-Fi client: authenticated
Dec 18 15:05:40 ndm: kernel: Wi-Fi client: associated
Dec 18 15:05:40 ndm: Network::Interface::Base: "WifiMaster0/WifiStation0": interface is down.
Dec 18 15:05:40 ndm: Core::ConfigurationSaver: saving configuration...
Dec 18 15:05:42 ndm: Network::Interface::Base: "WifiMaster0/WifiStation0": interface is up.
Dec 18 15:05:42 ndm: Core::ConfigurationSaver: saving configuration...
Dec 18 15:05:43 ndm: kernel: Wi-Fi client: probe request: SSID=GVD, BSSID=00:00:00:00:00:00
Dec 18 15:05:43 ndm: Core::ConfigurationSaver: configuration saved.
Dec 18 15:05:44 ndm: kernel: Wi-Fi client: probe response: SSID=GVD, BSSID=ec:41:18:b8:a4:01, channel=2
Dec 18 15:05:44 ndm: kernel: Wi-Fi client: authenticated
Dec 18 15:05:44 ndm: kernel: Wi-Fi client: associated
Dec 18 15:05:48 ndhcpc: WifiMaster0/WifiStation0: NDM DHCP client (version 3.2.37) started.
Dec 18 15:05:48 ndhcpc: WifiMaster0/WifiStation0: created PID file "/var/run/ndhcpc-apcli0.pid".
Dec 18 15:05:49 ndhcpc: WifiMaster0/WifiStation0: received OFFER for 192.168.3.16 from 192.168.3.1.
Dec 18 15:05:52 ndhcpc: WifiMaster0/WifiStation0: received ACK for 192.168.3.16 from 192.168.3.1.
Dec 18 15:05:53 ndm: Dhcp::Client: configuring interface WifiMaster0/WifiStation0.
Dec 18 15:05:53 ndm: Network::Interface::Ip: "WifiMaster0/WifiStation0": IP address is 192.168.3.16/24.
Dec 18 15:05:53 ndm: Dhcp::Client: obtained IP address 192.168.3.16/24.
Dec 18 15:05:53 ndm: Dhcp::Client: interface "WifiMaster0/WifiStation0" is global, priority 28671.
Dec 18 15:05:53 ndm: Dhcp::Client: adding a default route via 192.168.3.1.
Dec 18 15:05:53 ndm: Dhcp::Client: adding name server 192.168.3.1.
Dec 18 15:05:53 ndm: Dns::Manager: name server 192.168.3.1 added, domain (default).
Dec 18 15:05:54 ndm: Http::Nginx: loaded SSL certificate for "a24b99a95cf26c71f2984fd7.keenetic.io".
Dec 18 15:05:54 ndm: Core::Server: started Session /var/run/ndm.core.socket.
Dec 18 15:05:54 ndm: Core::Session: client disconnected.
Dec 18 15:05:54 ndm: Http::Manager: updated configuration.
Dec 18 15:05:54 ndm: Core::Server: started Session /var/run/ndm.core.socket.
Dec 18 15:05:54 ndm: Core::Session: client disconnected.

Edited by Никита Юрьев

Share this post


Link to post
Share on other sites
  • 0
On 12/17/2019 at 9:30 PM, Никита Юрьев said:

не могу изменить SNR через telnet

On 12/18/2019 at 9:20 AM, Никита Юрьев said:

Даже на дешёвых dlink есть такая возможность, я полагаю и здесь должна быть?

Изменение SNR запланировано в версии 3.5, настройка появится в CLI и веб-интерфейсе. Возможно, добавим и другие параметры.

  • Thanks 1

Share this post


Link to post
Share on other sites
  • 0
10 минут назад, Никита Юрьев сказал:

Отличная новость спасибо !Через какой промежуток времени выйдет версия 3.5?

После того как 3.4 в draft обкатают, потом в beta, выйдет реализ а затем уже 3.5

  • Thanks 1

Share this post


Link to post
Share on other sites
  • 0
24 minutes ago, AndreBA said:

После того как 3.4 в draft обкатают, потом в beta, выйдет реализ а затем уже 3.5

 

3 minutes ago, keenet07 said:

Несколько месяцев.

Спасибо  за инфу ! 

Share this post


Link to post
Share on other sites

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
Answer this question...

×   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.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...