disconnected received disassoc sending station leaving 8

При попытке подключения к точке доступа WiFi возникала ошибка «11:22:33:44:55:66@wlan1:disconnected, extensive data loss».
Чаще всего ошибка может быть вызвана следующими причинами:

  1. Низким сигналом. Это наиболее частая причина этой ошибки.
  2. Не корректными настройками Data Rates (если настроили Data Rates в Advanced mode настроек WiFi и отключили скорость, которая необходима абоненту).
  3. Помехами на канале (роутер с максимальной мощностью на том же канале, включенные бытовые приборы).
  4. Наличием на точке доступа «hidden SSID» (в редких случаях, но бывает).
  5. Нарушение поляризации антенны на стороне клиента или на точке доступа (если у всех клиентов такая проблема).
  6. Не корректное расположение точки доступа (рядом с металлическими предметами).

Варианты решения проблемы:

  1. Проверить силу сигнала в месте возникновения проблем.
  2. Проверить правильность размещения и ориентации точки доступа и ее антенн.
  3. Пересадить точку доступа на другой канал (6,1 или 11).

We have a product that considers installing on a client’s room a Mikrotik RouterBoard 951G 2HnD hosting a wifi network with WPA2 PSK security connected to our client’s network and an Android tablet connected to the Mikrotik’s wifi network. This solution has been installed on dozens of our clients’ sites and we have never had any issues before.

Two weeks ago the all the rooms (four) inside one of our client’s building started to have wifi problems. After working great for several hours, each tablet would disconnect (¿or be dropped?) from the RouterBoard 951G 2HnD’s wifi network and then immediately connect. After the first disconnection (or being dropped) and reconnection the tablet would keep disconnecting (or being dropped) and reconnecting from the wifi for several minutes, which would end in a final disconnection and then no more reconnection intents.

The solution worked great for months but after we changed the tablet this started happening. At the beginning we thought this was because we had changed the tablet but after trying with another Android tablets and an Android cell phone even, the problem would still occur. We also replaced the RouterBoard 951G 2HnD with one that was working great at another office and it also started to show this unusual behaviour.

Finally, we took one of the four room’s Android tablet and RouterBoard 951G 2HnD, and installed them on one of our laboratories without modifying any configuration on both of them. After almost 24 hours the problem has not replicated.

I thought activating the Wireless Debug Logs would us show more relevant information and help us focus our investigation on the right direction but it didn’t. Next are the log records:

Also, we did a spectrum analisis showing the usage of each channel (but only with networks with visible SSIDs) and the result was the following:

As the image shows we are currently working on channel 4 but previously when the problem started happening we were on channel 1.

We have no idea where to keep looking and why is this problem happening. Any help or guidance will be deeply appreciated.

Upate

I would like to add more detailed information about the usage of the wifi spectrum. At the beggining we were on channel one. Then we changed to channel 3 (see image on first post) but after using InSSIDer we ended changing to channel 10.

Next is the image of the test results when channel 3 was being used:

Next is the image of the test results after selecting the best wifi channel (which was channel 10):

I would love to hear more comments and thought. Everything that makes us do something we have not yet done.

EVEN MORE UPDATE

The next image presents the DHCP packets sent between the tablets and the Mikrotik router installed on one room:

The DHCP Discover and DHCP Request packets are sent from the tablets to the DHCP server (supposedly the Microtik’s), which are not beeing answered with a DHCP Offer or a DHCP ACK. One could get confuzed and think that the packets #997, #995, #999 y #1004 respond to the requests that appear before but their transaction ID shows that they are from another set of requests. Same happens with the DHCP NAK. On the DHCP protocol the different messages from one communication flow will keep the transaction ID as shown in the next image:

