Dhampir113
-
Posts
125 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Downloads
Blogs
Events
Posts posted by Dhampir113
-
-
Продублирую ещё раз здесь свое длинное сообщение, т.к. есть подобная в курилке , но ошибка воспроизводится и на 2.10 . Песня происходит сейчас на Keenetic II, также было на 2.09, 2.08 и 2.06.
Одно из падений Wi-Fi :
Скрытый текстJun 07 23:00:17ndhcpssending ACK of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 07 23:03:39ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.36 from 00:1e:10:1f:d4:bd. Jun 07 23:03:39ndhcpssending ACK of 192.168.1.36 to 00:1e:10:1f:d4:bd. Jun 07 23:03:39ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.36 from 00:1e:10:1f:d4:bd. Jun 07 23:03:40ndhcpssending ACK of 192.168.1.36 to 00:1e:10:1f:d4:bd. Jun 07 23:03:40ndhcpsDHCPDISCOVER received from 00:1e:10:1f:d4:bd. Jun 07 23:03:40ndhcpsmaking OFFER of 192.168.1.36 to 00:1e:10:1f:d4:bd. Jun 07 23:03:40ndhcpsDHCPDISCOVER received from 00:1e:10:1f:d4:bd. Jun 07 23:03:40ndhcpsmaking OFFER of 192.168.1.36 to 00:1e:10:1f:d4:bd. Jun 07 23:03:43ndhcpsDHCPDISCOVER received from 00:1e:10:1f:d4:bd. Jun 07 23:03:43ndhcpsmaking OFFER of 192.168.1.36 to 00:1e:10:1f:d4:bd. Jun 07 23:03:43ndhcpsDHCPDISCOVER received from 00:1e:10:1f:d4:bd. Jun 07 23:03:43ndhcpsmaking OFFER of 192.168.1.36 to 00:1e:10:1f:d4:bd. Jun 07 23:03:44ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:1e:10:1f:d4:bd. Jun 07 23:03:44ndhcpsclient IP and lease IP mismatch. Jun 07 23:03:44ndhcpssending NAK to 00:1e:10:1f:d4:bd. Jun 07 23:03:44ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:1e:10:1f:d4:bd. Jun 07 23:03:44ndhcpsclient IP and lease IP mismatch. Jun 07 23:03:44ndhcpssending NAK to 00:1e:10:1f:d4:bd. Jun 07 23:04:16wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. Jun 07 23:14:51ndhcpsDHCPREQUEST received (STATE_RENEWING) for 192.168.1.46 from 44:d2:44:2a:3e:ed. Jun 07 23:14:51ndhcpssending ACK of 192.168.1.46 to 44:d2:44:2a:3e:ed. Jun 07 23:44:03ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.33 from 8c:89:a5:05:02:cb. Jun 07 23:44:03ndhcpsanother client with that IP address 192.168.1.33. Jun 07 23:44:03ndhcpssending NAK to 8c:89:a5:05:02:cb. Jun 07 23:44:03ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.33 from 8c:89:a5:05:02:cb. Jun 07 23:44:03ndhcpsanother client with that IP address 192.168.1.33. Jun 07 23:44:03ndhcpssending NAK to 8c:89:a5:05:02:cb. Jun 07 23:44:03ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.33 from 8c:89:a5:05:02:cb. Jun 07 23:44:03ndhcpsanother client with that IP address 192.168.1.33. Jun 07 23:44:03ndhcpssending NAK to 8c:89:a5:05:02:cb. Jun 07 23:44:03ndhcpsDHCPDISCOVER received from 8c:89:a5:05:02:cb. Jun 07 23:44:04ndhcpsmaking OFFER of 192.168.1.52 to 8c:89:a5:05:02:cb. Jun 07 23:44:04ndhcpsDHCPDISCOVER received from 8c:89:a5:05:02:cb. Jun 07 23:44:04ndhcpsmaking OFFER of 192.168.1.52 to 8c:89:a5:05:02:cb. Jun 07 23:44:04ndhcpsDHCPDISCOVER received from 8c:89:a5:05:02:cb. Jun 07 23:44:04ndhcpsmaking OFFER of 192.168.1.52 to 8c:89:a5:05:02:cb. Jun 07 23:44:04ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.52 from 8c:89:a5:05:02:cb. Jun 07 23:44:04ndhcpssending ACK of 192.168.1.52 to 8c:89:a5:05:02:cb. Jun 07 23:44:05ndmNetwork::Interface::Switch: switch link up at port 1 (FastEthernet0/1). Jun 07 23:50:49wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated. Jun 07 23:51:13wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had associated successfully. Jun 07 23:51:14wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) set key done in WPA2/WPA2PSK. Jun 07 23:51:14ndhcpsDHCPDISCOVER received from 00:0a:f5:11:4f:08. Jun 07 23:51:14ndhcpsmaking OFFER of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 07 23:51:14ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:0a:f5:11:4f:08. Jun 07 23:51:14ndhcpssending ACK of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 07 23:51:33wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated. Jun 08 00:09:26wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had associated successfully. Jun 08 00:09:27wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) set key done in WPA2/WPA2PSK. Jun 08 00:09:27ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.62 from 84:a6:c8:57:37:5d. Jun 08 00:09:27ndhcpssending ACK of 192.168.1.62 to 84:a6:c8:57:37:5d. Jun 08 00:09:27ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.62 from 84:a6:c8:57:37:5d. Jun 08 00:09:27ndhcpssending ACK of 192.168.1.62 to 84:a6:c8:57:37:5d. Jun 08 00:09:28ndmNetwork::Interface::Switch: switch link down at port 1 (FastEthernet0/1). Jun 08 00:11:28wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had associated successfully. Jun 08 00:11:29wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) set key done in WPA2/WPA2PSK. Jun 08 00:11:29ndhcpsDHCPDISCOVER received from 00:0a:f5:11:4f:08. Jun 08 00:11:29ndhcpsmaking OFFER of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 08 00:11:29ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:0a:f5:11:4f:08. Jun 08 00:11:29ndhcpssending ACK of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 08 00:11:33wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated. Jun 08 00:26:21ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.33 from 00:1e:10:1f:80:10. Jun 08 00:26:21ndhcpsanother client with that IP address 192.168.1.33. Jun 08 00:26:21ndhcpssending NAK to 00:1e:10:1f:80:10. Jun 08 00:26:21ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.33 from 00:1e:10:1f:80:10. Jun 08 00:26:21ndhcpsanother client with that IP address 192.168.1.33. Jun 08 00:26:21ndhcpssending NAK to 00:1e:10:1f:80:10. Jun 08 00:26:21ndhcpsDHCPDISCOVER received from 00:1e:10:1f:80:10. Jun 08 00:26:22ndhcpsmaking OFFER of 192.168.1.57 to 00:1e:10:1f:80:10. Jun 08 00:26:22ndhcpsDHCPDISCOVER received from 00:1e:10:1f:80:10. Jun 08 00:26:22ndhcpsmaking OFFER of 192.168.1.57 to 00:1e:10:1f:80:10. Jun 08 00:26:25ndhcpsDHCPDISCOVER received from 00:1e:10:1f:80:10. Jun 08 00:26:25ndhcpsmaking OFFER of 192.168.1.57 to 00:1e:10:1f:80:10. Jun 08 00:26:25ndhcpsDHCPDISCOVER received from 00:1e:10:1f:80:10. Jun 08 00:26:25ndhcpsmaking OFFER of 192.168.1.57 to 00:1e:10:1f:80:10. Jun 08 00:26:26ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:1e:10:1f:80:10. Jun 08 00:26:26ndhcpsclient IP and lease IP mismatch. Jun 08 00:26:26ndhcpssending NAK to 00:1e:10:1f:80:10. Jun 08 00:26:26ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:1e:10:1f:80:10. Jun 08 00:26:26ndhcpsclient IP and lease IP mismatch. Jun 08 00:26:26ndhcpssending NAK to 00:1e:10:1f:80:10. Jun 08 00:26:58wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. Jun 08 00:36:27wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had associated successfully. Jun 08 00:36:32wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. Jun 08 00:36:59wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had associated successfully. Jun 08 00:37:04wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. Jun 08 00:37:07wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had associated successfully. Jun 08 00:37:12wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. Jun 08 00:37:45wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had associated successfully. Jun 08 00:37:47wmondCore::Syslog: last message repeated 2 times. Jun 08 00:37:53wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) pairwise key handshaking timeout. Jun 08 00:37:53wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. Jun 08 00:38:05wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had associated successfully. Jun 08 00:38:10wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. Jun 08 00:38:56ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.52 from 8c:89:a5:05:02:cb. Jun 08 00:38:57ndhcpssending ACK of 192.168.1.52 to 8c:89:a5:05:02:cb. Jun 08 00:38:57ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.52 from 8c:89:a5:05:02:cb. Jun 08 00:38:57ndhcpssending ACK of 192.168.1.52 to 8c:89:a5:05:02:cb. Jun 08 00:38:57ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.52 from 8c:89:a5:05:02:cb. Jun 08 00:38:57ndhcpssending ACK of 192.168.1.52 to 8c:89:a5:05:02:cb. Jun 08 00:38:58ndmNetwork::Interface::Switch: switch link up at port 1 (FastEthernet0/1). Jun 08 00:41:12wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had associated successfully. Jun 08 00:41:13wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) set key done in WPA2/WPA2PSK. Jun 08 00:41:13ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.62 from 84:a6:c8:57:37:5d. Jun 08 00:41:13ndhcpssending ACK of 192.168.1.62 to 84:a6:c8:57:37:5d. Jun 08 00:41:13ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.62 from 84:a6:c8:57:37:5d. Jun 08 00:41:14ndhcpssending ACK of 192.168.1.62 to 84:a6:c8:57:37:5d. Jun 08 00:41:14ndmNetwork::Interface::Switch: switch link down at port 1 (FastEthernet0/1).
Одно дело когда из сети вылетает одно устройство (причинное, у которого мак меняется на лету), но у меня же при этом ещё перестает раздаваться инет по вафле и падает сама Wi-Fi сеть для всех остальных устройств, т.е. теряется соединение с роутером по вафле (по кабелю все норм) в логах всем раздается NAK, индикатор Wi-fi горит.
Сижу на форуме с одного смарта, по ноуту идет фильм, мама смотрит ролики на ютубе через свой смарт, принтер просто висит в сети - все через вафлю: 2 смарта (00:0a:f5:11:4f:08, 00:87:01:19:64:d4) принтер (44:d2:44:2a:3e:ed), ноут по wi-fi (84:a6:c8:57:37:5d). Когда теряется wi-fi, подключаю ноут к роутеру по LAN (8c:89:a5:05:02:cb). Вмешательства в прошивку были только на одном смарте, на котором я впервые и заметил пропадание сети (решал это отключением/включением модуля на самом смарте). А сейчас даже если он не подключен к сети можно наблюдать картину выше, сеть пропадает сразу на всех устройствах. Приходится роутер перезапускать, чтоб восстановить все. Подключал все устройства к мобильному роутеру E5832S, проблем с пропаданием сети не замечал, так же оба смарта в течение недели тестировались на keenetic lite 2 (инет по кабелю ТТК) и тоже разрывов и потерь wi-fi не было.
Немножко понаблюдав заметил, что начинается всё с usb-модема Huawei 367 (00:1e:10:1f:d4:bd, 00:1e:10:1f:80:10, 00:1e:10:1f:d7:e6).
Вот ещё раз повтор: сидел в инете со смарта + на ноуте по вафле открыт форум, в 17.22 перестали грузиться страницы в хроме, затем отвалилась wi-fi (не смог зайти с телефона и ноута на роутер), хотя показывает значек что подключено, индикатор на роутере горит, в 17.26 попробовал переподключиться к вафле со смарта, нифига, не подключается. Зашел на роутер через Lan с ноута, в журнале:
Скрытый текст[I] Jun 9 17:22:49 wmond: WifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. [I] Jun 9 17:23:35 ndhcps: DHCPDISCOVER received for 192.168.1.52 from 8c:89:a5:05:02:cb. [I] Jun 9 17:23:35 ndhcps: making OFFER of 192.168.1.52 to 8c:89:a5:05:02:cb. [I] Jun 9 17:23:35 ndhcps: DHCPDISCOVER received for 192.168.1.52 from 8c:89:a5:05:02:cb. [I] Jun 9 17:23:35 ndhcps: making OFFER of 192.168.1.52 to 8c:89:a5:05:02:cb. [I] Jun 9 17:23:35 ndhcps: DHCPDISCOVER received for 192.168.1.52 from 8c:89:a5:05:02:cb. [I] Jun 9 17:23:35 ndhcps: making OFFER of 192.168.1.52 to 8c:89:a5:05:02:cb. [I] Jun 9 17:23:35 ndhcps: DHCPREQUEST received (STATE_SELECTING) for 192.168.1.52 from 8c:89:a5:05:02:cb. [I] Jun 9 17:23:35 ndhcps: sending ACK of 192.168.1.52 to 8c:89:a5:05:02:cb. [I] Jun 9 17:23:36 ndm: Network::Interface::Switch: switch link up at port 1 (FastEthernet0/1). [I] Jun 9 17:26:24 wmond: WifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated. [I] Jun 9 17:26:36 wmond: WifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had associated successfully. [I] Jun 9 17:26:43 wmond: WifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) pairwise key handshaking timeout. [I] Jun 9 17:26:43 wmond: WifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated. [I] Jun 9 17:26:50 wmond: WifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had associated successfully. [I] Jun 9 17:26:56 wmond: WifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) pairwise key handshaking timeout. [I] Jun 9 17:26:56 wmond: WifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated.
роутер не перезагружал, где-то в 17.27 смарт сам подключился к wi-fi, в этот раз записей о разрывах нет в логе. Из-за этих разрывов на youtubе ничего нельзя посмотреть.
А вот это уже на 2.10 и тут хорошо видно что каким-то образом модем пытается получить занятый другим устройством IP-адрес, и клиенты начинают отваливаться:
Скрытый текстJun 10 14:36:22ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.33 from 00:1e:10:1f:d7:e6. Jun 10 14:36:22ndhcpsanother client with that IP address 192.168.1.33. Jun 10 14:36:22ndhcpssending NAK to 00:1e:10:1f:d7:e6. Jun 10 14:36:22ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.33 from 00:1e:10:1f:d7:e6. Jun 10 14:36:22ndhcpsanother client with that IP address 192.168.1.33. Jun 10 14:36:22ndhcpssending NAK to 00:1e:10:1f:d7:e6. Jun 10 14:36:22ndhcpsDHCPDISCOVER received from 00:1e:10:1f:d7:e6. Jun 10 14:36:22ndhcpsmaking OFFER of 192.168.1.71 to 00:1e:10:1f:d7:e6. Jun 10 14:36:22ndhcpsDHCPDISCOVER received from 00:1e:10:1f:d7:e6. Jun 10 14:36:22ndhcpsmaking OFFER of 192.168.1.71 to 00:1e:10:1f:d7:e6. Jun 10 14:36:26ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:1e:10:1f:d7:e6. Jun 10 14:36:26ndhcpsclient IP and lease IP mismatch. Jun 10 14:36:26ndhcpssending NAK to 00:1e:10:1f:d7:e6. Jun 10 14:36:26ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:1e:10:1f:d7:e6. Jun 10 14:36:26ndhcpsclient IP and lease IP mismatch. Jun 10 14:36:26ndhcpssending NAK to 00:1e:10:1f:d7:e6. Jun 10 14:49:56wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had deauthenticated. Jun 10 17:53:40ndhcpsDHCPREQUEST received (STATE_RENEWING) for 192.168.1.37 from 00:87:01:19:64:d4. Jun 10 17:53:41ndhcpssending ACK of 192.168.1.37 to 00:87:01:19:64:d4. Jun 10 17:54:20wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated. Jun 10 17:54:48ndhcpsDHCPREQUEST received (STATE_RENEWING) for 192.168.1.46 from 44:d2:44:2a:3e:ed. Jun 10 17:54:48ndhcpssending ACK of 192.168.1.46 to 44:d2:44:2a:3e:ed. Jun 10 18:17:58wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had associated successfully. Jun 10 18:17:59wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) set key done in WPA2/WPA2PSK. Jun 10 18:18:00ndhcpsDHCPDISCOVER received from 00:0a:f5:11:4f:08. Jun 10 18:18:00ndhcpsmaking OFFER of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 10 18:18:00ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:0a:f5:11:4f:08. Jun 10 18:18:00ndhcpssending ACK of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 10 18:19:42wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated.
Почему модем лезет в локальную сеть за адресом и почему DHCP начинает его ему выдавать отключая при этом другого клиента? Помогите пожалуйста разобраться.
Селфтест прикрепляю ниже
-
18 минут назад, vasek00 сказал:
Остается только посмотреть что будет после 2.09.B.0.0-1
скорее всего это была моя вина, сейчас попробовал и на 2.09.B.0.0-0 и на 2.09.B.0.0-1, и после сброса и и после обновления/прошивки, просто у меня промежуток между включить и отключить отладку был около 5 секунд, а сейчас снимал селфтест по минуте и все параметры на месте. Извините что озадачил. Попробуйте сами включить и отключить отладку через секунду две и параметров не будет.
Тему можно закрывать.
-
1 час назад, vasek00 сказал:
В данном случае я бы поступил так :
сделаю, только у меня нужный набор равен рекомендуемому
1 час назад, vasek00 сказал:5.посмотреть результат.
в смысле параметры UPnP?
1 час назад, vasek00 сказал:не "путешествуете" например в раздел про Components
это я случайно
Результат:
непосредственно после сброса:Скрытый текст<process id="UPnP::Manager"> <pid>-1</pid> <service> <configured>no</configured> <alive>no</alive> <started>yes</started> <state>STOPPED</state> </service> </process>
после заливки конфига и перезапуска остается такжеСкрытый текст<process id="UPnP::Manager"> <pid>-1</pid> <service> <configured>no</configured> <alive>no</alive> <started>yes</started> <state>STOPPED</state> </service> </process>
периодически буду проверять параметры компонента -
3 часа назад, vasek00 сказал:
Не то что интересуюсь а для общего развития не возражал бы.
странно, в текущем селфтесте появились все параметры
Скрытый текст<process id="UPnP::Manager"> <name>miniupnpd</name> <arg>-a</arg> <arg>Bridge0</arg> <arg>br0</arg> <arg>-i</arg> <arg>UsbModem0</arg> <arg>-m</arg> <arg>***-***-***-***-***</arg> <arg>-u</arg> <arg>6*****************************</arg> <arg>-s</arg> <arg>S***********</arg> <arg>-N</arg> <arg>-U</arg> <state>S (sleeping)</state> <pid>6301</pid> <ppid>159</ppid> <vm-size>1432 kB</vm-size> <vm-data>304 kB</vm-data> <vm-stk>136 kB</vm-stk> <vm-exe>96 kB</vm-exe> <vm-lib>860 kB</vm-lib> <vm-swap>0 kB</vm-swap> <threads>1</threads> <fds>9</fds> <statistics> <interval>30</interval> <cpu> <now>43442.478009</now> <min>0</min> <max>0</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> <service> <configured>yes</configured> <alive>yes</alive> <started>yes</started> <state>STARTED</state> </service> </process>
может после обновления/прошивки/сброса необходимо время, чтобы компонент сверил серномер и сервистаг с сервером? ( я же селфтесты снимал максимум через 1-2 часа после прошивки и сброса),текущий селфтест, из которого взяты параметры UPnP::Manager, получается через 12 часов примерно после обновления до последней 2.09
З.Ы. Скинул селфтест в личку
-
43 минуты назад, vasek00 сказал:
Простые пользователи селф-тест который вы прикрепили смотреть не могут, только разработчики
могу отправить вам в личку если интересуетесь данной проблемой UpnP
-
В 05.06.2017 в 13:36, ndm сказал:
В бете официально убрали поддержку zyxelsn, который был только в "древних" партиях устройств. Но ради драфта придется аккуратно вернуть.
В 05.06.2017 в 18:28, vasek00 сказал:Все что связано с u-config думаю лучше подождать - оф.изменения в прошивке
Решил проблему по другому, в u-config добавил переменную sernumb со значением серийного номера, (там теперь две переменных с одинаковым значением: zyxelsn и sernumb, надеюсь мешать друг другу не будут), ошибки исчезли
З.Ы. Насчет UPnP:
такого у меня так и нету
Скрытый текст<process id="UPnP::Manager"> <name>miniupnpd</name> <arg>-a</arg> <arg>Bridge0</arg> <arg>br0</arg> <arg>-i</arg> <arg>PPPoE0</arg> <arg>-m</arg> <arg>7------------------------------7</arg> <arg>-u</arg> <arg>12------------------------------------------1a</arg> <arg>-s</arg> <arg>S--------------------------------------7</arg> <arg>-N</arg> <arg>-U</arg> <state>S (sleeping)</state> <pid>5687</pid> <ppid>159</ppid> <vm-size>1452 kB</vm-size> <vm-data>324 kB</vm-data> <vm-stk>136 kB</vm-stk> <vm-exe>96 kB</vm-exe> <vm-lib>860 kB</vm-lib> <vm-swap>0 kB</vm-swap> <threads>1</threads> <fds>9</fds> <statistics> <interval>4</interval> <cpu> <now>181067.504539</now> <min>0</min> <max>0</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics>
так и осталось вот так
<process id="UPnP::Manager"> <pid>-1</pid> <service> <configured>no</configured> <alive>no</alive> <started>yes</started> <state>STOPPED</state> </service> </process>
Хотя в журнале есть сообщения что она вроде работает:
Jun 07 01:47:42ndmUPnP::Manager: a new rule appended. Jun 07 01:47:42ndmUPnP::Manager: redirect rule added: udp UsbModem0:54491 -> 192.168.1.62:54491. Jun 07 01:47:42ndmUPnP::Manager: a new rule appended. Jun 07 01:47:42ndmUPnP::Manager: forward rule added: udp UsbModem0 -> 192.168.1.62:54491. Jun 07 01:47:42ndmUPnP::Manager: a new rule appended. Jun 07 01:47:42ndmUPnP::Manager: redirect rule added: tcp UsbModem0:42928 -> 192.168.1.62:42928. Jun 07 01:47:42ndmUPnP::Manager: a new rule appended. Jun 07 01:47:42ndmUPnP::Manager: forward rule added: tcp UsbModem0 -> 192.168.1.62:42928. Jun 07 01:47:42ndmUPnP::Manager: a new rule appended. Jun 07 01:47:42ndmUPnP::Manager: redirect rule added: udp UsbModem0:42928 -> 192.168.1.62:42928. Jun 07 01:47:42ndmUPnP::Manager: a new rule appended. Jun 07 01:47:42ndmUPnP::Manager: forward rule added: udp UsbModem0 -> 192.168.1.62:42928.
селф-тест прикрепил в следующее скрытое сообщение
-
8 минут назад, vasek00 сказал:
Все что связано с u-config думаю лучше подождать - оф.изменения в прошивке, так как оказываются есть "древние" и "не очень".
спасибо, помогли разобраться, будем ждать изменений
-
В 05.06.2017 в 18:15, vasek00 сказал:
1. Да в этом большой минус данного режима, соединение сбрасывается и заново поднимается. В данном случае чтоб узнать что случилось в системе не прибегаю к selftest можно использовать Entware и доступные утилиты.
2. Да, так как в первые секунды uboot ставит данный MAC (00:AA:BB:CC:DD:10) и IP из своего окружения и роутер доступен по tftp, если tftp нет то произойдет загрузка прошивки так сказать из flash роутера.
сорь, вот что ещё забыл
в self-test
<wlanwps/> <ndmhwid/> <ctrlsum/> <integrity>fail</integrity>
ndmhwid пропишу kn_rb
ctrlsum сгенерится сама?
integrity (типа проверка) получается не пройдена, значит u-config не прописан до конца?
вот что в printenv
Скрытый текстbootcmd=tftp bootdelay=5 baudrate=57600 ethaddr="00:AA:BB:CC:DD:10" ipaddr=192.168.1.1 serverip=192.168.1.2 ramargs=setenv bootargs root=/dev/ram rw addip=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):$(netdev):off addmisc=setenv bootargs $(bootargs) console=ttyS0,$(baudrate) ethaddr=$(ethaddr) panic=1 flash_self=run ramargs addip addmisc;bootm $(kernel_addr) $(ramdisk_addr) kernel_addr=BFC40000 u-boot=u-boot.bin load=tftp 8A100000 $(u-boot) u_b=protect off 1:0-1;era 1:0-1;cp.b 8A100000 BC400000 $(filesize) loadfs=tftp 8A100000 root.cramfs u_fs=era bc540000 bc83ffff;cp.b 8A100000 BC540000 $(filesize) test_tftp=tftp 8A100000 root.cramfs;run test_tftp ethact=Eth0 (10/100-M) zyxelsn=S************ servicetag=*************** servicehost=ndss.11.zyxel.ndmsystems.com servicepass=*************** wlanssid=Keenetic-**** wlankey=******** country=RU lastwanip=***.***.***.*** cloudalias=******************************* stdin=serial stdout=serial stderr=serial
-
2 минуты назад, vasek00 сказал:
А как же у вас вообще UPnP работает если он STOPPED.
Разработчики ответили выше, что будет подправлено
работает, но видимо с косяками.
Если не сильно утомил у меня последние 2 вопроса:
1. Модем и должен реконнектиться после включения отладки?
2. В U-config есть переменная ethaddr, она и должна быть: ethaddr="00:AA:BB:CC:DD:10" или же у неё другое значение должно быть?
-
В 05.06.2017 в 13:38, vasek00 сказал:
сделайте selftest (текущий) и потом поиск по "UPnP::Manager" вы должны попасть на описание данной службы где в полях <arg> должны увидеть тек. значения
сделал, но значений не нашел, вот только что есть:
<process id="UPnP::Manager"> <pid>-1</pid> <service> <configured>no</configured> <alive>no</alive> <started>yes</started> <state>STOPPED</state> </service> </process>
И вот ещё что заметил,после снятия селфтеста (включения отладки) реконнектится usb-модем, так должно быть? на 2.06 и 2.08 вроде не было/не замечал
Скрытый текст[I] Jun 5 16:35:46 ndm: Core::Debug: system debug enabled. [I] Jun 5 16:35:46 ndnproxy: stats. file: /var/ndnproxymain.stat [I] Jun 5 16:35:46 pppd[379]: Modem hangup [I] Jun 5 16:35:46 pppd[379]: Connect time 851.3 minutes. [I] Jun 5 16:35:46 pppd[379]: Sent 11978099 bytes, received 137604001 bytes. [I] Jun 5 16:35:46 pppd[379]: Connection terminated. [I] Jun 5 16:35:46 ndhcps: NDM DHCP server stopped (exit status: 0). [I] Jun 5 16:35:46 ndhcps: NDM DHCP server stopped (exit status: 0). [I] Jun 5 16:35:46 ndm: Network::InterfaceFlusher: flushed UsbModem0 conntrack and route cache. [I] Jun 5 16:35:46 pppd[379]: Exit. [I] Jun 5 16:35:46 ndnproxy: updating configuration... [I] Jun 5 16:35:46 ndnproxy: load config file: /var/ndnproxymain.conf [I] Jun 5 16:35:46 ndnproxy: set profile for ip 127.0.0.1 0 [I] Jun 5 16:35:46 ndnproxy: set profile for ip ::1 0 [I] Jun 5 16:35:46 ndnproxy: stats. file: /var/ndnproxymain.stat [I] Jun 5 16:35:46 ndm: Network::Interface::Base: "UsbModem0": interface is up. [I] Jun 5 16:35:46 ndm: Hotspot::Manager: New neighbour: IP: 192.168.1.33, MAC: *****************, Interface: Bridge0. [I] Jun 5 16:35:46 ndm: Hotspot::Manager: ARP Entries dump. [I] Jun 5 16:35:46 ndm: Hotspot::Manager: 0: IP: 192.168.1.46, MAC: *****************, Interface: Bridge0, Age: 40 s. [I] Jun 5 16:35:46 ndm: Hotspot::Manager: 1: IP: 192.168.1.37, MAC: *****************, Interface: Bridge0, Age: 11 s. [I] Jun 5 16:35:46 ndm: Hotspot::Manager: 2: IP: 192.168.1.33, MAC: *****************, Interface: Bridge0, Age: 0 s. [I] Jun 5 16:35:46 ndm: Hotspot::Manager: 3: IP: 192.168.1.62, MAC: *****************, Interface: Bridge0, Age: 55 s. [I] Jun 5 16:35:46 ndnproxy: updating configuration... [I] Jun 5 16:35:46 ndnproxy: load config file: /var/ndnproxymain.conf [I] Jun 5 16:35:46 ndnproxy: set profile for ip 127.0.0.1 0 [I] Jun 5 16:35:46 ndnproxy: set profile for ip ::1 0 [I] Jun 5 16:35:46 ndnproxy: stats. file: /var/ndnproxymain.stat [I] Jun 5 16:35:46 upnp: shutting down MiniUPnPd [I] Jun 5 16:35:46 ndm: Core::Server: client disconnected. [I] Jun 5 16:35:48 ndhcps: NDM DHCP server (version 3.2.11) started. [I] Jun 5 16:35:48 ndhcps: interfaces dump: [I] Jun 5 16:35:48 ndhcps: >>>>>>>>>>>>>>> [I] Jun 5 16:35:48 ndhcps: <<<<<<<<<<<<<<< [I] Jun 5 16:35:48 ndhcps: DHCP interfaces count: 1 [I] Jun 5 16:35:48 ndhcps: setup sockets, use binding: yes, use only kernel socket: no [I] Jun 5 16:35:48 ndhcps: NDM DHCP server (version 3.2.11) started. [I] Jun 5 16:35:48 ndhcps: interfaces dump: [I] Jun 5 16:35:48 ndhcps: >>>>>>>>>>>>>>> [I] Jun 5 16:35:48 ndhcps: <<<<<<<<<<<<<<< [I] Jun 5 16:35:48 ndhcps: DHCP interfaces count: 1 [I] Jun 5 16:35:48 ndhcps: setup sockets, use binding: yes, use only kernel socket: no [I] Jun 5 16:35:48 ndm: Core::Server: started Session /var/run/ndm.core.socket. [I] Jun 5 16:35:48 ndhcps: load dynamic lease: 192.168.1.37 ***************** 23825 android-**************** [I] Jun 5 16:35:48 ndhcps: IP address 192.168.1.37 is in pool 192.168.1.33-192.168.1.72 [I] Jun 5 16:35:48 ndhcps: add dynamic lease: 192.168.1.37 ***************** 74952 bind yes android-**************** unknown [I] Jun 5 16:35:48 ndhcps: load dynamic lease: 192.168.1.33 ***************** 24707 android-**************** [I] Jun 5 16:35:48 ndhcps: IP address 192.168.1.33 is in pool 192.168.1.33-192.168.1.72 [I] Jun 5 16:35:48 ndhcps: add dynamic lease: 192.168.1.33 ***************** 75834 bind yes android-**************** unknown [I] Jun 5 16:35:48 ndhcps: load dynamic lease: 192.168.1.46 ***************** 24900 EPSON2A3EED [I] Jun 5 16:35:48 ndhcps: IP address 192.168.1.46 is in pool 192.168.1.33-192.168.1.72 [I] Jun 5 16:35:48 ndhcps: add dynamic lease: 192.168.1.46 ***************** 76027 bind yes EPSON2A3EED unknown [I] Jun 5 16:35:48 ndhcps: load dynamic lease: 192.168.1.62 ***************** 25135 DHAMPIR-PC [I] Jun 5 16:35:48 ndhcps: IP address 192.168.1.62 is in pool 192.168.1.33-192.168.1.72 [I] Jun 5 16:35:48 ndhcps: add dynamic lease: 192.168.1.62 ***************** 76262 bind yes DHAMPIR-PC unknown [I] Jun 5 16:35:48 ndhcps: add signal 2 handler 0x40a218 [I] Jun 5 16:35:48 ndhcps: add signal 15 handler 0x40a218 [I] Jun 5 16:35:48 ndm: Core::Server: client disconnected. [I] Jun 5 16:35:48 ndhcps: add signal 16 handler 0x40a218 [I] Jun 5 16:35:48 ndhcps: add signal 17 handler 0x40a218 [I] Jun 5 16:35:48 ndhcps: add signal 1 handler 0x40a218 [I] Jun 5 16:35:48 ndm: Core::Server: started Session /var/run/ndm.core.socket. [I] Jun 5 16:35:48 ndnproxy: max. requests 14 132 [I] Jun 5 16:35:48 ndhcps: load dynamic lease: 192.168.1.37 ***************** 23825 android-**************** [I] Jun 5 16:35:48 ndhcps: IP address 192.168.1.37 is not in pool 10.1.30.33-10.1.30.52 [I] Jun 5 16:35:48 ndhcps: load dynamic lease: 192.168.1.33 ***************** 24707 android-**************** [I] Jun 5 16:35:48 ndhcps: IP address 192.168.1.33 is not in pool 10.1.30.33-10.1.30.52 [I] Jun 5 16:35:48 ndhcps: load dynamic lease: 192.168.1.46 ***************** 24900 EPSON2A3EED [I] Jun 5 16:35:48 ndhcps: IP address 192.168.1.46 is not in pool 10.1.30.33-10.1.30.52 [I] Jun 5 16:35:48 ndhcps: load dynamic lease: 192.168.1.62 ***************** 25135 DHAMPIR-PC [I] Jun 5 16:35:48 ndhcps: IP address 192.168.1.62 is not in pool 10.1.30.33-10.1.30.52 [I] Jun 5 16:35:48 ndhcps: add signal 2 handler 0x40a218 [I] Jun 5 16:35:48 ndhcps: add signal 15 handler 0x40a218 [I] Jun 5 16:35:48 ndhcps: add signal 16 handler 0x40a218 [I] Jun 5 16:35:48 ndhcps: add signal 17 handler 0x40a218 [I] Jun 5 16:35:48 ndhcps: add signal 1 handler 0x40a218 [I] Jun 5 16:35:48 ndm: Core::Server: client disconnected. [I] Jun 5 16:35:49 ndnproxy: max. requests 14 132 [I] Jun 5 16:35:50 ndnproxy: max. requests 14 132 [I] Jun 5 16:35:51 pppd[5332]: pppd 2.4.4-4 started by root, uid 0 [I] Jun 5 16:35:52 ndm: Core::Debug: system debug disabled. [I] Jun 5 16:35:52 chat[5343]: report (Manufacturer) [I] Jun 5 16:35:52 chat[5343]: report (Model) [I] Jun 5 16:35:52 chat[5343]: report (Revision) [I] Jun 5 16:35:52 chat[5343]: report (MF192-) [I] Jun 5 16:35:52 chat[5343]: report (BD_MF) [I] Jun 5 16:35:52 chat[5343]: report (COPS:) [I] Jun 5 16:35:52 chat[5343]: send (ATZE1^M) [I] Jun 5 16:35:52 chat[5343]: expect (OK) [I] Jun 5 16:35:52 chat[5343]: ^M [I] Jun 5 16:35:52 chat[5343]: OK [I] Jun 5 16:35:52 chat[5343]: -- got it [I] Jun 5 16:35:52 chat[5343]: send (ATI^M) [I] Jun 5 16:35:52 chat[5343]: expect (OK) [I] Jun 5 16:35:52 chat[5343]: ^M [I] Jun 5 16:35:52 chat[5343]: ATI^M^M [I] Jun 5 16:35:52 chat[5343]: Manufacturer: huawei^M [I] Jun 5 16:35:52 chat[5343]: Model: E367^M [I] Jun 5 16:35:52 chat[5343]: Revision: 11.838.01.00.158^M [I] Jun 5 16:35:52 chat[5343]: IMEI: ***************^M [I] Jun 5 16:35:52 chat[5343]: +GCAP: +CGSM,+DS,+ES^M [I] Jun 5 16:35:52 chat[5343]: ^M [I] Jun 5 16:35:52 chat[5343]: OK [I] Jun 5 16:35:52 chat[5343]: -- got it [I] Jun 5 16:35:52 chat[5343]: send (AT+CGDCONT=1,"IP","internet.mts.ru"^M)
З.Ы. Self-test приложил в следующее скрытое сообщение!!!
-
9 часов назад, vasek00 сказал:
UConfig же переменные нужны для восстановления прошивки и для доступа к обновления на сервер обновлений.
проверил через консоль вроде бы все на месте, и серийник и сервистаг, но у меня не sernumb а zyxelsn=S************, все значения корректные и соответствуют тем, что на задней крышке, значит не в Uconfigе дело, из настроек только инет и wifi, значит дело в прошивке? я тогда собираю роутер? могу скинуть то что выдает по printenv в личку
Updated: сделал восстановление через Keenetic Recovery, затем сброс, обновление до последней стабильной 2.06. Обновился до 2.09 через вебморду файлом, затем сброс и обновился до последней 2.09.
В журнале сохраняются:
[E] Jan 1 00:00:07 ndm: Core::System::UConfig: recovery failed. [W] Jan 1 00:00:07 ndm: Core::Mode: the system started in the factory mode, "router" core mode selected. [C] Jun 3 14:10:45 ndm: EasyConfig::Manager: system failed [0xcffd0101]. [C] Jun 3 14:11:32 ndm: Core::Ndss: system failed [0xcffd0746], no serial. [W] Jan 1 03:00:48 ndm: UPnP::Manager: unable to read a serial number.
- 1
-
1 час назад, vasek00 сказал:
Вопрос только как он может слетать при прошивки
у меня вопрос: почему он слетает?
-
1 минуту назад, vasek00 сказал:
Просто проверить mtd1 там все видно.
ну у меня уровень познаний на уровне прошивальщика, могу через putty проверить параметры по printenv, если вы это имеете ввиду? в hex-редакторе не умею работать
-
1 час назад, vasek00 сказал:
А что ждать то
ждать, потому что в U-confige у меня серийный номер на месте, проверял в декабре 16 года когда после очередного обновления через вебморду у меня слетал сервистаг, все параметры сверял по задней крышке и сохранил по saveenv. Если номер слетел, значит проблема какая-то есть (в процессе обновления или железе, я не знаю этого), тем более я не один такой, у кого слетает u-config
З.Ы. Так то залезть в консоль недолго, UART-модуль рядом лежит, но все-таки хочу послушать что разрабы скажут
-
В 03.06.2017 в 18:34, vasek00 сказал:
Uconfig думаю имеет отношение к uboot configuration или он же U-Config
это я понял, но не хочется туда лезть, подождем что админы скажут
вот не перезагружал, ошибка вылезла после реконнекта usb-модема
Скрытый текстJun 03 23:27:48ndnproxymax. requests 14 132 Jun 03 23:27:48ndmCore::Scgi::Session: unsupported method "HEAD" for "/ci/self-test.txt". Jun 03 23:27:49ndnproxymax. requests 14 132 Jun 03 23:27:50pppd[16224]pppd 2.4.4-4 started by root, uid 0 Jun 03 23:27:50ndmHotspot::Manager: New neighbour: IP: 192.168.1.46, MAC: *****************, Interface: Bridge0. Jun 03 23:27:50ndmHotspot::Manager: ARP Entries dump. Jun 03 23:27:50ndmHotspot::Manager: 0: IP: 192.168.1.52, MAC: *****************, Interface: Bridge0, Age: 16 s. Jun 03 23:27:50ndmHotspot::Manager: 1: IP: 192.168.1.37, MAC: *****************, Interface: Bridge0, Age: 21 s. Jun 03 23:27:50ndmHotspot::Manager: 2: IP: 192.168.1.46, MAC: *****************, Interface: Bridge0, Age: 0 s. Jun 03 23:27:50ndmHotspot::Manager: 3: IP: 192.168.1.33, MAC: *****************8, Interface: Bridge0, Age: 15 s. Jun 03 23:27:51ndnproxyupdating configuration... Jun 03 23:27:51ndnproxyload config file: /var/ndnproxymain.conf Jun 03 23:27:51ndnproxyset profile for ip 127.0.0.1 0 Jun 03 23:27:51ndhcps__loop. remaining timeout: 1157 Jun 03 23:27:51ndnproxyset profile for ip ::1 0 Jun 03 23:27:51ndhcps__loop. remaining timeout: 1168 Jun 03 23:27:51chat[16232]report (Manufacturer) Jun 03 23:27:51chat[16232]report (Model) Jun 03 23:27:51chat[16232]report (Revision) Jun 03 23:27:51chat[16232]report (MF192-) Jun 03 23:27:51chat[16232]report (BD_MF) Jun 03 23:27:51chat[16232]report (COPS:) Jun 03 23:27:51chat[16232]send (ATZE1^M) Jun 03 23:27:51ndhcpsNDM DHCP server stopped (exit status: 0). Jun 03 23:27:51ndhcpsNDM DHCP server stopped (exit status: 0). Jun 03 23:27:51chat[16232]expect (OK) Jun 03 23:27:51chat[16232]^M Jun 03 23:27:51chat[16232]OK Jun 03 23:27:51chat[16232] -- got it Jun 03 23:27:51chat[16232]send (ATI^M) Jun 03 23:27:51chat[16232]expect (OK) Jun 03 23:27:51chat[16232]^M Jun 03 23:27:51chat[16232]ATI^M^M Jun 03 23:27:51chat[16232]Manufacturer: huawei^M Jun 03 23:27:51chat[16232]Model: E367^M Jun 03 23:27:51chat[16232]Revision: 11.838.01.00.158^M Jun 03 23:27:51chat[16232]IMEI: ***************^M Jun 03 23:27:51chat[16232]+GCAP: +CGSM,+DS,+ES^M Jun 03 23:27:51chat[16232]^M Jun 03 23:27:51chat[16232]OK Jun 03 23:27:51chat[16232] -- got it Jun 03 23:27:51chat[16232]send (AT+CGDCONT=1,"IP","internet.mts.ru"^M) Jun 03 23:27:51chat[16232]expect (OK) Jun 03 23:27:51chat[16232]^M Jun 03 23:27:51chat[16232]AT+CGDCONT=1,"IP","internet.mts.ru"^M^M Jun 03 23:27:51chat[16232]OK Jun 03 23:27:51chat[16232] -- got it Jun 03 23:27:51chat[16232]send (AT+COPS?^M) Jun 03 23:27:51chat[16232]expect (OK) Jun 03 23:27:51chat[16232]^M Jun 03 23:27:51chat[16232]AT+COPS?^M^M Jun 03 23:27:51chat[16232]+COPS: 0,2,"25001",2^M Jun 03 23:27:51chat[16232]^M Jun 03 23:27:51chat[16232]OK Jun 03 23:27:51chat[16232] -- got it Jun 03 23:27:52pppd[16224]Exit. Jun 03 23:27:52ndmNetwork::Interface::Base: "UsbModem0": interface is up. Jun 03 23:27:53ndhcpsNDM DHCP server (version 3.2.11) started. Jun 03 23:27:53ndhcpsNDM DHCP server (version 3.2.11) started. Jun 03 23:27:53ndmCore::Server: started Session /var/run/ndm.core.socket. Jun 03 23:27:53ndmCore::Server: client disconnected. Jun 03 23:27:53ndmCore::Server: started Session /var/run/ndm.core.socket. Jun 03 23:27:53ndmCore::Server: client disconnected. Jun 03 23:27:58pppd[16240]pppd 2.4.4-4 started by root, uid 0 Jun 03 23:27:59chat[16245]report (Manufacturer) Jun 03 23:27:59chat[16245]report (Model) Jun 03 23:27:59chat[16245]report (Revision) Jun 03 23:27:59chat[16245]report (MF192-) Jun 03 23:27:59chat[16245]report (BD_MF) Jun 03 23:27:59chat[16245]report (COPS:) Jun 03 23:27:59chat[16245]send (ATZE1^M) Jun 03 23:27:59chat[16245]expect (OK) Jun 03 23:27:59chat[16245]ATZE1^M^M Jun 03 23:27:59chat[16245]OK Jun 03 23:27:59chat[16245] -- got it Jun 03 23:27:59chat[16245]send (ATI^M) Jun 03 23:27:59chat[16245]expect (OK) Jun 03 23:27:59chat[16245]^M Jun 03 23:27:59chat[16245]ATI^M^M Jun 03 23:27:59chat[16245]Manufacturer: huawei^M Jun 03 23:27:59chat[16245]Model: E367^M Jun 03 23:27:59chat[16245]Revision: 11.838.01.00.158^M Jun 03 23:27:59chat[16245]IMEI: ***************^M Jun 03 23:27:59chat[16245]+GCAP: +CGSM,+DS,+ES^M Jun 03 23:27:59chat[16245]^M Jun 03 23:27:59chat[16245]OK Jun 03 23:27:59chat[16245] -- got it Jun 03 23:27:59chat[16245]send (AT+CGDCONT=1,"IP","internet.mts.ru"^M) Jun 03 23:27:59chat[16245]expect (OK) Jun 03 23:27:59chat[16245]^M Jun 03 23:27:59chat[16245]AT+CGDCONT=1,"IP","internet.mts.ru"^M^M Jun 03 23:27:59chat[16245]OK Jun 03 23:27:59chat[16245] -- got it Jun 03 23:27:59chat[16245]send (AT+COPS?^M) Jun 03 23:27:59chat[16245]expect (OK) Jun 03 23:27:59chat[16245]^M Jun 03 23:27:59chat[16245]AT+COPS?^M^M Jun 03 23:27:59chat[16245]+COPS: 0,2,"25001",2^M Jun 03 23:27:59chat[16245]^M Jun 03 23:27:59chat[16245]OK Jun 03 23:27:59chat[16245] -- got it Jun 03 23:27:59pppd[16240]Serial port initialized. Jun 03 23:27:59chat[16247]abort on (NO CARRIER) Jun 03 23:27:59chat[16247]abort on (NO DIALTONE) Jun 03 23:27:59chat[16247]abort on (NO DIAL TONE) Jun 03 23:27:59chat[16247]abort on (BUSY) Jun 03 23:27:59chat[16247]abort on (VOICE) Jun 03 23:27:59chat[16247]abort on (FCLASS) Jun 03 23:27:59chat[16247]abort on (NO ANSWER) Jun 03 23:27:59chat[16247]send (ATD*99#^M) Jun 03 23:27:59chat[16247]expect (CONNECT) Jun 03 23:27:59chat[16247]^M Jun 03 23:27:59chat[16247]ATD*99#^M^M Jun 03 23:27:59chat[16247]CONNECT Jun 03 23:27:59chat[16247] -- got it Jun 03 23:27:59pppd[16240]Serial connection established. Jun 03 23:27:59pppd[16240]Using interface ppp0 Jun 03 23:27:59pppd[16240]Connect: ppp0 <--> /dev/ttyUSB0 Jun 03 23:28:00pppd[16240]CHAP authentication succeeded Jun 03 23:28:00pppd[16240]CHAP authentication succeeded Jun 03 23:28:02pppd[16240]Could not determine remote IP address: defaulting to 10.64.64.64 Jun 03 23:28:02pppd[16240]local IP address 10.172.21.133 Jun 03 23:28:02pppd[16240]remote IP address 10.64.64.64 Jun 03 23:28:02pppd[16240]primary DNS address 217.8.235.225 Jun 03 23:28:02pppd[16240]secondary DNS address 217.8.235.241 Jun 03 23:28:02ndmNetwork::Interface::Base: "UsbModem0": interface is up. Jun 03 23:28:02ndmNetwork::Interface::Base: "UsbModem0": interface is up. Jun 03 23:28:02ndmNetwork::Interface::PPP: interface "UsbModem0" is global, priority 300. Jun 03 23:28:02ndmNetwork::Interface::PPP: "UsbModem0": adding default route via UsbModem0. Jun 03 23:28:02ndmNetwork::Interface::PPP: adding nameserver 217.8.235.225. Jun 03 23:28:02ndmDns::Manager: name server 217.8.235.225 added, domain (default). Jun 03 23:28:02ndmNetwork::Interface::PPP: adding nameserver 217.8.235.241. Jun 03 23:28:02ndmDns::Manager: name server 217.8.235.241 added, domain (default). Jun 03 23:28:02ndmNetwork::Interface::IP: "UsbModem0": IP address is 10.172.21.133/32. Jun 03 23:28:02ndmNetwork::Interface::UsbModem: reading statistics from: ttyUSB1. Jun 03 23:28:02ndmUPnP::Manager: unable to read a serial number. Jun 03 23:28:04ndmCore::Server: started Session /var/run/ndm.core.socket. Jun 03 23:28:04upnpHTTP listening on port 57745 Jun 03 23:28:04upnpListening for NAT-PMP/PCP traffic on port 5351 Jun 03 23:28:10ndmEasyConfig::Manager: system failed [0xcffd0101]. Jun 03 23:28:42ndmCore::Ndss: system failed [0xcffd0746], no serial.
-
32 минуты назад, AndreBA сказал:
С "полным" сбросом перепрошились?
вот с полным сбросом
Jun 03 12:26:29ndmEasyConfig::Manager: system failed [0xcffd0101]. Jun 03 12:26:56ndmCore::Ndss: system failed [0xcffd0746], no serial.
-
обновил, тоже самое
Jun 03 00:29:57upnpListening for NAT-PMP/PCP traffic on port 5351 Jun 03 00:30:03ndmNtp::Client: invalid server "0.pool.ntp.org", trying next. Jun 03 00:30:03ndmNtp::Client: could not synchronize, waiting... Jun 03 00:30:04ndmEasyConfig::Manager: system failed [0xcffd0101]. Jun 03 15:56:31ndmCore::System::Clock: system time has been changed. Jun 03 15:56:31ndmNtp::Client: time synchronized with "0.pool.ntp.org". Jun 03 15:56:31pppd[374]System time change detected. Jun 03 15:56:47ndmCore::Ndss: system failed [0xcffd0746], no serial.
-
После обновления Keenetic II до 2.09.B.0.0-0 в журнале появились записи о новых ошибках, на 2.09.A.9.0-0 их не было
[E] Jan 1 00:00:07 ndm: Core::System::UConfig: recovery failed. [W] Jan 1 00:00:07 ndm: Core::Mode: the system started in the factory mode, "router" core mode selected. [C] Jun 3 14:10:45 ndm: EasyConfig::Manager: system failed [0xcffd0101]. [C] Jun 3 14:11:32 ndm: Core::Ndss: system failed [0xcffd0746], no serial.
появляются периодически после рестарта
при переходе Wi-Fi точки доступа на стандарт 802.11n клиенты теряют сеть и перестают к ней подключаться
in 2.10
Posted · Edited by Dhampir113
добавил
вот снова клиенты сами отвалились:
Jun 11 00:29:59wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had deauthenticated. Jun 11 00:30:08wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) had associated successfully. Jun 11 00:30:10wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) replay counter differs in key handshaking. Jun 11 00:30:10wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:0a:f5:11:4f:08) set key done in WPA2/WPA2PSK. Jun 11 00:30:10ndhcpsDHCPDISCOVER received from 00:0a:f5:11:4f:08. Jun 11 00:30:10ndhcpsmaking OFFER of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 11 00:30:10ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.33 from 00:0a:f5:11:4f:08. Jun 11 00:30:10ndhcpssending ACK of 192.168.1.33 to 00:0a:f5:11:4f:08. Jun 11 00:36:22wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) had associated successfully. Jun 11 00:36:23wmondWifiMaster0/AccessPoint0: (RT2860) STA(84:a6:c8:57:37:5d) set key done in WPA2/WPA2PSK. Jun 11 00:36:23ndhcpsDHCPDISCOVER received from 84:a6:c8:57:37:5d. Jun 11 00:36:23ndhcpsmaking OFFER of 192.168.1.62 to 84:a6:c8:57:37:5d. Jun 11 00:36:23ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.62 from 84:a6:c8:57:37:5d. Jun 11 00:36:23ndhcpssending ACK of 192.168.1.62 to 84:a6:c8:57:37:5d. Jun 11 00:36:58ndhcpsDHCPREQUEST received (STATE_RENEWING) for 192.168.1.37 from 00:87:01:19:64:d4. Jun 11 00:36:58ndhcpssending ACK of 192.168.1.37 to 00:87:01:19:64:d4.
Привязки MAC-IP нету, перевел на сегмент 192.168.3.1. Буду наблюдать
я все сюда подытожил
З.Ы. В личку скинул конфиг и селфтест