[4.0 Alpha 12: lock precedence violation: CLOCK (105) after SCHEDULE (208)]

26 минут назад, AJ_ сказал:

Mar  8 17:20:48 ndhcps
Info: sending ACK of 192.168.1.94 to 80:35:c1:37:35:d5.

Mar  8 17:20:48 ndhcps
Info: DHCPREQUEST received (STATE_SELECTING) for 192.168.1.94 from 80:35:c1:37:35:d5.

Mar  8 17:20:48 ndhcps
Info: making OFFER of 192.168.1.94 to 80:35:c1:37:35:d5.

Mar  8 17:20:48 ndhcps
Info: DHCPDISCOVER received from 80:35:c1:37:35:d5.

Mar  8 17:20:47 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(80:35:c1:37:35:d5) set key done in WPA2/WPA2PSK.

Mar  8 17:20:47 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(80:35:c1:37:35:d5) had associated successfully.

Mar  8 17:20:47 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(80:35:c1:37:35:d5) had associated successfully.

Mar  8 17:20:35 ndhcps
Info: sending ACK of 192.168.1.54 to d4:25:8b:ba:0b:ad.

Mar  8 17:20:35 ndhcps
Info: DHCPREQUEST received (STATE_INIT) for 192.168.1.54 from d4:25:8b:ba:0b:ad.

Mar  8 17:20:35 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(d4:25:8b:ba:0b:ad) set key done in WPA2/WPA2PSK.

Mar  8 17:20:35 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(d4:25:8b:ba:0b:ad) had associated successfully.

Mar  8 17:20:30 ndhcps
Info: sending ACK of 192.168.1.85 to 00:15:99:a0:d1:a4.

Mar  8 17:20:29 ndhcps
Info: DHCPREQUEST received (STATE_SELECTING) for 192.168.1.85 from 00:15:99:a0:d1:a4.

Mar  8 17:20:29 ndhcps
Info: making OFFER of 192.168.1.85 to 00:15:99:a0:d1:a4.

Mar  8 17:20:29 ndhcps
Info: DHCPDISCOVER received for 169.254.183.68 from 00:15:99:a0:d1:a4.

Mar  8 17:20:27 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:15:99:a0:d1:a4) set key done in WPA2/WPA2PSK.

Mar  8 17:20:27 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:15:99:a0:d1:a4) had re-associated successfully.

Mar  8 17:20:21 ndhcps
Info: sending ACK of 192.168.1.76 to 00:08:22:d0:bb:fb.

Mar  8 17:20:21 ndhcps
Info: DHCPREQUEST received (STATE_INIT) for 192.168.1.76 from 00:08:22:d0:bb:fb.

Mar  8 17:20:21 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) set key done in WPA3/WPA3PSK.

Mar  8 17:20:21 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) had associated successfully.

Mar  8 17:20:21 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:20 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:15:99:a0:d1:a4) had deauthenticated by AP (reason: PTK 4-way handshake timeout).

Mar  8 17:20:20 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:15:99:a0:d1:a4) pairwise key handshaking timeout (msg 1 of 4-way).

Mar  8 17:20:18 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) association rejected because PMKID expired or invalid.

Mar  8 17:20:18 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:18 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) association rejected because PMKID expired or invalid.

Mar  8 17:20:18 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:18 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) association rejected because PMKID expired or invalid.

Mar  8 17:20:18 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:17 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) association rejected because PMKID expired or invalid.

Mar  8 17:20:17 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:17 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) association rejected because PMKID expired or invalid.

Mar  8 17:20:17 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:17 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) association rejected because PMKID expired or invalid.

Mar  8 17:20:17 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:16 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) association rejected because PMKID expired or invalid.

Mar  8 17:20:16 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:16 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) association rejected because PMKID expired or invalid.

Mar  8 17:20:16 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:08:22:d0:bb:fb) SAE handshake completed, PWE method: H2E.

Mar  8 17:20:11 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:15:99:a0:d1:a4) had associated successfully.

Mar  8 17:20:06 ndm
Error: Core::Configurator: cloud control2 subscribe system: EULA not accepted [coala/rci].

Mar  8 17:20:06 ndm
Error: Core::Configurator: cloud control2 subscribe stats: EULA not accepted [coala/rci].

Mar  8 17:20:06 ndm
Error: Core::Syslog: last message repeated 4 times.

Mar  8 17:20:06 ndm
Error: Core::Configurator: cloud control2 subscribe event: EULA not accepted [coala/rci].

Mar  8 17:20:00 ndm
Info: Core::Session: client disconnected.

Mar  8 17:20:00 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Mar  8 17:20:00 ndm
Info: Http::Manager: updated configuration.

Mar  8 17:20:00 ndm
Info: Core::Session: client disconnected.