Looking deeper on the DHCP Request messages sent by the tablets, we found one (packet #785) asking for the IP 172.22.198.134 to the DHCP server with the IP address 152.141.217.7, which is very weird because the only Wi-Fi network registrated on the test devices was the one with SSID CVNET62710 owned by the Mikrotik.

Additionally, the ARP packets were analized and we found that the device with a MAC address 00:00:0c:07:ac:64, that appears as All-HSRP-routers_64, reports that he has the IP address 172.22.198.1 and the IP address 192.168.89.1, being this last one the IP address of the Mikrotik’s Wi-Fi interface that holds the DHCP server. Next you can see the evidence:

I’m thinking this duplicated IP is the reason the problem of the disconnection and reconnection on of the tablet of this room. Sadly, I haven’t been able to take captures on the other rooms so I can’t assure or discard that this could be happening on every one of them.

Also, today in the morning when we went to configure the IP address of the tablet (of the current room) as a static one, when we selected manual IP address we found that it was set to 192.168.1.128, which is not from the ranged delivered by the Mikrotik (192.168.89.X). It seems that it took the IP address of another network even though the only registrated Wi-Fi network is CVNET62710.

I would like to hear your thoughts on the matter and see if you think this could be causing the recurrent disconnection and reconnection of the devices.

Есть у меня ноут с Vista. Жили мы с ним долго и в общем счастливо. Однако с ростом скоростей домашнего подключения стал дурить ASUS, за что был заменён на Mikrotik. С некоторых пор стал замечать, что пропадает соединение по WiFi. Почему?

Если не по теме, то куда можно запостить ещё?

Микротик на эту тему говорит просто:

Mar 25 22:54:11 mikrotik xx:xx:xx:xx:xx:xx@wlan1: disconnected, received deauth: unspecified (1)

Vista со своей стороны рассказывает простынёй:

Имя журнала: Microsoft-Windows-WLAN-AutoConfig/Operat ional
Подача: Microsoft-Windows-WLAN-AutoConfig
Дата: 25.03.2014 22:54:06
Код события: 8003
Категория задачи:Отсутствует
Уровень: Сведения
Ключевые слова:
Пользователь: SYSTEM
Компьютер: ACER
Описание:
Служба автонастройки WLAN успешно отключилась от беспроводной сети.

Сетевой адаптер: Intel(R) Wireless WiFi Link 5100
GUID интерфейса: <72b83a1f-de34-4b39-9fa8-c348775c8926>
Режим подключения: Автоматическое подключение с использованием профиля
Имя профиля: hotspot
SSID: hotspot
Тип BSS: Infrastructure
Причина: Сеть отключена драйвером.

Имя журнала: System
Подача: Microsoft-Windows-Dhcp-Client
Дата: 25.03.2014 22:54:10
Код события: 1103
Категория задачи:Отсутствует
Уровень: Сведения
Ключевые слова:Классический
Пользователь: Н/Д
Компьютер: ACER
Описание:
Компьютеру успешно назначен сетевой адрес, и теперь он может подключаться к другим компьютерам.

Имя журнала: System
Подача: Tcpip
Дата: 25.03.2014 22:54:10
Код события: 4201
Категория задачи:Отсутствует
Уровень: Сведения
Ключевые слова:Классический
Пользователь: Н/Д
Компьютер: ACER
Описание:
Система обнаружила, что сетевой адаптер Беспроводное сетевое соединение был подключен к сети, и инициировала нормальную работу через этот сетевой адаптер.

Т.е. по всему выходит, что драйвер решает отключиться. А вот зачем он это делает — не понятно.
Ноут хоть и держит торентокачалку, но активного трафика на момент отключений нет.
Привязать к конкретному времени эти отключения тоже нельзя. Сегодня около 11 вечера началось, 3-5 реконнектов и прошло.
Может в 12 ночи или в час ночи такое выкинуть. Драйвер, если верить микрософту, последней версии.
Что ещё и где ещё можно посмотреть. Спасибо

в самом начале же написал
Mar 25 22:54:11 mikrotik xx:xx:xx:xx:xx:xx@wlan1: disconnected, received deauth: unspecified (1)
и ещё дальше про выдачу адреса клиенту по dhcp после переподключения

т.е. и микротик говорит, что клиент отключился, и виста сама говорит, что отключилась, а чегой-то она так делает — не понятно

/system logging add topics=wireless action=memory
или
/system logging add topics=wireless action=disk

Mar 25 22:50:50 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B attempts to associate
Mar 25 22:50:50 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: reassociating
Mar 25 22:50:50 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: disconnected, ok
Mar 25 22:50:50 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B not in local ACL, by default accept
Mar 25 22:50:50 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: connected
Mar 25 22:52:52 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B attempts to associate
Mar 25 22:52:52 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: reassociating
Mar 25 22:52:52 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: disconnected, ok
Mar 25 22:52:52 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B not in local ACL, by default accept
Mar 25 22:52:52 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: connected
Mar 25 22:52:57 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: disconnected, unicast key exchange timeout
Mar 25 22:53:10 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B attempts to associate
Mar 25 22:53:10 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B not in local ACL, by default accept
Mar 25 22:53:10 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: connected
Mar 25 22:53:25 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: disconnected, received deauth: unspecified (1)
Mar 25 22:53:54 Cisco2611XM mikrotik_wireless: B8:B4:2E:24:5D:BF@wlan1: disconnected, received deauth: sending station leaving (3)
Mar 25 22:53:58 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B attempts to associate
Mar 25 22:53:58 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B not in local ACL, by default accept
Mar 25 22:53:58 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: connected
Mar 25 22:54:11 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: disconnected, received deauth: unspecified (1)
Mar 25 22:54:23 Cisco2611XM mikrotik_wireless: wlan1: B8:B4:2E:13:D6:E1 attempts to associate
Mar 25 22:54:23 Cisco2611XM mikrotik_wireless: wlan1: B8:B4:2E:13:D6:E1 not in local ACL, by default accept
Mar 25 22:54:23 Cisco2611XM mikrotik_wireless: B8:B4:2E:24:5D:BF@wlan1: connected
Mar 25 22:54:45 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B attempts to associate
Mar 25 22:54:45 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B not in local ACL, by default accept
Mar 25 22:54:45 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: connected
Mar 25 22:57:18 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B attempts to associate
Mar 25 22:57:18 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: reassociating
Mar 25 22:57:18 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: disconnected, ok
Mar 25 22:57:18 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B not in local ACL, by default accept
Mar 25 22:57:18 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: connected
Mar 25 22:57:25 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: disconnected, received deauth: unspecified (1)
Mar 25 22:57:58 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B attempts to associate
Mar 25 22:57:58 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B not in local ACL, by default accept
Mar 25 22:57:58 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: connected
Mar 25 22:58:32 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B attempts to associate
Mar 25 22:58:32 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: reassociating
Mar 25 22:58:32 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: disconnected, ok
Mar 25 22:58:32 Cisco2611XM mikrotik_wireless: wlan1: 00:16:EA:29:1A:3B not in local ACL, by default accept
Mar 25 22:58:32 Cisco2611XM mikrotik_wireless: 00:16:EA:29:1A:3B@wlan1: connected

Вот лог, я тут особо ничего сверхплохого не вижу. Просмотрел весь за 25 число, много подобных сообщений от мобильных клиентов иосы-андроеды, но мой ноут отваливался только в районе 23х. Пойду попробую драйвер для интела поискать

Оцените статью
Все о Windows 10
Добавить комментарий

Не копируйте текст!
Adblock
detector