Jump to content
Как правильно добавить self-test и прочую отладку в тему
Где взять тестовые сборки
Официальное хранилище ПО в виде файлов
  • 0

Ethernet подключение активно/неактивно

Игорь1991

Asked by Игорь1991,

 Share

Question

Игорь1991 Newbie

Игорь1991

Posted
Posted

Добрый день! 

Роутер sprinter kn-3711, пару дней назад начались уведомления о событиях: Ethernet соединение активно/отключено. При этом интернет похоже работает, хотелось бы знать природу данных событий. 

Настройки все по умолчанию, которые были предложены мастером по настройке. Устройств подключенных: смарт ТВ, ПК, 2 смартфона, планшет. Все по 5 Ггц. 

8 answers to this question

Recommended Posts

  • 0
Илья Картавенко Honored Flooder

Илья Картавенко

Posted
Posted
6 минут назад, Игорь1991 сказал:

Добрый день! 

Роутер sprinter kn-3711, пару дней назад начались уведомления о событиях: Ethernet соединение активно/отключено. При этом интернет похоже работает, хотелось бы знать природу данных событий. 

Настройки все по умолчанию, которые были предложены мастером по настройке. Устройств подключенных: смарт ТВ, ПК, 2 смартфона, планшет. Все по 5 Ггц. 

Уведомления про какой-то конкретный порт говорят?

  • 0
Mamay Honored Flooder

Mamay

Posted
Posted
6 минут назад, Игорь1991 сказал:

... интернет похоже работает, хотелось бы знать природу данных событий. 

Без лог файлов говорить не о чем.

  • 0
ksp Member

ksp

Posted
Posted

Раз есть события - значит меняется статус интерфейса, скорее всего меняется статус link на порту коммутатора куда подключён кабель провайдера. Это будет видно в self-test в журнале системных сообщений.

  • Upvote 1
  • 0
Игорь1991 Newbie

Игорь1991

Posted
  • Author
Posted
Спойлер

Dec 25 09:51:03 bndstrg
Info: band steering: send BTM request to 3e:0e:2d:aa:73:58 for roam to 2.4GHz band (Low RSSI: -79)

Dec 25 09:41:45 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(3e:0e:2d:aa:73:58) had re-associated from 50:ff:20:dd:00:f1 (FT roam).

Dec 25 09:41:45 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(3e:0e:2d:aa:73:58) FT authenticated successfully.

Dec 25 09:41:14 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(3e:0e:2d:aa:73:58) had re-associated from 52:ff:20:8d:00:f1 (FT roam).

Dec 25 09:41:14 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(3e:0e:2d:aa:73:58) FT authenticated successfully.

Dec 25 09:41:13 bndstrg
Info: band steering: send BTM request to 3e:0e:2d:aa:73:58 for roam to 2.4GHz band (Low RSSI: -91)

Dec 25 09:16:22 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(3e:0e:2d:aa:73:58) had re-associated from 50:ff:20:dd:00:f1 (FT roam).

Dec 25 09:16:22 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(3e:0e:2d:aa:73:58) FT authenticated successfully.

Dec 25 09:11:41 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(58:cd:c9:86:a9:e7) had disassociated by STA (reason: STA is leaving or has left BSS).

Dec 25 09:02:41 dhcpd
Info: Sending Reply to fe80::d5ce:d011:904:4c8b port 546

Dec 25 09:02:41 dhcpd
Info: Information-request message from fe80::d5ce:d011:904:4c8b port 546, transaction ID 0x830AC700

Dec 25 09:02:19 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(3e:0e:2d:aa:73:58) had re-associated from 52:ff:20:8d:00:f1 (FT roam).

Dec 25 09:02:19 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(3e:0e:2d:aa:73:58) FT authenticated successfully.

Dec 25 09:02:19 bndstrg
Info: Core::Syslog: last message repeated 2 times.

Dec 25 09:02:09 bndstrg
Info: band steering: send BTM request to 3e:0e:2d:aa:73:58 for roam to 2.4GHz band (Low RSSI: -81)

Dec 25 08:41:05 ndm
Info: Core::System::StartupConfig: configuration saved.

Dec 25 08:41:04 ndm
Info: Core::Schedule::Manager: raised action "stop" by "schedule0".

Dec 25 08:41:02 ndm
Info: Core::System::StartupConfig: saving (coala/rci).

Dec 25 08:41:02 ndm
Info: Core::Syslog: last message repeated 13 times.

Dec 25 08:41:02 ndm
Info: Core::Schedule::Manager: updated schedule "schedule0".

Dec 25 08:41:02 ndm
Info: Core::Schedule::Manager: cleared schedule "schedule0".

Dec 25 08:41:02 ndm
Info: Core::Schedule::Manager: updated description of "schedule0".

Dec 25 08:40:45 ndm
Info: Core::System::StartupConfig: configuration saved.

Dec 25 08:40:42 ndm
Info: Core::System::StartupConfig: saving (coala/rci).

Dec 25 08:40:42 ndm
Info: Core::Schedule::Manager: raised action "stop" by "schedule0".

Dec 25 08:32:42 ndhcps
Info: sending ACK of 192.168.1.64 to 58:cd:c9:86:a9:e7.

Dec 25 08:32:42 ndhcps
Info: DHCPREQUEST received (STATE_SELECTING) for 192.168.1.64 from 58:cd:c9:86:a9:e7.

Dec 25 08:32:42 ndhcps
Info: making OFFER of 192.168.1.64 to 58:cd:c9:86:a9:e7.

Dec 25 08:32:42 dhcpd
Info: Sending Reply to fe80::d5ce:d011:904:4c8b port 546

