Jump to content
Калькуляторы

Nanobridge M2 - валится линк

Reply to this topic

tofu   

tofu
Posted (edited)

Буквально сегодня начал валиться линк. Пробовал уходить на другие частоты, полосу менял с 40 на 20, отключил шифрование, повышал\понижал мощность... ничего не помогает... в чем может быть причина?

 

"Логи с БС"

 

Apr 06 17:55:13 system: Start

Apr 6 17:55:13 syslogd started: BusyBox v1.11.2

Apr 6 17:55:14 wireless: ath0 Set Mode:Master

Sep 27 13:08:22 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 13:08:22 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 13:08:22 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 13:08:25 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: PTK: Failed to receive EAPOL-Key msg 4/4 response, all tries exhausted.

Sep 27 13:08:25 wireless: ath0 Sending deauth to 00:27:22:78:11:b5. Reason: 4-way keying handshake timeout (15).

Sep 27 13:08:25 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: deauthenticated due to local deauth request

Sep 27 13:08:25 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=1 rx_bytes=135 tx_packets=6 tx_bytes=866

Sep 27 13:08:25 wireless: ath0 Expired node:00:27:22:78:11:B5

Sep 27 13:08:25 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: disassociated

Sep 27 13:08:26 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 13:08:26 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 13:08:26 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 13:08:29 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: PTK: Failed to receive EAPOL-Key msg 2/4 response, all tries exhausted.

Sep 27 13:08:29 wireless: ath0 Sending deauth to 00:27:22:78:11:b5. Reason: 4-way keying handshake timeout (15).

Sep 27 13:08:29 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=0 rx_bytes=0 tx_packets=4 tx_bytes=428

Sep 27 13:08:29 wireless: ath0 Expired node:00:27:22:78:11:B5

Sep 27 13:08:29 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: deauthenticated due to local deauth request

Sep 27 13:08:29 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: disassociated

Sep 27 13:08:29 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 13:08:29 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 13:08:29 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 13:08:29 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 13:08:51 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 13:08:51 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 13:08:51 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 13:08:51 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 13:09:13 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 13:09:13 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 13:09:13 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 13:09:13 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: received EAPOL-Key msg 2/4 in invalid state (10) - dropped

Sep 27 13:09:13 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 13:10:38 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: disassociated

Sep 27 13:10:38 wireless: ath0 Sending deauth to 00:27:22:78:11:b5. Reason: Authentication is not valid (2).

Sep 27 13:10:38 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=0 rx_bytes=0 tx_packets=29 tx_bytes=1080

Sep 27 13:10:38 wireless: ath0 Expired node:00:27:22:78:11:B5

Sep 27 13:13:35 init: reloading /etc/inittab

Sep 27 13:13:35 system: Stop

Sep 27 13:13:36 init: process '/bin/hostapd /etc/aaa1.cfg' (pid 956) exited. Scheduling for restart.

Sep 27 13:13:36 init: process '/sbin/ntpclient -n -s -c 0 -l -h 193.109.70.10' (pid 957) exited. Scheduling for restart.

Sep 27 13:13:36 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 958) exited. Scheduling for restart.

Sep 27 13:13:36 init: process '/bin/tinysnmpd /etc/snmp.conf /lib/tinysnmp' (pid 959) exited. Scheduling for restart.

Sep 27 13:13:37 syslogd exiting

Sep 27 13:13:43 system: Start

Sep 27 13:13:43 syslogd started: BusyBox v1.11.2

Sep 27 13:13:43 wireless: ath0 Set Mode:Master

Sep 27 13:14:21 wireless: ath0 Scan request completed

Sep 27 13:15:07 init: reloading /etc/inittab

Sep 27 13:15:07 system: Stop

Sep 27 13:15:08 init: process '/bin/hostapd /etc/aaa1.cfg' (pid 1519) exited. Scheduling for restart.

Sep 27 13:15:08 init: process '/sbin/ntpclient -n -s -c 0 -l -h 193.109.70.10' (pid 1520) exited. Scheduling for restart.

Sep 27 13:15:08 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1521) exited. Scheduling for restart.