Mar  8 17:20:00 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Mar  8 17:20:00 ndm
Info: Http::Nginx: loaded SSL certificate for "35d5cbb291a97f7906dc37d9.keenetic.io".

Mar  8 17:19:59 ndm
Info: Dns::Manager: added static record for "35d5cbb291a97f7906dc37d9.keenetic.io", address 78.47.125.180.

Mar  8 17:19:56 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": BSS(ra0) channel switched to 3.

Mar  8 17:19:56 kernel
Info: ACS result: primary channel 3, 40 MHz spectrum min dirty (with CCA) = 2113

Mar  8 17:19:54 ndm
Info: Ntp::Client: time synchronized.

Mar  8 17:19:54 ndm
Info: Core::System::Clock: system time has been changed.

Feb 17 21:41:01 upnp
Info: Listening for NAT-PMP/PCP traffic on port 5351

Feb 17 21:41:01 upnp
Info: HTTP listening on port 1900

Feb 17 21:41:01 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Feb 17 21:41:01 ndm
Info: Core::System::DriverManager: loading /lib/modules/4.9-ndm-5/nf_nat_ftp.ko.

Feb 17 21:41:01 ndm
Info: Core::System::DriverManager: loading /lib/modules/4.9-ndm-5/nf_conntrack_ftp.ko.

Feb 17 21:41:01 nimproxy
Info: NDM IGMP/Multicast Proxy, v0.0.36.

Feb 17 21:41:00 ndm
Info: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(00:15:99:a0:d1:a4) had associated successfully.

Feb 17 21:41:00 ndm
Info: Core::Session: client disconnected.

Feb 17 21:41:00 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Feb 17 21:41:00 ndm
Info: Http::Manager: updated configuration.

Feb 17 21:40:59 ndm
Info: Core::Session: client disconnected.

Feb 17 21:40:59 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Feb 17 21:40:59 ndm
Info: Http::Nginx: loaded SSL certificate for "35d5cbb291a97f7906dc37d9.keenetic.io".

Feb 17 21:40:59 ndm
Info: Network::InternetChecker: Internet access detected.

Feb 17 21:40:59 ndm
Info: PingCheck::Profile: "default": restore connected state.