Dec 25 08:32:42 dhcpd
Info: Information-request message from fe80::d5ce:d011:904:4c8b port 546, transaction ID 0x7EEE3700

Dec 25 08:32:41 dhcpd
Info: Sending Reply to fe80::d5ce:d011:904:4c8b port 546

Dec 25 08:32:41 dhcpd
Info: Information-request message from fe80::d5ce:d011:904:4c8b port 546, transaction ID 0xCBCAEA00

Dec 25 08:32:41 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(58:cd:c9:86:a9:e7) set key done in WPA2/WPA2PSK.

Dec 25 08:32:41 ndhcps
Info: DHCPDISCOVER received from 58:cd:c9:86:a9:e7.

Dec 25 08:32:41 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(58:cd:c9:86:a9:e7) had associated.

Dec 25 08:28:11 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(3e:0e:2d:aa:73:58) had re-associated from 50:ff:20:dd:00:f1 (FT roam).

Dec 25 08:28:10 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(3e:0e:2d:aa:73:58) FT authenticated successfully.

Dec 25 08:28:10 bndstrg
Info: band steering: send BTM request to 3e:0e:2d:aa:73:58 for roam to 5GHz band

Dec 25 08:26:25 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(3e:0e:2d:aa:73:58) had re-associated from 52:ff:20:8d:00:f1 (FT roam).

Dec 25 08:26:25 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(3e:0e:2d:aa:73:58) FT authenticated successfully.

Dec 25 08:26:24 bndstrg
Info: band steering: send BTM request to 3e:0e:2d:aa:73:58 for roam to 2.4GHz band (Low RSSI: -81)

Dec 25 08:26:20 ndhcps
Info: sending ACK of 192.168.1.49 to 3e:0e:2d:aa:73:58.

Dec 25 08:26:19 ndhcps
Info: DHCPREQUEST received (STATE_SELECTING) for 192.168.1.49 from 3e:0e:2d:aa:73:58.

Dec 25 08:26:19 ndhcps
Info: making OFFER of 192.168.1.49 to 3e:0e:2d:aa:73:58.

Dec 25 08:26:19 ndhcps
Info: DHCPDISCOVER received from 3e:0e:2d:aa:73:58.

Dec 25 08:26:19 ndhcps
Info: making OFFER of 192.168.1.49 to 3e:0e:2d:aa:73:58.

Dec 25 08:26:19 ndhcps
Info: DHCPDISCOVER received from 3e:0e:2d:aa:73:58.

Dec 25 08:26:19 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(3e:0e:2d:aa:73:58) set key done in WPA2/WPA2PSK.

Dec 25 08:26:18 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(3e:0e:2d:aa:73:58) had associated (has FT caps).

Dec 25 08:24:48 ndm
Info: Core::Schedule::Manager: raised action "stop" by "schedule0".

Dec 25 08:24:27 coalagent
Info: updating configuration...

Dec 25 08:24:23 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(ec:30:b3:c9:44:08) had re-associated from 52:ff:20:8d:00:f1 (FT roam).

Dec 25 08:24:23 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(ec:30:b3:c9:44:08) FT authenticated successfully.

Dec 25 08:24:21 ndm
Info: Core::Session: client disconnected.

Dec 25 08:24:21 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Dec 25 08:24:21 ndm
Info: Http::Manager: updated configuration.

Dec 25 08:24:21 ndm
Info: Core::Session: client disconnected.

Dec 25 08:24:21 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Dec 25 08:24:21 ndm
Info: Http::Nginx: loaded SSL certificate for "3552db683248aec2f1bd5cda.keenetic.io".

Dec 25 08:24:21 ndm
Info: Dns::Manager: added static record for "3552db683248aec2f1bd5cda.keenetic.io", address ::

Dec 25 08:24:21 ndm
Info: Dns::Manager: added static record for "3552db683248aec2f1bd5cda.keenetic.io", address 78.47.125.180.

Dec 25 08:24:21 ndm
Info: Netfilter::Util::Conntrack: flushed 1 IPv6 connections.

Dec 25 08:24:20 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": BSS(ra8) channel switched to 40.

Dec 25 08:24:20 kernel
Info: ACS result: Primary Channel 40, Min Channel Busy = 6674, BW = 160

Dec 25 08:24:16 ndm
Info: Network::InternetChecker: Internet access detected.

Dec 25 08:24:16 ndm
Info: Netfilter::Util::Conntrack: flushed 36 IPv4 connections.

Dec 25 08:24:15 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": BSS(ra0) channel switched to 7.

Dec 25 08:24:15 kernel
Info: ACS result: Primary Channel 7, Min Channel Busy = 9666, BW = 20

Dec 25 08:24:14 ndhcps
Info: sending ACK of 192.168.1.97 to ec:30:b3:c9:44:08.

Dec 25 08:24:14 ndhcps
Info: DHCPREQUEST received (STATE_INIT) for 192.168.1.97 from ec:30:b3:c9:44:08.

Dec 25 08:24:14 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(ec:30:b3:c9:44:08) set key done in WPA2/WPA2PSK.

Dec 25 08:24:13 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(ec:30:b3:c9:44:08) had associated (has FT caps).

Dec 25 08:24:13 ndm
Info: Core::Schedule::Manager: raised action "stop" by "schedule0".

В 25.12.2024 в 08:18, Игорь1991 сказал:

Добавил логи с журнала за сегодня. 

 

Логи не все, до момента ошибки. 

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

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.

×
 Share
Go to question listing

  • Recently Browsing   0 members

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

Important Information

This site uses cookies. By clicking "I accept" or continuing to browse the site, you authorize their use in accordance with the Privacy Policy.

  I accept