Sep 27 13:15:08 init: process '/bin/tinysnmpd /etc/snmp.conf /lib/tinysnmp' (pid 1522) exited. Scheduling for restart.

Sep 27 13:15:09 syslogd exiting

Sep 27 13:15:15 system: Start

Sep 27 13:15:15 syslogd started: BusyBox v1.11.2

Sep 27 13:16:10 init: reloading /etc/inittab

Sep 27 13:16:10 system: Stop

Sep 27 13:16:11 init: process '/bin/hostapd /etc/aaa1.cfg' (pid 1935) exited. Scheduling for restart.

Sep 27 13:16:11 init: process '/sbin/ntpclient -n -s -c 0 -l -h 193.109.70.10' (pid 1936) exited. Scheduling for restart.

Sep 27 13:16:11 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1937) exited. Scheduling for restart.

Sep 27 13:16:11 init: process '/bin/tinysnmpd /etc/snmp.conf /lib/tinysnmp' (pid 1938) exited. Scheduling for restart.

Sep 27 13:16:13 syslogd exiting

Sep 27 13:16:19 system: Start

Sep 27 13:16:19 syslogd started: BusyBox v1.11.2

Sep 27 13:16:19 wireless: ath0 Set Mode:Master

Sep 27 13:23:08 wireless: ath0 Scan request completed

Sep 27 13:31:42 init: reloading /etc/inittab

Sep 27 13:31:42 system: Stop

Sep 27 13:31:43 init: process '/bin/hostapd /etc/aaa1.cfg' (pid 2338) exited. Scheduling for restart.

Sep 27 13:31:43 init: process '/sbin/ntpclient -n -s -c 0 -l -h 193.109.70.10' (pid 2339) exited. Scheduling for restart.

Sep 27 13:31:43 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 2340) exited. Scheduling for restart.

Sep 27 13:31:43 init: process '/bin/tinysnmpd /etc/snmp.conf /lib/tinysnmp' (pid 2341) exited. Scheduling for restart.

Sep 27 13:31:44 syslogd exiting

Sep 27 13:31:50 system: Start

Sep 27 13:31:50 syslogd started: BusyBox v1.11.2

Sep 27 13:34:21 init: reloading /etc/inittab

Sep 27 13:34:21 system: Stop

Sep 27 13:34:22 init: process '/bin/hostapd /etc/aaa1.cfg' (pid 3459) exited. Scheduling for restart.

Sep 27 13:34:22 init: process '/sbin/ntpclient -n -s -c 0 -l -h 193.109.70.10' (pid 3460) exited. Scheduling for restart.

Sep 27 13:34:22 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 3461) exited. Scheduling for restart.

Sep 27 13:34:22 init: process '/bin/tinysnmpd /etc/snmp.conf /lib/tinysnmp' (pid 3462) exited. Scheduling for restart.

Sep 27 13:34:23 syslogd exiting

Sep 27 13:34:29 system: Start

Sep 27 13:34:29 syslogd started: BusyBox v1.11.2

Sep 27 13:38:23 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 13:38:23 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 13:38:23 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 13:38:23 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 13:42:36 wireless: ath0 Received disassoc from 00:27:22:78:11:b5. Reason: Station has left the basic service area and is disassociated (8).

Sep 27 13:42:36 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=19086 rx_bytes=23695287 tx_packets=21387 tx_bytes=17978715

Sep 27 13:42:36 wireless: ath0 Expired node:00:27:22:78:11:B5

Sep 27 13:42:36 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: disassociated

Sep 27 13:42:46 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 13:42:46 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 13:42:46 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 13:42:46 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 14:23:05 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 14:23:05 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 14:23:05 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 14:23:05 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: received EAPOL-Key msg 2/4 in invalid state (10) - dropped

Sep 27 14:23:05 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 14:23:11 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 14:23:11 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 14:23:11 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 14:23:11 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 14:27:01 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 14:27:01 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 14:27:01 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 14:27:02 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 14:27:02 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: received EAPOL-Key msg 4/4 in invalid state (11) - dropped

Sep 27 14:34:30 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: group key handshake completed (RSN)

Sep 27 14:38:39 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 14:38:39 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 14:38:39 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 14:38:39 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: received EAPOL-Key msg 2/4 in invalid state (10) - dropped