Feb 17 21:40:59 kernel
Info: capability: warning: `nginx' uses 32-bit capabilities (legacy support in use)

Feb 17 21:40:59 ndm
Info: Network::InterfaceFlusher: flushed conntrack and route cache.

Feb 17 21:40:59 ndm
Info: Core::Session: client disconnected.

Feb 17 21:40:59 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Feb 17 21:40:58 nimproxy
Info: NDM IGMP/Multicast proxy stopped (exit status: 0).

Feb 17 21:40:58 ndm
Info: Network::Interface::Base: "FastEthernet0/Vlan2": "dhcp-client" changed "ipv4" layer state "pending" to "running".

Feb 17 21:40:58 ndm
Warning: Dns::Manager: name server 5.3.3.3 is disregarded while public is active.

Feb 17 21:40:58 ndm
Info: Dhcp::Client: adding name server 5.3.3.3.

Feb 17 21:40:58 ndm
Info: Dhcp::Client: adding a host route to name server 5.3.3.3.

Feb 17 21:40:58 ndm
Warning: Dns::Manager: name server 109.195.144.3 is disregarded while public is active.

Feb 17 21:40:58 ndm
Info: Dhcp::Client: adding name server 109.195.144.3.

Feb 17 21:40:58 ndm
Info: Dhcp::Client: adding a host route to name server 109.195.144.3.

Feb 17 21:40:58 ndm
Info: Dhcp::Client: adding a default route via 37.113.227.254.

Feb 17 21:40:58 ndm
Info: Dhcp::Client: interface "ISP" is global, priority 32767.

Feb 17 21:40:58 ndm
Info: Dhcp::Client: obtained IP address 37.113.227.131/22.

Feb 17 21:40:58 ndm
Info: Network::Interface::Ip: "FastEthernet0/Vlan2": IP address is 37.113.227.131/22.

Feb 17 21:40:58 ndm
Info: Dhcp::Client: configuring interface ISP.

Feb 17 21:40:58 ndhcpc
Info: FastEthernet0/Vlan2: received ACK for 37.113.227.131 from 109.195.144.70 lease 600 sec.

Feb 17 21:40:58 ndhcpc
Info: FastEthernet0/Vlan2: received OFFER for 37.113.227.131 from 109.195.144.70.

Feb 17 21:40:58 kernel
Info: br0: port 2(ra0) entered forwarding state

Feb 17 21:40:58 kernel
Info: br0: port 2(ra0) entered blocking state

Feb 17 21:40:57 kernel
Info: MT7628 Andes FW Version: 1, Build: 20180704090333, Length: 64812

Feb 17 21:40:57 kernel
Info: br0: port 2(ra0) entered disabled state

Feb 17 21:40:56 ndm
Info: Core::System::DriverManager: loading /lib/modules/4.9-ndm-5/nf_nat_sip.ko.

Feb 17 21:40:56 ndm
Info: Core::System::DriverManager: loading /lib/modules/4.9-ndm-5/nf_conntrack_sip.ko.

Feb 17 21:40:56 kernel
Info: fastvpn: Fast VPN init, v6.0-19

Feb 17 21:40:56 kernel
Info: fastvpn: enabled

Feb 17 21:40:56 kernel
Info: fastvpn: registered

Feb 17 21:40:56 kernel
Info: fastvpn: sizeof(hashent) = 88

Feb 17 21:40:56 kernel
Info: fastvpn: sizeof(bind) = 264

Feb 17 21:40:56 ndhcpc
Info: FastEthernet0/Vlan2: created PID file "/var/run/ndhcpc-eth2.2.pid".

Feb 17 21:40:56 ndhcpc
Info: FastEthernet0/Vlan2: NDM DHCP Client, v3.2.51.

Feb 17 21:40:56 ndm
Info: Core::System::DriverManager: loading /lib/modules/4.9-ndm-5/fastvpn.ko.

Feb 17 21:40:56 nimproxy
Info: NDM IGMP/Multicast Proxy, v0.0.36.

Feb 17 21:40:56 ndm
Info: Http::Manager: updated configuration.

Feb 17 21:40:56 ndm
Info: Core::Session: client disconnected.

Feb 17 21:40:56 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Feb 17 21:40:56 ndm
Info: Core::Session: client disconnected.

Feb 17 21:40:56 ndhcps
Info: NDM DHCP Server, v3.2.51.

Feb 17 21:40:56 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Feb 17 21:40:56 ndhcps
Info: NDM DHCP Server, v3.2.51.

Feb 17 21:40:56 wind
Info: version 1.0.3 started on br0.

Feb 17 21:40:56 coalagent
Info: version 0.4.51 starting on 192.168.1.1.

Feb 17 21:40:55 mtkiappd
Info: MediaTek IAPP daemon v2.0.10 started on br1.

Feb 17 21:40:55 mtkiappd
Info: MediaTek IAPP daemon v2.0.10 started on br0.

Feb 17 21:40:55 telnetd
Info: waiting for connections...

Feb 17 21:40:55 ndm
Info: Core::Session: client disconnected.

Feb 17 21:40:55 ndm
Info: Core::Server: started Session /var/run/ndm.core.socket.

Feb 17 21:40:54 ndm
Info: Http::Nginx: loaded SSL certificate for "35d5cbb291a97f7906dc37d9.keenetic.io".

Feb 17 21:40:53 ndm
Info: Network::Interface::Base: "FastEthernet0/Vlan2": "ethernet" changed "link" layer state "pending" to "running".

Feb 17 21:40:53 ndm
Info: Network::Interface::Base: "FastEthernet0": "ethernet" changed "link" layer state "pending" to "running".

Feb 17 21:40:53 ndm
Info: Network::Interface::Base: "FastEthernet0/0": "ethernet" changed "link" layer state "pending" to "running".

Feb 17 21:40:53 ndm
Info: Network::Interface::Switch: "FastEthernet0/0": switch link up at port 0 (100FD/AN).

Feb 17 21:40:53 ndm
Info: Network::Interface::Mtk::WifiMaster: "WifiMaster0": auto channel mode set.

Feb 17 21:40:53 ndm
Info: Core::System::DriverManager: loading /lib/modules/4.9-ndm-5/igmpsn.ko.

Feb 17 21:40:53 ndm
Info: Http::Manager: disabled NDMP passthrough.

Feb 17 21:40:53 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": peer isolation enabled.

Feb 17 21:40:53 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint0": peer isolation disabled.

Feb 17 21:40:52 ndm
Info: Core::Server: system ready, core startup time is 26 seconds.

Feb 17 21:40:53 kernel
Info: igmpsn: NDM IGMP Switch Snooping Module, v4.3.3

Feb 17 21:40:53 kernel
Info: br1: port 3(ra4.2) entered forwarding state

Feb 17 21:40:53 kernel
Info: br1: port 3(ra4.2) entered blocking state

Feb 17 21:40:53 kernel
Info: device ra4.2 entered promiscuous mode

Feb 17 21:40:53 kernel
Info: br1: port 3(ra4.2) entered disabled state

Feb 17 21:40:53 kernel
Info: br1: port 3(ra4.2) entered blocking state

Feb 17 21:40:53 kernel
Info: br0: port 3(ra4.1) entered forwarding state

Feb 17 21:40:53 kernel
Info: br0: port 3(ra4.1) entered blocking state

Feb 17 21:40:53 kernel
Info: device ra4 entered promiscuous mode

Feb 17 21:40:53 kernel
Info: device ra4.1 entered promiscuous mode

Feb 17 21:40:53 kernel
Info: br0: port 3(ra4.1) entered disabled state

Feb 17 21:40:53 kernel
Info: br0: port 3(ra4.1) entered blocking state

Feb 17 21:40:52 ndm
Info: CloudControl2::Agent: security level unchanged.

Feb 17 21:40:52 ndm
Info: Components::Manager: auto-update channel is "draft".

Feb 17 21:40:52 ndm
Info: EasyConfig::Manager: disabled.

Feb 17 21:40:52 ndm
Info: Network::InternetChecker: a new maximum fail count set to 4.

Feb 17 21:40:52 ndm
Info: Network::InternetChecker: a new check period set to 15 seconds.

Feb 17 21:40:52 ndm
Info: Dns::Filter::Public: enabled.

Feb 17 21:40:52 ndm
Info: Dns::Manager: proxy reload.

Feb 17 21:40:52 ndm
Info: Dns::Manager: enable DNS filter engine "public".

Feb 17 21:40:52 ndm
Info: Dns::Filter::Public: associated interface "Home" with preset "cloudflare-malware".

Feb 17 21:40:52 ndm
Info: Dns::Manager: enabled rebind protection.

Feb 17 21:40:52 ndm
Info: Ntp::Client: NTP service enabled.

Feb 17 21:40:52 ndm
Info: Ntp::Server: enabled.

Feb 17 21:40:52 ndm
Info: Telnet::Server: telnet server enabled.

Feb 17 21:40:52 ndm
Info: Http::Manager: HTTP service was enabled.

Feb 17 21:40:52 ndm
Info: Igmp::Proxy: IGMP proxy enabled.

Feb 17 21:40:52 ndm
Info: Dns::Manager: DNS proxy enabled.

Feb 17 21:40:52 ndm
Info: Dhcp::Server: service enabled.

Feb 17 21:40:52 ndm
Info: UPnP::Manager: using LAN interface: Bridge0.

Feb 17 21:40:52 ndm
Info: Network::Interface::Mtk::Ppe: software PPE enabled.

Feb 17 21:40:52 ndm
Info: Hotspot::Manager: rule "permit" applied to host "00:08:22:d0:bb:fb".

Feb 17 21:40:52 ndm
Info: Hotspot::Manager: rule "permit" applied to host "b8:94:e7:d0:b4:94".

Feb 17 21:40:52 ndm
Info: Hotspot::Manager: rule "permit" applied to host "7c:ed:8d:a4:f5:a0".

Feb 17 21:40:52 ndm
Info: Hotspot::Manager: rule "permit" applied to host "d4:25:8b:ba:0b:ad".

Feb 17 21:40:52 ndm
Info: Hotspot::Manager: rule "permit" applied to host "80:35:c1:37:35:d5".

Feb 17 21:40:52 ndm
Info: Hotspot::Manager: rule "permit" applied to host "00:15:99:a0:d1:a4".

Feb 17 21:40:52 ndm
Info: Hotspot::Manager: policy "permit" applied to interface "Guest".

Feb 17 21:40:52 ndm
Info: Telnet::Server: bruteforce detection is reconfigured.

Feb 17 21:40:52 ndm
Info: Telnet::Server: security level unchanged.

Feb 17 21:40:52 ndm
Info: Network::Nat: a NAT rule added.

Feb 17 21:40:52 ndm
Info: Network::Nat: a NAT rule added.

Feb 17 21:40:52 ndm
Info: Http::Manager: enabled SSL redirect.

Feb 17 21:40:52 ndm
Info: Http::Manager: enabled SSL service.

Feb 17 21:40:52 ndm
Info: Http::Manager: bruteforce detection is reconfigured.

Feb 17 21:40:52 ndm
Info: Http::Manager: bruteforce detection is enabled.

Feb 17 21:40:52 ndm
Info: Http::Manager: security level set to private.

Feb 17 21:40:52 ndm
Info: Dhcp::Server: pool "_WEBADMIN_GUEST_AP" is enabled.

Feb 17 21:40:52 ndm
Info: Dhcp::Server: pool "_WEBADMIN_GUEST_AP" bound to interface Guest.

Feb 17 21:40:52 ndm
Info: Dhcp::Pool: "_WEBADMIN_GUEST_AP": set lease time: 25200 seconds.

Feb 17 21:40:52 ndm
Info: Dhcp::Pool: "_WEBADMIN_GUEST_AP": assigned IP address range 10.1.30.33 to 10.1.30.152.

Feb 17 21:40:52 ndm
Info: Dhcp::Server: pool "_WEBADMIN" is enabled.

Feb 17 21:40:52 ndm
Info: Dhcp::Server: pool "_WEBADMIN" bound to interface Home.

Feb 17 21:40:52 ndm
Info: Dhcp::Pool: "_WEBADMIN": assigned IP address range 192.168.1.33 to 192.168.1.152.

Feb 17 21:40:52 ndm
Info: Network::Interface::Base: "Bridge1": interface is up.

Feb 17 21:40:52 ndm
Info: Network::Interface::Mtk::Iapp: Bridge1 key applied.

Feb 17 21:40:52 ndm
Info: Igmp::Proxy: added downstream interface Bridge1.

Feb 17 21:40:52 ndm
Info: Dhcp::Client: Bridge1 DHCP name servers are enabled.

Feb 17 21:40:52 ndm
Info: Dhcp::Client: Bridge1 DHCP client DNS host routes are enabled.

Feb 17 21:40:52 ndm
Info: Network::Interface::Ip: "Bridge1": IP address is 10.1.30.1/24.

Feb 17 21:40:52 ndm
Info: Network::Interface::Mac: "Bridge1": MAC address is 52:ff:20:29:89:9d.

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered forwarding state

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered blocking state

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered disabled state

Feb 17 21:40:52 ndm
Info: Network::Interface::Mac: "Bridge1": backed up the default address 52:ff:20:19:89:9e of "Guest" before changing.

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered forwarding state

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered blocking state

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered disabled state

Feb 17 21:40:52 ndm
Info: Network::Interface::Mac: "FastEthernet0/Vlan3": backed up the default address 50:ff:20:29:89:9e of "FastEthernet0/Vlan3" before changing.

Feb 17 21:40:52 ndm
Info: Network::Interface::Bridge: "Bridge1": set enhanced address "52:ff:20:29:89:9d".

Feb 17 21:40:52 ndm
Info: Network::Interface::L3Base: "Bridge1": security level set to "protected".

Feb 17 21:40:52 ndm
Info: Network::Interface::EthernetIp: "Bridge1": peer isolation enabled.

Feb 17 21:40:52 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": peer isolation enabled.

Feb 17 21:40:52 ndm
Info: Network::Interface::EthernetIp: "Bridge1": ACL type unchanged.

Feb 17 21:40:52 ndm
Info: Network::Interface::Bridge: "Bridge1": GuestWiFi included.

Feb 17 21:40:52 kernel
Info: br1: disabled STP choke for port 2(ra1)

Feb 17 21:40:52 kernel
Info: device ra1 entered promiscuous mode

Feb 17 21:40:52 kernel
Info: br1: port 2(ra1) entered disabled state

Feb 17 21:40:52 kernel
Info: br1: port 2(ra1) entered blocking state

Feb 17 21:40:52 ndm
Info: Network::Interface::Bridge: "Bridge1": FastEthernet0/Vlan3 included.

Feb 17 21:40:52 kernel
Info: br1: disabled STP choke for port 1(eth2.3)

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered forwarding state

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered blocking state

Feb 17 21:40:52 kernel
Info: device eth2.3 entered promiscuous mode

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered disabled state

Feb 17 21:40:52 kernel
Info: br1: port 1(eth2.3) entered blocking state

Feb 17 21:40:52 ndm
Info: TrafficControl::Manager: "Bridge1" interface rate limited to 5120 kbit/s.

Feb 17 21:40:52 ndm
Info: Network::Interface::Base: "Bridge1": description saved.

Feb 17 21:40:52 ndm
Info: Network::Interface::Base: "Bridge1": renamed to "Guest".

Feb 17 21:40:51 ndm
Info: Network::Interface::Repository: "Bridge1" interface created.

Feb 17 21:40:51 ndm
Info: Network::Interface::Base: "Bridge1": interface is up.

Feb 17 21:40:51 ndm
Info: Network::Interface::Base: "Bridge1": "base" changed "conf" layer state "disabled" to "running".

Feb 17 21:40:51 ndm
Info: Network::Interface::Base: "Bridge1": network MTU reset to default.

Feb 17 21:40:51 ndm
Info: Network::Interface::Base: "Bridge1": interface is down.

Feb 17 21:40:51 ndm
Info: Network::Interface::Base: "Bridge0": interface is up.

Feb 17 21:40:51 ndm
Info: Network::Interface::Mtk::Iapp: Bridge0 key applied.

Feb 17 21:40:51 ndm
Info: Igmp::Proxy: added downstream interface Bridge0.

Feb 17 21:40:51 ndm
Info: Dhcp::Client: Bridge0 DHCP name servers are enabled.

Feb 17 21:40:51 ndm
Info: Dhcp::Client: Bridge0 DHCP client DNS host routes are enabled.

Feb 17 21:40:51 ndm
Info: Network::Interface::Ip: "Bridge0": IP address is 192.168.1.1/24.

Feb 17 21:40:51 ndm
Info: Network::Interface::L3Base: "Bridge0": security level set to "private".

Feb 17 21:40:51 ndm
Info: Network::Interface::EthernetIp: "Bridge0": ACL type unchanged.

Feb 17 21:40:51 ndm
Info: Network::Interface::Bridge: "Bridge0": AccessPoint included.

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered forwarding state

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered blocking state

Feb 17 21:40:51 kernel
Info: br0: port 2(ra0) entered forwarding state

Feb 17 21:40:51 kernel
Info: br0: port 2(ra0) entered blocking state

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered disabled state

Feb 17 21:40:51 kernel
Info: br0: port 2(ra0) entered disabled state

Feb 17 21:40:51 kernel
Info: br0: disabled STP choke for port 2(ra0)

Feb 17 21:40:51 kernel
Info: br0: port 2(ra0) entered forwarding state

Feb 17 21:40:51 kernel
Info: br0: port 2(ra0) entered blocking state

Feb 17 21:40:51 kernel
Info: device ra0 entered promiscuous mode

Feb 17 21:40:51 kernel
Info: br0: port 2(ra0) entered disabled state

Feb 17 21:40:51 kernel
Info: br0: port 2(ra0) entered blocking state

Feb 17 21:40:51 ndm
Info: Network::Interface::Bridge: "Bridge0": FastEthernet0/Vlan1 inherited in Bridge0.

Feb 17 21:40:51 ndm
Info: Network::Interface::Mac: "Bridge0": MAC address is 50:ff:20:29:89:9e.

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered forwarding state

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered blocking state

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered disabled state

Feb 17 21:40:51 ndm
Info: Network::Interface::Mac: "Bridge0": backed up the default address 50:ff:20:29:89:9e of "Home" before changing.

Feb 17 21:40:51 ndm
Info: Network::Interface::Ip: "Bridge0": IP address cleared.

Feb 17 21:40:51 ndm
Info: Network::Interface::Ip: "Bridge0": IP address cleared.

Feb 17 21:40:51 ndm
Info: Network::Interface::L3Base: "Bridge0": global priority cleared.

Feb 17 21:40:51 ndm
Info: Network::Interface::L3Base: "Bridge0": global priority unchanged.

Feb 17 21:40:51 ndm
Info: Network::Interface::Base: "Bridge0": interface is up.

Feb 17 21:40:51 kernel
Info: br0: disabled STP choke for port 1(eth2.1)

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered forwarding state

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered blocking state

Feb 17 21:40:51 kernel
Info: device eth2.1 entered promiscuous mode

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered disabled state

Feb 17 21:40:51 kernel
Info: br0: port 1(eth2.1) entered blocking state

Feb 17 21:40:51 ndm
Info: Network::Interface::Base: "Bridge0": description saved.

Feb 17 21:40:51 ndm
Info: Network::Interface::Base: "Bridge0": renamed to "Home".

Feb 17 21:40:50 ndm
Info: Network::Interface::Repository: "Bridge0" interface created.

Feb 17 21:40:50 ndm
Info: Network::Interface::Base: "Bridge0": interface is up.

Feb 17 21:40:50 ndm
Info: Network::Interface::Base: "Bridge0": "base" changed "conf" layer state "disabled" to "running".

Feb 17 21:40:50 ndm
Info: Network::Interface::Base: "Bridge0": network MTU reset to default.

Feb 17 21:40:50 ndm
Info: Network::Interface::Base: "Bridge0": interface is down.

Feb 17 21:40:49 ndm
Info: Network::Interface::Base: "WifiMaster0/WifiStation0": interface is down.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: WifiMaster0/WifiStation0 DHCP name servers are enabled.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: WifiMaster0/WifiStation0 DHCP client DNS host routes are enabled.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: started DHCP client on WifiMaster0/WifiStation0.

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::WifiStation: "WifiMaster0/WifiStation0": wireless encryption disabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::L3Base: "WifiMaster0/WifiStation0": security level set to "public".

Feb 17 21:40:49 ndm
Info: Network::Interface::Base: "WifiMaster0/AccessPoint3": interface is down.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: WifiMaster0/AccessPoint3 DHCP name servers are enabled.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: WifiMaster0/AccessPoint3 DHCP client DNS host routes are enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::L3Base: "WifiMaster0/AccessPoint3": security level set to "private".

Feb 17 21:40:49 ndm
Info: Network::Interface::EthernetIp: "WifiMaster0/AccessPoint3": ACL type unchanged.

Feb 17 21:40:49 ndm
Info: Network::Interface::Base: "WifiMaster0/AccessPoint2": interface is down.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: WifiMaster0/AccessPoint2 DHCP name servers are enabled.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: WifiMaster0/AccessPoint2 DHCP client DNS host routes are enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::L3Base: "WifiMaster0/AccessPoint2": security level set to "private".

Feb 17 21:40:49 ndm
Info: Network::Interface::EthernetIp: "WifiMaster0/AccessPoint2": ACL type unchanged.

Feb 17 21:40:49 ndm
Info: Network::Interface::Base: "WifiMaster0/AccessPoint1": interface is down.

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": fast transition enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": fast transition MDID set to "Nk".

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": BTM enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": RRM enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": WMM extensions enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::Wireless: "WifiMaster0/AccessPoint1": SSID saved.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: WifiMaster0/AccessPoint1 DHCP name servers are enabled.

Feb 17 21:40:49 ndm
Info: Dhcp::Client: WifiMaster0/AccessPoint1 DHCP client DNS host routes are enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": WPA3 enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": WPA2 enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::Mtk::AccessPoint: "WifiMaster0/AccessPoint1": wireless encryption enabled.

Feb 17 21:40:49 ndm
Info: Network::Interface::Wifi: "WifiMaster0/AccessPoint1": WPA PSK set.

Feb 17 21:40:49 ndm
Info: Network::Interface::L3Base: "WifiMaster0/AccessPoint1": security level set to "protected".

Feb 17 21:40:49 ndm
Info: Network::Interface::EthernetIp: "WifiMaster0/AccessPoint1": ACL type unchanged.

Спрячьте пожалуйста эту "портянку"(без обид) под спойлер. 

[4.0 Alpha 12: lock precedence violation: CLOCK (105) after SCHEDULE (208)]

2 часа назад, vasek00 сказал:

И не только системный монитор, как то весь WEB "тупит" при переходе между разделами,

Есть такое....

[4.0 Alpha 12: lock precedence violation: CLOCK (105) after SCHEDULE (208)]

3 минуты назад, ant76 сказал:

У меня тоже попросил это, выбрал и принял соглашение.

Тоже выбрал и согласился.

[4.0 Alpha 12: lock precedence violation: CLOCK (105) after SCHEDULE (208)]

При обновлении на 4.0.12 запросил запрос о стране регистрации и лицензионном соглашении:

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

Может это связанно с записями в лог (приведенными постом выше).

 

[4.0 Alpha 12: lock precedence violation: CLOCK (105) after SCHEDULE (208)]

После обновления  на Версия ОС 4.0 Alpha 12, открытия окна "Системный монитор" происходит с задержкой в несколько секунд. При этом в журнале появляются записи:

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

Мар 8 08:09:22

 

ndm

Thread: "Queue::HHZQJGQWVTEQXIXV::http/rci": lock precedence violation: CLOCK (105) after SCHEDULE (208).

Мар 8 08:09:22

 

ndm

Thread: "Queue::HHZQJGQWVTEQXIXV::http/rci" (1165) backtrace:

Мар 8 08:09:22

 

ndm

Thread: Core::System::Clock::GetTime() const+0x30

Мар 8 08:09:22

 

ndm

Thread: Core::Schedule::Object_::GetTime_(unsigned int&, unsigned int&, unsigned int&, unsigned int&) const+0x4c

Мар 8 08:09:22

 

ndm

Thread: Core::Schedule::Object_::AttachTo(Xml::Node&) const+0x25c

Мар 8 08:09:22

 

ndm

Thread: Core::Schedule::Manager::AttachScheduleTo(CString const&, Xml::Node&) const+0xd8

Мар 8 08:09:22

 

ndm

Thread: Core::Command::(anonymous namespace)::ShowSchedule::Execute(Command::Request const&, Command::Response&) const+0x64

Мар 8 08:09:22

 

ndm

Thread: Core::Configurator::Execute(Command::Base const*, Command::Request const&, Command::Response&)+0x1f8

Мар 8 08:09:22

 

ndm

Thread: Core::Configurator::Serve(Command::Request const&, Command::Response&)+0x3e4

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::Tools::(anonymous namespace)::JsonPostObject_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Object const*, Json::Object*)+0x684

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::Tools::(anonymous namespace)::JsonPostValue_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Value const*, Json::Object*)+0x1ac

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::Tools::(anonymous namespace)::JsonPostObject_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Object const*, Json::Object*)+0xab0

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::Tools::(anonymous namespace)::JsonPostValue_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Value const*, Json::Object*)+0x1ac

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::Tools::(anonymous namespace)::JsonPostObject_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Object const*, Json::Object*)+0xab0

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::Tools::(anonymous namespace)::JsonPostValue_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Value const*, Json::Object*)+0x1ac

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::Tools::JsonPost(Core::Configurator&, Core::Scgi::Request const&, Json::Document const&, Core::Scgi::Trace&, Json::Document&, bool*)+0x13c

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::ThreadPool::Task_::ProcessJsonRequest_(Core::Configurator&, Core::Scgi::Request const&, Core::Scgi::Trace&, Array<char>&, Io::OStream&)+0x368

Мар 8 08:09:22

 

ndm

Thread: Core::Scgi::ThreadPool::Task_::Run()+0x144

Мар 8 08:09:22

 

ndm

Thread: Task::Thread::Run_()+0x314

Мар 8 08:09:22

 

ndm

Thread: Task::Thread::Run()+0x18

Мар 8 08:09:22

 

ndm

Thread: Thread::StartRoutine_(void*)+0x2d0

Мар 8 08:09:22

 

ndm

Thread: start()+0x8c

Мар 8 08:09:22

 

ndm

Thread: __clone()+0x30

Ниже скрытым постом прикреплю self-test с основного роутера и ретранслятора.

[4.0 Alpha 1: Сломалось отображение отдачи]

В версия ОС 4.0 Alpha 11 ситуация не поменялась.

[4.0 Alpha 1: Сломалось отображение отдачи]

@hellonowПрикреплю следующим скрытым постом self-test.

Хотя же отписывал, что вызывает это:

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

 

 

[4.0 Alpha 1: Сломалось отображение отдачи]

@hellonow В версия ОС 4.0 Alpha 10 ситуация не поменялась.

[4.0 Alpha 10 , Дублирование устройств]

3 часа назад, Zit сказал:

Всем привет!

Такое уже давно происходит, с момента покупки камеры,но может кто знает почему так или знает решение, чтобы так не происходило?

Камера физически одна, порт соответственно один, но вот устройств почему то два:

  Скрыть содержимое

так же не должно быть?

А если зафиксировать IP адрес, поставить галачку "Постоянный IP-адрес"?

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

 

[Ночная тема (расширение браузера)]

3 часа назад, PASPARTU сказал:

Последняя версия расширения, в хром и в FF не показывает счетчики TXErr RXErr.

Если у вас нет ошибок, то и не будет показывать.

Появятся ошибки, отобразиться.

[4.0A9: не загружается раздел "storage"]

Версия ОС 4.0 Alpha 10 исправлено:

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

 

[4.0 Alpha 1: Сломалось отображение отдачи]

@hellonow На эту проблемку обратите внимание.

[4.0A9: не загружается раздел "storage"]

Есть такое:

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

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

 

[Максимальный объем подключаемого внешнего накопителя]

2 минуты назад, krass сказал:

Имхо, лучше сразу взять с доп. питанием независимо 2.5 или 3.5 

Это точно не помешает....

[Максимальный объем подключаемого внешнего накопителя]

3 минуты назад, Болат сказал:

Значить больше 2тб лучше с питанием? 

Если 3,5", то с доп.питанием. Если 2.5", то возможно и потянет и без доп.питания.

[Максимальный объем подключаемого внешнего накопителя]

4 минуты назад, Болат сказал:

Здравствуйте! У вас hard на 4тб с питанием или без? Я тоже хочу купить hard на 4 или на 6тб, вот только не могу определится, с питанием или без питания. Сомнения в том что большая емкость без питания как будет вести себя. 

С доп.питанием.

[4.0 Alpha 1: Сломалось отображение отдачи]

Версия ОС 4.0 Alpha 9, ситуация не изменилась.

[4.0 Alpha 1: Сломалось отображение отдачи]

В 4.0 Alpha 8 ситуация не изменилась.

@Le ecureuil посмотрите пожалуйста. 

[4.0 Alpha 6: после обновления не видит жесткие диски]

4 часа назад, Spider1973 сказал:

У меня на 1710 на ней переходник 860 модема вообще по питанию светиться перестал,соответственно модем в системе не виден

Откатывайте прошивку и ждать обновление.

[4.0 Alpha 6: после обновления не видит жесткие диски]

14 минуты назад, Slider88 сказал:

после обновления до alpha 6 kn-1711 не видит жесткие диски. ОДновременно на двух домашних роутерах такая петрушка. 

Цитата

 

 

[4.0 Alpha 1: Сломалось отображение отдачи]

Версия ОС4.0 Alpha 5 ситуация не изменилась.

При включенном "ppe hardware" :

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

При отключенном "ppe hardware" :

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

Нагрузка на процессор при этом увеличивается.... 

[Ночная тема (расширение браузера)]

Еще плохо читаемый текст:

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

 

[Ночная тема (расширение браузера)]

@eralde  Добрый день! Спасибо за расширение для прошивок 4.х!

"Засвечивается" при наведение курсора в выпадающем меню выбранная позиция:

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

Версия 0.5.108. Браузер Opera версия:94.0.4606.76. Система:Linux Mint 21.1.

[После обновления Keenetic Giga 3 через веб-конфигуратор сам конфигуратор изменился, а пароль не принимется.]

1 час назад, Mamay сказал:

что продвинутые дети папе делали мозги, к примеру...

 Было такое.

[После обновления Keenetic Giga 3 через веб-конфигуратор сам конфигуратор изменился, а пароль не принимется.]

20 минут назад, Blosfora сказал:

дефолтные пароль

А что значит "дефолтные пароль"? По умолчанию логина и пароля нет.