Sep 27 14:38:39 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 14:50:47 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 14:50:47 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 14:50:47 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 14:50:48 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: received EAPOL-Key msg 2/4 in invalid state (10) - dropped

Sep 27 14:50:48 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 15:08:06 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 15:08:06 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 15:08:06 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 15:08:06 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: received EAPOL-Key msg 2/4 in invalid state (10) - dropped

Sep 27 15:08:06 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 15:08:12 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 15:08:12 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 15:08:12 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 15:08:12 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 15:16:07 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 15:16:07 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 15:16:07 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 15:16:07 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 15:32:08 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 15:32:08 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 15:32:08 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 15:32:08 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 15:34:30 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: group key handshake completed (RSN)

Sep 27 15:47:51 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 15:47:51 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 15:47:51 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: associated

Sep 27 15:47:51 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: received EAPOL-Key msg 2/4 in invalid state (10) - dropped

Sep 27 15:47:51 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: pairwise key handshake completed (RSN)

Sep 27 15:47:51 hostapd: ath0: STA 00:27:22:78:11:b5 WPA: received EAPOL-Key msg 4/4 in invalid state (11) - dropped

Sep 27 16:05:20 wireless: ath0 Received disassoc from 00:27:22:78:11:b5. Reason: Station has left the basic service area and is disassociated (8).

Sep 27 16:05:20 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=351899 rx_bytes=233892983 tx_packets=132541 tx_bytes=14047902

Sep 27 16:05:20 wireless: ath0 Expired node:00:27:22:78:11:B5

Sep 27 16:05:20 hostapd: ath0: STA 00:27:22:78:11:b5 IEEE 802.11: disassociated

Sep 27 16:05:28 init: reloading /etc/inittab

Sep 27 16:05:28 system: Stop

Sep 27 16:05:29 init: process '/bin/hostapd /etc/aaa1.cfg' (pid 3922) exited. Scheduling for restart.

Sep 27 16:05:29 init: process '/sbin/ntpclient -n -s -c 0 -l -h 193.109.70.10' (pid 3923) exited. Scheduling for restart.

Sep 27 16:05:29 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 3924) exited. Scheduling for restart.

Sep 27 16:05:29 init: process '/bin/tinysnmpd /etc/snmp.conf /lib/tinysnmp' (pid 3925) exited. Scheduling for restart.

Sep 27 16:05:31 syslogd exiting

Sep 27 16:05:37 system: Start

Sep 27 16:05:37 syslogd started: BusyBox v1.11.2

Sep 27 19:49:32 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:49:53 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:50:15 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:50:37 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:51:01 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:51:25 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:51:47 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:52:12 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:52:33 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:52:55 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:53:48 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 19:53:48 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:54:20 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 19:54:20 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:55:08 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 19:55:08 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:55:40 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 19:55:40 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:56:06 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 19:56:06 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:56:44 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 19:56:44 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:57:42 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 19:57:42 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:58:04 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 19:59:07 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 19:59:07 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:02:47 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:02:47 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:03:08 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:03:46 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:03:46 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:04:54 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:04:54 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:05:35 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:05:35 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:06:02 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:06:02 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:07:31 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:07:31 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:08:34 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:08:34 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:09:12 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:09:12 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:09:38 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:09:38 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:10:26 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:10:26 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:11:03 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:11:08 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:11:08 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:13:01 wireless: ath0 Sending deauth to 00:27:22:78:11:b5. Reason: Authentication is not valid (2).

Sep 27 20:13:01 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=8626971 rx_bytes=6076225757 tx_packets=4051761 tx_bytes=2259236699

Sep 27 20:13:01 wireless: ath0 Expired node:00:27:22:78:11:B5

Sep 27 20:14:25 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:14:25 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:26:05 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:27:33 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:27:57 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:28:18 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:28:41 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:29:34 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:29:34 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:30:01 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:30:01 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:30:38 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:30:38 wireless: ath0 Registered node:00:27:22:78:11:B5

 

"Логи с АС"

 

Apr 06 17:55:14 system: Start

Apr 6 17:55:14 syslogd started: BusyBox v1.11.2

Sep 27 20:26:04 wireless: ath0 New Access Point/Cell address:Not-Associated

Sep 27 20:26:05 wireless: ath0 New Access Point/Cell address:00:27:22:64:C1:34

Sep 27 20:27:28 wireless: ath0 New Access Point/Cell address:Not-Associated

Sep 27 20:27:33 wireless: ath0 New Access Point/Cell address:00:27:22:64:C1:34

Sep 27 20:27:55 wireless: ath0 New Access Point/Cell address:Not-Associated

Sep 27 20:27:57 wireless: ath0 New Access Point/Cell address:00:27:22:64:C1:34

Sep 27 20:28:18 wireless: ath0 New Access Point/Cell address:Not-Associated

Sep 27 20:28:18 wireless: ath0 New Access Point/Cell address:00:27:22:64:C1:34

Sep 27 20:28:40 wireless: ath0 New Access Point/Cell address:Not-Associated

Sep 27 20:28:41 wireless: ath0 New Access Point/Cell address:00:27:22:64:C1:34

Sep 27 20:29:03 wireless: ath0 New Access Point/Cell address:Not-Associated

Sep 27 20:29:08 wireless: ath0 Scan request completed

Sep 27 20:29:13 wireless: ath0 Scan request completed

Sep 27 20:29:18 wireless: ath0 Scan request completed

Sep 27 20:29:23 wireless: ath0 Scan request completed

Sep 27 20:29:29 wireless: ath0 Scan request completed

Sep 27 20:29:34 wireless: ath0 Scan request completed

Sep 27 20:29:34 wireless: ath0 New Access Point/Cell address:00:27:22:64:C1:34

Sep 27 20:29:56 wireless: ath0 New Access Point/Cell address:Not-Associated

Sep 27 20:30:01 wireless: ath0 Scan request completed

Sep 27 20:30:01 wireless: ath0 New Access Point/Cell address:00:27:22:64:C1:34

Sep 27 20:30:22 wireless: ath0 New Access Point/Cell address:Not-Associated

Sep 27 20:30:28 wireless: ath0 Scan request completed

Sep 27 20:30:33 wireless: ath0 Scan request completed

Sep 27 20:30:38 wireless: ath0 Scan request completed

Sep 27 20:30:38 wireless: ath0 New Access Point/Cell address:00:27:22:64:C1:34

Edited by tofu

Share this post

Link to post
Share on other sites

kosmich7   

kosmich7
Posted

Зона френеля частично перекрыта.

Где перекрыта ? в голове)

 

Скрины говорят об отсутствии проблем в параметрах линка.

Share this post

Link to post
Share on other sites

tofu   

tofu
Posted (edited)

Зона френеля частично перекрыта.

Где перекрыта ? в голове)

очень культурно и полезно, настоящий профессионал своего дела. что вы хотели сказать этим? Может будем посодержательнее?

Edited by tofu

Share this post

Link to post
Share on other sites

kosmich7   

kosmich7
Posted

Зона френеля частично перекрыта.

Где перекрыта ? в голове)

очень культурно и полезно, настоящий профессионал своего дела. что вы хотели сказать этим? Может будем посодержательнее?

Содержательней некуда.

 

Скрины говорят об отсутствии проблем в параметрах линка.

 

Что вам есче добавить чтоб вам стало понятно ?

 

И тут вдруг выясняеться что бриджи используються для резервирования)))

Какую траву вы курите ?)

Share this post

Link to post
Share on other sites

tofu   

tofu
Posted

Что вам есче добавить чтоб вам стало понятно ?

о чем говорит этот кусок лога

 

 

Sep 27 20:11:03 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:11:08 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:11:08 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:13:01 wireless: ath0 Sending deauth to 00:27:22:78:11:b5. Reason: Authentication is not valid (2).

Sep 27 20:13:01 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=8626971 rx_bytes=6076225757 tx_packets=4051761 tx_bytes=2259236699

Sep 27 20:13:01 wireless: ath0 Expired node:00:27:22:78:11:B5

Sep 27 20:14:25 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:14:25 wireless: ath0 Registered node:00:27:22:78:11:B5

 

И тут вдруг выясняеться что бриджи используються для резервирования)))

Какую траву вы курите ?)

какого реервирования? Вы о чем?

Share this post

Link to post
Share on other sites

kosmich7   

kosmich7
Posted

Sep 27 20:11:03 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:11:08 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:11:08 wireless: ath0 Registered node:00:27:22:78:11:B5

Sep 27 20:13:01 wireless: ath0 Sending deauth to 00:27:22:78:11:b5. Reason: Authentication is not valid (2).

Sep 27 20:13:01 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=8626971 rx_bytes=6076225757 tx_packets=4051761 tx_bytes=2259236699

Sep 27 20:13:01 wireless: ath0 Expired node:00:27:22:78:11:B5

Sep 27 20:14:25 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:78:11:b5)

Sep 27 20:14:25 wireless: ath0 Registered node:00:27:22:78:11:B5

Это просто лог событий который говорит событиях, и никоем образом не имеет отношения к реальным параметрам линка.

 

а вот это откуда

просто предположу... при включенном RSTP на СПД, BPDU пакеты могут влиять как то?

взялось ?

Кто и где это включил и зачем ?

 

Ах да и про карму можно россказать из вашего лога)))

Share this post

Link to post
Share on other sites

tofu   

tofu
Posted

а вот это откуда

 

Просмотр сообщенияtofu (Сегодня, 21:09) писал:

просто предположу... при включенном RSTP на СПД, BPDU пакеты могут влиять как то?

 

взялось ?

Кто и где это включил и зачем ?

на спд реализовано плоское кольцо... насосы НЕ В КОЛЬЦЕ!

Share this post

Link to post
Share on other sites

NewUse   

NewUse
Posted

У Вас не линк валится, а точка(клиент) ребутится по питанию.

 

ну и для п2п рекомендую до 5.3 откатить и мощности порезать.

ну и или аск увеличить или аггрегацию поубавить, либо то и другое

 

И, да, галочка п2п но АСК стоит?, а лучше ЭирМакс нафиг отрубить.

Share this post

Link to post
Share on other sites

tofu   

tofu
Posted

У Вас не линк валится, а точка(клиент) ребутится по питанию.

 

блин, я не знаю как обьяснить вам то, что я вижу в моменты глюков... скрин не могу приложить... попробую нарисовать...

post-66811-027245000 1348774884_thumb.png

Share this post

Link to post
Share on other sites

NewUse   

NewUse
Posted

дай скрины с двух сторон в момент глюков, отключи вотчдог (чтоб не ребутил), обрати внимание на Lan0 и Noise Floor, откатись до 5.3 отруби ЭирМакс.

Share this post

Link to post
Share on other sites

tofu   

tofu
Posted

ну и для п2п рекомендую до 5.3 откатить и мощности порезать.

понизил на обоих до 18, менять FW пока не стал.

 

 

ну и или аск увеличить или аггрегацию поубавить, либо то и другое

аск поднял до 1 мили.

 

И, да, галочка п2п но АСК стоит?, а лучше ЭирМакс нафиг отрубить.

отрубил аирмакс.

 

сейчас почищу логи и буду смотреть, канальная скорость кстати даже поднялась немного. агрегацию какую поставить лучше?

Share this post

Link to post
Share on other sites

NewUse   

NewUse
Posted
менять FW пока не стал.

Обновите хотяб до 5.5.2, я 5.5 длительно не тестил.

 

сейчас почищу логи и буду смотреть

В логи ЮБНТ ничерта не пишет, касаемо состояния эфира.

, канальная скорость кстати даже поднялась немного.

Естественно :)

 

агрегацию какую поставить лучше?

Если CCQ возросло до 100 -- оставляйте максимум 32 на что-то там.

Share this post

Link to post
Share on other sites

NewUse   

NewUse
Posted

Блин, только заметил, у Вас 2.55 ГГц, AirView в момент проблем запустите, если точка на каком-нить коттедже, проверьте не совпадают ли падения с моментом включения микроволновки? не юзает ли кто радио-няню поблизости...

Шифрование ВПА2-АЕС поставьте, а то ведь найдутся любители халявы....

Share this post

Link to post
Share on other sites

tofu   

tofu
Posted

Обновите хотяб до 5.5.2, я 5.5 длительно не тестил.

у меня с порта коммутатора в режиме tag подается VLAN 1130 по которому управляются бриджи и в режиме untag подаю VLAN 1230 для PPPoE (на конце бриджа один абон). Соответственно в бриджах прописан mgmt vlan 1130. Смена FW никак не повлияет на эту схему работы?

Share this post

Link to post
Share on other sites

NewUse   

NewUse
Posted
Смена FW никак не повлияет на эту схему работы?

в рамках 5.5 нет, проблем не будет, а вот с даунгрейдом до 5.3 скорее всего будут траблы, так что лучше иметь физ. доступ к девайсам с обоих сторон, если решитесь на даунгрейд.

Share this post

Link to post
Share on other sites

Saab95   

Saab95
Posted

Еще бы ему не валиться - это же UBNT.

 

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

 

 

Share this post

Link to post
Share on other sites

tofu   

tofu
Posted

Нужно сперва попробовать частоты поменять, просканировать эфир. Уменьшить полосу до 20мгц.

ну я ж в первом посте написал что пробовал =)

 

Провести ревизию устройств, может сдуло или еще какая проблема.

 

не сдуло, уже ездил...

Share this post

Link to post
Share on other sites

NewUse   

NewUse
Posted
Провести ревизию устройств, может сдуло или еще какая проблема.

сдуть -- не сдуло, сигнал идеальный, правда пока нет скрина в момент траблов.

А вот аптаим клиента 20 мин, т.е. была перезагрузка, о причинах коорой ничего не известно, может и в правду кабель разболтался, это идея :)

Share this post

Link to post
Share on other sites

tofu   

tofu
Posted

в рамках 5.5 нет, проблем не будет, а вот с даунгрейдом до 5.3 скорее всего будут траблы, так что лучше иметь физ. доступ к девайсам с обоих сторон, если решитесь на даунгрейд.

обновился до 5.5.2... уровни опять поднялись, ccq достиг 100%. Вроде пока все нормуль, устройства ведут себя адекватно... тестим, ждем помех

 

правда пока нет скрина в момент траблов.

я прикладывал скрин, повторяю... в момент траблов радиолинк якобы есть, но доступа на удаленную железку нет, в графе ccq прочерк, в графе TX\RX,Mbps первое число 300 второе 0, в обычном состоянии 300\300 или 270\300, в графе last ip написано unknown, хотя device name и MAC удаленной железки определяется

post-66811-064985100 1348779080_thumb.png

Share this post

Link to post
Share on other sites

NewUse   

NewUse
Posted (edited)
уровни опять поднялись

держите ccq на 100%, канальные скорости в 300Мбит в обе стороны, и при соблюдении этих условий найдите минимальную мощность -- это даст максимум скорости :), но это никак не поможет в решении Вашей конкретной проблемы :(((

 

но доступа на удаленную железку нет, в графе ccq прочерк, в графе TX\RX,Mbps первое число 300 второе 0, в обычном состоянии 300\300 или 270\300, в графе last ip написано unknown, хотя device name и MAC удаленной железки определяется

Следить нужно со стороны клиента :(, но очень похоже на перезагрузку, я почти на 100% уверен, причин не знаю, возможно питание, не замечали скачки LAN-speed на 10Мбит на клиенте?

 

Сразу после того как в следующий раз прервётся и восстановится связь с клиентом, посмотрите Uptime на нём (предварительно необходимо убедится, что watchdog на нём ОТключен).

Edited by NewUse

Share this post

Link to post
Share on other sites

Yodda83   

Yodda83
Posted

Если тебя ещё актуальна, подскажите плиз что означают эти строки :

Sep 27 13:10:38 wireless: ath0 Sending deauth to 00:27:22:78:11:b5. Reason: Authentication is not valid (2).

Sep 27 13:10:38 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:78:11:b5 rx_packets=0 rx_bytes=0 tx_packets=29 tx_bytes=1080

Sep 27 13:10:38 wireless: ath0 Expired node:00:27:22:78:11:B5

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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

×
Followers 0
Go to topic listing Ubiquiti Networks