Had deauthenticated by sta reason class 2 error nonauth sta

Добрый вечер всем! Купил KN-1810-01RU Настроено 2 отдельные домашние Wi-Fi в 2,4 и 5 ггц, с разными названиями. Скрин настроек 2,4 Роуминг между частотами соответственно выключен Гостевые сети отключены, MESH отключена. Экраны, фильтры и т.д. не создавались, всё в состоянии "из коробки". Только с...

Добрый вечер всем!

Купил KN-1810-01RU

Настроено 2 отдельные домашние Wi-Fi в 2,4 и 5 ггц, с разными названиями.

Скрин настроек 2,4

image.thumb.png.74ed34bad6cd9338f644337cfc82598a.png

Роуминг между частотами соответственно выключен

image.png.a41aa9263733309b6b1dc65c18f12ebb.png

Гостевые сети отключены, MESH отключена. 

Экраны, фильтры и т.д. не создавались, всё в состоянии «из коробки». Только сделал статические IP устройствам.

Уровень сигнала от роутера до устройства — около -32db, перекрытия с другими мощными сетями нет.

На 5G до 4 устройств — все стабильные в любых режимах.

На 2,4G — до 3 устройств, одно из них периодически вылетает, остальные стабильные. Может вылетать даже когда роутер больше никто не трогает и нагрузки нет.

Устройство — смарт Asus ZenFone Max Pro (ZB602KL), поддерживает 802.11 b/g/n, стабильно работает в требуемом режиме на двух других роутерах — TP-Link и Asus

На устройстве всего-лишь WhatsApp — по статистике в пределах 20 мегабайт в минуту, т.е. ни о чём вообще.

В какую сторону копать и что делать? Нужна стабильная связь.

Логи — пример двух случаев:

Дек 17 21:05:50 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) had deauthenticated by STA (reason: class 3 error — nonassoc STA).
Дек 17 21:05:50 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) had associated successfully.
Дек 17 21:05:51 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) set key done in WPA2/WPA2PSK.
Дек 17 21:05:51 ndhcps
DHCPDISCOVER received from 0c:9d:92:d8:f1:5b.
Дек 17 21:05:51 ndhcps
making OFFER of 192.168.2.44 to 0c:9d:92:d8:f1:5b.
Дек 17 21:05:51 ndhcps
DHCPREQUEST received (STATE_SELECTING) for 192.168.2.44 from 0c:9d:92:d8:f1:5b.
Дек 17 21:05:51 ndhcps
sending ACK of 192.168.2.44 to 0c:9d:92:d8:f1:5b.
Дек 17 21:06:01 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) had deauthenticated by STA (reason: class 3 error — nonassoc STA).
Дек 17 21:06:01 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) had deauthenticated by STA (reason: class 3 error — nonassoc STA).
Дек 17 21:06:07 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) had associated successfully.
Дек 17 21:06:07 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) set key done in WPA2/WPA2PSK.
Дек 17 21:06:07 ndhcps
DHCPDISCOVER received from 0c:9d:92:d8:f1:5b.
Дек 17 21:06:07 ndhcps
making OFFER of 192.168.2.44 to 0c:9d:92:d8:f1:5b.
Дек 17 21:06:07 ndhcps
DHCPREQUEST received (STATE_SELECTING) for 192.168.2.44 from 0c:9d:92:d8:f1:5b.
Дек 17 21:06:07 ndhcps
sending ACK of 192.168.2.44 to 0c:9d:92:d8:f1:5b.
Дек 17 21:06:11 ndm
UPnP::Manager: a new nat rule appended.
Дек 17 21:06:11 ndm
UPnP::Manager: redirect rule added: udp GigabitEthernet1:1549 -> 192.168.2.44:41201.
Дек 17 21:06:11 ndm
UPnP::Manager: a new filter rule appended.
Дек 17 21:06:11 ndm
UPnP::Manager: forward rule added: udp GigabitEthernet1 -> 192.168.2.44:41201.

Дек 20 18:52:18 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) had deauthenticated by STA (reason: class 3 error — nonassoc STA).
Дек 20 18:52:18 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) had deauthenticated by STA (reason: class 3 error — nonassoc STA).
Дек 20 18:52:29 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) had associated successfully.
Дек 20 18:52:29 wmond
WifiMaster0/AccessPoint0: (MT7615) STA(0c:9d:92:d8:f1:5b) set key done in WPA2/WPA2PSK.
Дек 20 18:52:29 ndhcps
DHCPDISCOVER received from 0c:9d:92:d8:f1:5b.
Дек 20 18:52:29 ndhcps
making OFFER of 192.168.2.44 to 0c:9d:92:d8:f1:5b.
Дек 20 18:52:29 ndhcps
DHCPREQUEST received (STATE_SELECTING) for 192.168.2.44 from 0c:9d:92:d8:f1:5b.
Дек 20 18:52:29 ndhcps
sending ACK of 192.168.2.44 to 0c:9d:92:d8:f1:5b.
Дек 20 18:52:37 ndm
UPnP::Manager: a new nat rule appended.
Дек 20 18:52:37 ndm
UPnP::Manager: redirect rule added: udp GigabitEthernet1:6663 -> 192.168.2.44:49171.
Дек 20 18:52:37 ndm
UPnP::Manager: a new filter rule appended.
Дек 20 18:52:37 ndm
UPnP::Manager: forward rule added: udp GigabitEthernet1 -> 192.168.2.44:49171.


Edited December 20, 2020 by Alex Ostrenko

Источник

I was in a similar situation since two weeks and I found a solution yesterday (11th May) which is working so far (dual boot Ubuntu 20.04 / Windows, wireless card Broadcom 4325).

Surprisingly, my issue was not due to wireless driver or power management (tried many things in previous days, no improvement) but related to the ARP entry of my computer expiring on my local router (ARP stands for Address Resolution Protocol, it makes translation beetween IP addresses and MAC addresses).

To make it short (investigation details at the end of this answer) :

  • The ARP entries of my router have a timeout of 20 minutes,
  • For my computer it was decreasing up to expiration (which made me lose connection every 20 minutes),
  • And the same for other devices but for them it was automatically refreshed before expiring. I made network captures to find out what these devices were doing differently and found that their timeout is refreshed when they send an ARP request.

=> A solution appeared, I had to tell my computer to do the same ! (send ARP request)

Implementation of the solution

To send an ARP request, I used arping that you can install from its package :

sudo apt install arping

When you launch it, it says that it must run as root or with the cap_net_raw capability.
Since I didn’t wanted to launch it as root, I added the capability :

sudo setcap "cap_net_raw+ep" /usr/sbin/arping

I used the following command to send one ARP Request to my router (replace the IP address with the one relevant for you) :

arping -c 1 192.168.1.1

Then I wanted this command to run every 15 minutes to refresh the ARP entry regularly.
This is done by editing the file /etc/crontab :

sudo vi /etc/crontab

And adding this line at then end of the file :

*/15 * * * * <username> arping -c 1 192.168.1.1

That will make the ARP request sent every 15 minutes.

Detailed investigation process

Here are more details on how I discovered the issue :

  • Developped a widget telling me with timestamps when the connection is lost, and when it comes back.
  • Running a tcpdump capture until a disconnection/reconnection happens (purpose of the widget).
  • In the capture, found ARP messages around the issue time.
  • Looked into the ARP table of my pfSense router and saw that the timeout entry for my PC was always decreasing until expiration ; for other devices connected it decreased also but at some point it was resetting to default value (1200s in my case) before expiration.
  • Waited until expiration to confirm I observe the disconnection symptom on my computer (yes).
  • Made tcpdump captures on the router to see how others devices were successfully resetting their timeout : by sending ARP requests before it expires.
  • Installed arping as explained above and sent a test ARP request to the router : it resetted my expiration timeout to 1200s, victory ! o/

Finally, I don’t know why I never faced this issue when using Windows.
When checking the ARP table I see the entry becoms expired as well but then immediately get resetted to 20 minutes and I cannot see a network disconnection.

You may also wonder how to check the ARP table.
If you are using a pfSense router, it can be found in the submenu «Diagnostics > Table ARP» (to be translated in English, my menus are in French).
With another device, you will have to check its documentation.

But at the end, event if you can’t check the ARP table you can still try to insert the line in /etc/crontab and run it for a couple of hours/days. If your problem doesn’t reappear then it was the issue :-)

Hope this helps !

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account


Closed

Armiixteryx opened this issue

Jan 29, 2022

· 21 comments

Comments

@Armiixteryx

Hello,

I am getting an issue with this WiFi card that is included in my laptop.

Sometimes I lost connection to internet, but system WiFi keeps connected to the router. It is not an issue in my ISP because my other devices (mobile, tablet, Smart TV, etc) keeps working with internet just fine.

When that happens, I check the system logs (journalctl -f), and I get this message repeatedly:

wpa_supplicant[697]: wlp2s0: CTRL-EVENT-BEACON-LOSS

and in other moments I get following log, showing that the connection gets disconnected and system reconnects it:

kernel: wlp2s0: deauthenticated from 58:xx:xx:xx:xx:21 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
rtw_8821ce 0000:02:00.0: sta 58:xx:xx:xx:xx:21 with macid 0 left
wpa_supplicant[697]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=58:xx:xx:xx:xx:21 reason=6
wpa_supplicant[697]: wlp2s0: SME: Trying to authenticate with 58:xx:xx:xx:xx:21 (SSID='xxxx' freq=2427 MHz)
kernel: wlp2s0: authenticate with 58:xx:xx:xx:xx:21
wpa_supplicant[697]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
kernel: wlp2s0: send auth to 58:xx:xx:xx:xx:21 (try 1/3)
NetworkManager[488]: <info>  [1643497538.7599] device (wlp2s0): supplicant interface state: completed -> authenticating
kernel: wlp2s0: authenticated
wpa_supplicant[697]: wlp2s0: Trying to associate with 58:xx:xx:xx:xx:21 (SSID='xxxx' freq=2427 MHz)
NetworkManager[488]: <info>  [1643497538.7679] device (wlp2s0): supplicant interface state: authenticating -> associating
kernel: wlp2s0: associate with 58:xx:xx:xx:xx:21 (try 1/3)
kernel: wlp2s0: RX AssocResp from 58:xx:xx:xx:xx:21 (capab=0x431 status=0 aid=2)
kernel: rtw_8821ce 0000:02:00.0: sta 58:xx:xx:xx:xx:21 joined with macid 0
kernel: wlp2s0: associated
wpa_supplicant[697]: wlp2s0: Associated with 58:xx:xx:xx:xx:21
wpa_supplicant[697]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
NetworkManager[488]: <info>  [1643497538.7799] device (wlp2s0): supplicant interface state: associating -> 4way_handshake
wpa_supplicant[697]: wlp2s0: WPA: Key negotiation completed with 58:xx:xx:xx:xx:21 [PTK=CCMP GTK=CCMP]
wpa_supplicant[697]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 58:xx:xx:xx:xx:21 completed [id=0 id_str=]
NetworkManager[488]: <info>  [1643497538.8264] device (wlp2s0): supplicant interface state: 4way_handshake -> completed
kernel: rtw_8821ce 0000:02:00.0: failed to get tx report from firmware
systemd-resolved[470]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.
systemd-resolved[470]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.

@lwfinger

kernel: wlp2s0: deauthenticated from 58:xx:xx:xx:xx:21 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
rtw_8821ce 0000:02:00.0: sta 58:xx:xx:xx:xx:21 with macid 0 left
wpa_supplicant[697]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=58:xx:xx:xx:xx:21 reason=6

That CLASS2_FRAME_FROM_NONAUTH_STA reason for disconnecting is troubling. It makes me wonder if your AP is doing something that rtw88 is not expecting.

It is OK to obfuscate the MAC listings in stuff you post, but please leave the first 3 octants in the clear. They indicate the vendor of your equipment. The last 3 indicate the serial number of the device, and it is OK to replace then with x’s, but the vendor of the AP is valuable information.

I will check the current status of rtw88 in the kernel, and update this repo accordingly.

@lwfinger

As I said, the disconnect reason is troubling; however, most loss of beacon problems are due to AP and STA not handling sleep mode correctly. This is not the sleep that happens when you close the cover on your laptop, but a means of reducing power usage when wireless traffic is low.

To check this, we will disable that sleep mode. As root, create a file /etc/modprobe.d/50-rtw88.conf containing the following 2 lines:

options rtw_core disable_lps_deep=y
options rtw88_core disable_lps_deep=y

The first line handles drivers from this repo, and the second for rtw88 drivers built into the kernel.

@Armiixteryx

kernel: wlp2s0: deauthenticated from 58:xx:xx:xx:xx:21 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA) rtw_8821ce 0000:02:00.0: sta 58:xx:xx:xx:xx:21 with macid 0 left wpa_supplicant[697]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=58:xx:xx:xx:xx:21 reason=6

That CLASS2_FRAME_FROM_NONAUTH_STA reason for disconnecting is troubling. It makes me wonder if your AP is doing something that rtw88 is not expecting.

It is OK to obfuscate the MAC listings in stuff you post, but please leave the first 3 octants in the clear. They indicate the vendor of your equipment. The last 3 indicate the serial number of the device, and it is OK to replace then with x’s, but the vendor of the AP is valuable information.

I will check the current status of rtw88 in the kernel, and update this repo accordingly.

Here are the first octects: 58:d9:d5

@Armiixteryx

As I said, the disconnect reason is troubling; however, most loss of beacon problems are due to AP and STA not handling sleep mode correctly. This is not the sleep that happens when you close the cover on your laptop, but a means of reducing power usage when wireless traffic is low.

To check this, we will disable that sleep mode. As root, create a file /etc/modprobe.d/50-rtw88.conf containing the following 2 lines:

options rtw_core disable_lps_deep=y options rtw88_core disable_lps_deep=y

The first line handles drivers from this repo, and the second for rtw88 drivers built into the kernel.

Thank you, I have created the file. I will test and update this issue on results.

@lwfinger

Your AP vendor is Tenda Technology Co.,Ltd.Dongguan Branch.

@lwfinger

I just pushed an update to bring the code up to the kernel 5.18 value. Perhaps the changes will help your issue.

@bigangryrobot

@bigangryrobot

possibly related stack

22.06.21 21:30	wpa_supplicant	wlp1s0: CTRL-EVENT-BEACON-LOSS
22.06.21 21:30	kernel	------------[ cut here ]------------
22.06.21 21:30	kernel	purge skb(s) not reported by firmware
22.06.21 21:30	kernel	WARNING: CPU: 0 PID: 132630 at drivers/net/wireless/realtek/rtw88/tx.c:161 rtw_tx_report_purge_timer+0x20/0x50 [rtw88_core]
22.06.21 21:30	kernel	Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ecdh_generic ecc mc squashfs loop snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec rtw88_8822ce rtw88_8822c rtw88_pci snd_hda_core amdgpu rtw88_core joydev snd_hwdep mousedev soundwire_bus mac80211 vfat snd_soc_core fat edac_mce_amd kvm_amd snd_compress gpu_sched ac97_bus i2c_algo_bit snd_pcm_dmaengine huawei_wmi kvm hid_multitouch ledtrig_audio wmi_bmof cfg80211 ttm sparse_keymap irqbypass snd_pcm crct10dif_pclmul crc32_pclmul snd_timer drm_kms_helper ghash_clmulni_intel snd aesni_intel cec syscopyarea crypto_simd sysfillrect cryptd sysimgblt rfkill pcspkr glue_helper snd_rn_pci_acp3x sp5100_tco ccp libarc4 fb_sys_fops soundcore snd_pci_acp3x rapl i2c_piix4 wmi
22.06.21 21:30	kernel	 k10temp tpm_crb tpm_tis video tpm_tis_core tpm i2c_hid mac_hid rng_core pinctrl_amd acpi_cpufreq drm uinput sg fuse crypto_user agpgart ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 crc32c_intel serio_raw xhci_pci
22.06.21 21:30	kernel	CPU: 0 PID: 132630 Comm: ksystemlog Tainted: G        W         5.10.42-1-MANJARO #1
22.06.21 21:30	kernel	Hardware name: HUAWEI KLVL-WXX9/KLVL-WXX9-PCB, BIOS 1.10 12/31/2020
22.06.21 21:30	kernel	RIP: 0010:rtw_tx_report_purge_timer+0x20/0x50 [rtw88_core]
22.06.21 21:30	kernel	Code: 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 41 54 55 53 48 89 fb 48 c7 c7 18 7c e4 c0 e8 fd ff 9c e5 <0f> 0b 4c 8d 63 d8 4c 89 e7 e8 62 e9 a2 e5 48 8d 7b e0 48 89 c5 e8
22.06.21 21:30	kernel	RSP: 0000:ffffa5dec0003ec8 EFLAGS: 00010282
22.06.21 21:30	kernel	RAX: 0000000000000000 RBX: ffff8dec95086308 RCX: 0000000000000027
22.06.21 21:30	kernel	RDX: ffff8def7f418bb8 RSI: 0000000000000001 RDI: ffff8def7f418bb0
22.06.21 21:30	kernel	RBP: ffff8dec95086308 R08: 0000000000000000 R09: ffffa5dec0003d00
22.06.21 21:30	kernel	R10: ffffa5dec0003cf8 R11: ffffffffa74c9948 R12: ffffffffc0e32480
22.06.21 21:30	kernel	R13: dead000000000122 R14: ffffffffc0e32480 R15: ffff8def7f41cf80
22.06.21 21:30	kernel	FS:  00007f1329ff0880(0000) GS:ffff8def7f400000(0000) knlGS:0000000000000000
22.06.21 21:30	kernel	CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
22.06.21 21:30	kernel	CR2: 00002e5304b5d468 CR3: 000000011a5b0000 CR4: 0000000000350ef0
22.06.21 21:30	kernel	Call Trace:
22.06.21 21:30	kernel	 <IRQ>
22.06.21 21:30	kernel	 ? rtw_tx_write_data_h2c_get+0x90/0x90 [rtw88_core]
22.06.21 21:30	kernel	 call_timer_fn+0x29/0x130
22.06.21 21:30	kernel	 __run_timers.part.0+0x1cf/0x260
22.06.21 21:30	kernel	 ? rebalance_domains+0x108/0x3f0
22.06.21 21:30	kernel	 run_timer_softirq+0x26/0x50
22.06.21 21:30	kernel	 __do_softirq+0xcb/0x2ba
22.06.21 21:30	kernel	 asm_call_irq_on_stack+0x12/0x20
22.06.21 21:30	kernel	 </IRQ>
22.06.21 21:30	kernel	 do_softirq_own_stack+0x37/0x40
22.06.21 21:30	kernel	 irq_exit_rcu+0x9c/0xd0
22.06.21 21:30	kernel	 sysvec_apic_timer_interrupt+0x36/0x80
22.06.21 21:30	kernel	 ? asm_sysvec_apic_timer_interrupt+0xa/0x20
22.06.21 21:30	kernel	 asm_sysvec_apic_timer_interrupt+0x12/0x20
22.06.21 21:30	kernel	RIP: 0033:0x7f132e420511
22.06.21 21:30	kernel	Code: 66 0f 1f 84 00 00 00 00 00 c5 fe 7f 40 80 48 83 e8 80 c5 fe 7f 80 20 ff ff ff c5 fe 7f 80 40 ff ff ff c5 fe 7f 80 60 ff ff ff <48> 39 d0 76 da 48 83 c6 80 48 83 e6 80 48 8d 3c 31 48 89 d6 48 29
22.06.21 21:30	kernel	RSP: 002b:00007ffe67b38158 EFLAGS: 00000207
22.06.21 21:30	kernel	RAX: 00007f12bbb37714 RBX: 0000000000000450 RCX: 00007f12bbb36594
22.06.21 21:30	kernel	RDX: 00007f12bbb38644 RSI: 0000000000002130 RDI: 00007f12bbb36514
22.06.21 21:30	kernel	RBP: 00007f12bbb36514 R08: 00000000000021c0 R09: 0000000000ff0000
22.06.21 21:30	kernel	R10: 000000000000ff00 R11: 000001007f000100 R12: 00000000000021c0
22.06.21 21:30	kernel	R13: 000000000000023f R14: 00000000ffffffff R15: 000000000000084c
22.06.21 21:30	kernel	---[ end trace adbe2be71686001e ]---
22.06.21 21:30	kernel	rtw_8822ce 0000:01:00.0: timed out to flush queue 1
22.06.21 21:30	kernel	rtw_8822ce 0000:01:00.0: timed out to flush queue 2
22.06.21 21:30	kernel	rtw_8822ce 0000:01:00.0: sta 30:b1:xx:xx:xx:xx with macid 0 left
22.06.21 21:30	wpa_supplicant	wlp1s0: CTRL-EVENT-DISCONNECTED bssid=30:b1:xx:xx:xx:xx reason=4 locally_generated=1
22.06.21 21:30	wpa_supplicant	wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
22.06.21 21:30	NetworkManager	<info>  [1624390201.0714] device (wlp1s0): supplicant interface state: completed -> disconnected
22.06.21 21:30	wpa_supplicant	wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
22.06.21 21:30	NetworkManager	<info>  [1624390201.3536] device (wlp1s0): supplicant interface state: disconnected -> scanning
22.06.21 21:30	wpa_supplicant	wlp1s0: SME: Trying to authenticate with 30:b2:xx:xx:xx:xx (SSID='mySSID' freq=5180 MHz)
22.06.21 21:30	kernel	wlp1s0: authenticate with 30:b2:xx:xx:xx:xx
22.06.21 21:30	NetworkManager	<info>  [1624390201.7890] device (wlp1s0): supplicant interface state: scanning -> authenticating
22.06.21 21:30	kernel	wlp1s0: send auth to 30:b2:xx:xx:xx:xx (try 1/3)
22.06.21 21:30	kernel	wlp1s0: authenticated
22.06.21 21:30	wpa_supplicant	wlp1s0: Trying to associate with 30:b2:xx:xx:xx:xx (SSID='mySSID' freq=5180 MHz)
22.06.21 21:30	NetworkManager	<info>  [1624390201.7935] device (wlp1s0): supplicant interface state: authenticating -> associating
22.06.21 21:30	kernel	wlp1s0: associate with 30:b2:xx:xx:xx:xx (try 1/3)
22.06.21 21:30	wpa_supplicant	wlp1s0: Associated with 30:b2:xx:xx:xx:xx
22.06.21 21:30	wpa_supplicant	wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
22.06.21 21:30	wpa_supplicant	wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
22.06.21 21:30	kernel	wlp1s0: RX AssocResp from 30:b2:xx:xx:xx:xx (capab=0x1511 status=0 aid=46)
22.06.21 21:30	kernel	rtw_8822ce 0000:01:00.0: sta 30:b2:xx:xx:xx:xx joined with macid 0
22.06.21 21:30	kernel	wlp1s0: associated
22.06.21 21:30	NetworkManager	<info>  [1624390201.8078] device (wlp1s0): supplicant interface state: associating -> associated
22.06.21 21:30	NetworkManager	<info>  [1624390201.8079] device (wlp1s0): DHCPv4 lease renewal requested
22.06.21 21:30	NetworkManager	<info>  [1624390201.8616] dhcp4 (wlp1s0): canceled DHCP transaction
22.06.21 21:30	NetworkManager	<info>  [1624390201.8617] dhcp4 (wlp1s0): state changed bound -> terminated
22.06.21 21:30	NetworkManager	<info>  [1624390201.8623] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
22.06.21 21:30	NetworkManager	<info>  [1624390201.8624] device (wlp1s0): DHCPv6 lease renewal requested
22.06.21 21:30	NetworkManager	<info>  [1624390201.8625] dhcp6 (wlp1s0): canceled DHCP transaction
22.06.21 21:30	NetworkManager	<info>  [1624390201.8625] dhcp6 (wlp1s0): state changed bound -> terminated
22.06.21 21:30	NetworkManager	<info>  [1624390201.8628] dhcp6 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
22.06.21 21:30	kernel	wlp1s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 30:b2:xx:xx:xx:xx
22.06.21 21:30	NetworkManager	<info>  [1624390201.9608] device (wlp1s0): supplicant interface state: associated -> 4way_handshake
22.06.21 21:30	wpa_supplicant	wlp1s0: WPA: Key negotiation completed with 30:b2:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
22.06.21 21:30	wpa_supplicant	wlp1s0: CTRL-EVENT-CONNECTED - Connection to 30:b2:xx:xx:xx:xx completed [id=0 id_str=]
22.06.21 21:30	NetworkManager	<info>  [1624390201.9927] device (wlp1s0): supplicant interface state: 4way_handshake -> completed
22.06.21 21:30	wpa_supplicant	wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=351000
22.06.21 21:30	NetworkManager	<info>  [1624390202.8844] dhcp6 (wlp1s0): state changed unknown -> bound
22.06.21 21:30	dbus-daemon	[system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.362' (uid=0 pid=132196 comm="/usr/bin/NetworkManager --no-daemon ")
22.06.21 21:30	systemd	Starting Network Manager Script Dispatcher Service...
22.06.21 21:30	dbus-daemon	[system] Successfully activated service 'org.freedesktop.nm_dispatcher'
22.06.21 21:30	systemd	Started Network Manager Script Dispatcher Service.
22.06.21 21:30	audit	SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
22.06.21 21:30	kernel	audit: type=1130 audit(1624390202.893:500): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
22.06.21 21:30	NetworkManager	<info>  [1624390203.9183] dhcp4 (wlp1s0): state changed unknown -> bound, address=192.168.100.132
22.06.21 21:30	systemd	NetworkManager-dispatcher.service: Deactivated successfully.
22.06.21 21:30	audit	SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
22.06.21 21:30	kernel	audit: type=1131 audit(1624390212.660:501): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

@bigangryrobot

reviewing your pr you mention above f7e18c5 i think it will address this issue. I will find a box to run this on and report back

@bigangryrobot

also possibly related #82

@bigangryrobot

@bigangryrobot

@lwfinger

I have said it before, and I will likely have to say it again that I did not write this driver and I do not have any knowledge of the internals of the chip other than what I have learned from reading the code. If there is a build issue with a certain kernel, that is something I can usually handle.

You need to take the issue to the authors of the code as described in the final paragraph of README.md. When you submit the E-mail, be absolutely that it is plain text. Any HTML mail will be rejected by the server.

@lucassith

Unfortunately, the driver creators are lazy/unresponsive.

I wrote an email explaining my bug from another issue but so far have not received any reply. Such is unfortunately the charm of closed software that has problems.

For me, none of the driver issues were solved so I bought a WIFI transmitter that has open software and disabled the RTL drivers in the kernel. This is how my adventure with Realtek’s device ended.

At the very end, thank you @lwfinger for all the help and code you have prepared in this repo. I understand that you are not able to improve something that is out of your reach but you still do a great job.

@lwfinger

The author is not lazy, but he has many responsibilities. The software is no more closed than code for Intel or any other devices. The intellectual property in the implementation of the very complicated procedures of wifi5 or wifi6 is very valuable, thus the internals of the devices and the associated firmware are not made public.

@bigangryrobot

this is a very visible bug showing in a large number of cases and needs addressed somehow. I will try to contact the authors as suggested. If you are going to close this bug then close the associated ones too so we can at-least consolidate efforts.

@ObserverOfTime

This bug has been present in both this driver and the rtl8821ce one for years.
The authors are surely aware of it but they don’t seem to be doing anything to fix it.

@dubhater

I have not had any beacon loss for three days now since I made this change to the driver:

diff --git a/phy.c b/phy.c
index 6d8f006..d4f9d28 100644
--- a/phy.c
+++ b/phy.c
@@ -766,8 +766,8 @@ void rtw_phy_dynamic_mechanism(struct rtw_dev *rtwdev)
 {
 	/* for further calculation */
 	rtw_phy_statistics(rtwdev);
-	rtw_phy_dig(rtwdev);
-	rtw_phy_cck_pd(rtwdev);
+// 	rtw_phy_dig(rtwdev);
+// 	rtw_phy_cck_pd(rtwdev);
 	rtw_phy_ra_track(rtwdev);
 	rtw_phy_tx_path_diversity(rtwdev);
 	rtw_phy_cfo_track(rtwdev);

Also no disconnections and no delays in the browser.

So far I haven’t figured out why this helps. The two functions seem to do the same things that the old driver does, and I never had problems with that one. It’s really strange.

@lwfinger

The first of those two lines come from the original submission of the driver, thus the record has no information on why it was selected.

The commit message associated with the second line was as follows:
rtw88: add dynamic rrsr configuration

Register rrsr determines the response rate we send.
In field tests, using rate higher than current tx rate could lead
to difficulty for the receiving end to receive management/control
frames. Calculate current modulation level by tx rate then cross out
rate higher than those.

Adding that change to the repo could be dangerous. The code in phy.c is used by ALL the drivers in rtw88, and you have tested only on 8821ce. In addition, I have tested that device on my computer, and did not have a single disconnect in 4 days. If you want to have that change in your repo, use git to add and commit it locally. That way, any upstream changes will not overwrite it.

@dubhater

I was just hoping other people affected by this problem can test this «fix». Maybe it only helps on my system.

By the way, @lwfinger what RFE type is your device? What about everyone who’s affected by this problem? Mine is RFE 2.

(Also, you looked at the wrong commit in the blame, but it doesn’t matter anyway.)

@lwfinger

I think mine is RFE 1, but I could not find it in my logs.

The blame I looked at was from the mainline head. I think I got it right.

Источник

The following table describes the deauthentication reason codes.

Reason code

Meaning

0

Reserved.

1

Unspecified reason.

2

Previous authentication no longer valid.

3

Deauthenticated because sending station (STA) is leaving or has left
Independent Basic Service Set (IBSS) or ESS.

4

Disassociated due to inactivity.

5

Disassociated because WAP device is unable to handle all currently
associated STAs.

6

Class 2 frame received from nonauthenticated STA.

7

Class 3 frame received from nonassociated STA.

8

Disassociated because sending STA is leaving or has left Basic Service
Set (BSS).

9

STA requesting (re)association is not authenticated with responding STA.

10

Disassociated because the information in the Power Capability element is
unacceptable.

11

Disassociated because the information in the Supported Channels
element is unacceptable.

12

Disassociated due to BSS Transition Management.

13

Invalid element, that is, an element defined in this standard for which the
content does not meet the specifications in Clause 8.

14

Message integrity code (MIC) failure.

15

4-Way Handshake timeout.

16

Group Key Handshake timeout.

17

Element in 4-Way Handshake different from (Re)Association Request/
Probe Response/Beacon frame.

18

Invalid group cipher.

19

Invalid pairwise cipher.

20

Invalid AKMP.

21

Unsupported RSNE version.

22

Invalid RSNE capabilities.

23

IEEE 802.1X authentication failed.

24

Cipher suite rejected because of the security policy.

Источник
  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Official Flavours Support
  • Networking & Wireless
  • [ubuntu] Ubuntu 20.04 Wifi Disassociated / Deauth at exact 10 minute intervals

  1. Question Ubuntu 20.04 Wifi Disassociated / Deauth at exact 10 minute intervals

    I have noticed that my wifi disconnects frequently for a few seconds. I thought it was a network issue, but when i checked the dmesg logs, i see that it happens exactly with 10 minute intervals. I cannot seem to diagnose the issue?

    Can anyone help?

    Code:

    [Sat Jan 29 04:35:38 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)[Sat Jan 29 04:45:39 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 04:55:40 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 05:05:42 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 05:15:43 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 05:25:44 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 05:35:45 2022] wlp3s0: disassociated from 3c:84:6a:*:*:* (Reason: 1=UNSPECIFIED)
[Sat Jan 29 05:45:51 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 05:55:52 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 06:05:53 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 06:15:54 2022] wlp3s0: disassociated from 3c:84:6a:*:*:* (Reason: 1=UNSPECIFIED)
[Sat Jan 29 06:26:01 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 06:36:03 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 06:46:04 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 06:56:05 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 07:06:06 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 07:16:07 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 07:26:08 2022] wlp3s0: disassociated from 3c:84:6a:*:*:* (Reason: 1=UNSPECIFIED)
[Sat Jan 29 07:36:14 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 08:00:12 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 08:10:13 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 08:20:14 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 08:30:15 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 08:40:16 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 08:50:17 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 09:00:18 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 09:10:20 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 09:20:21 2022] wlp3s0: disassociated from 3c:84:6a:*:*:* (Reason: 1=UNSPECIFIED)
[Sat Jan 29 09:30:27 2022] wlp3s0: disassociated from 3c:84:6a:*:*:* (Reason: 1=UNSPECIFIED)
[Sat Jan 29 09:40:33 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 09:50:34 2022] wlp3s0: disassociated from 3c:84:6a:*:*:* (Reason: 1=UNSPECIFIED)
[Sat Jan 29 10:00:40 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 10:10:41 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 10:20:42 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 10:30:44 2022] wlp3s0: deauthenticated from 3c:84:6a:*:*:* (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[Sat Jan 29 10:40:45 2022] wlp3s0: disassociated from 3c:84:6a:*:*:* (Reason: 1=UNSPECIFIED)

    Last edited by shreyaslolage; February 3rd, 2022 at 06:38 AM.

  2. Re: Ubuntu 20.04 LTS Wifi

    Please run the wireless script from the sticky thread and show the outputs here

  3. Re: Ubuntu 20.04 LTS Wifi

    Sorry, I am new to forums and stuff. I have done everything specified in the Sticky Thread. My wifi disconnects every 10 minutes with Reason 1 disassociated or reason 6 deauth.

    [Wed Feb 2 21:12:06 2022] wlp3s0: disassociated from 3c:84:*:*:*:* (Reason: 1=UNSPECIFIED)

    Please check this pastebin as the script suggested I do this or post a tar file.
    https://pastebin.com/iVZ5NgUH

    Thanks and Regards

    Last edited by shreyaslolage; February 3rd, 2022 at 06:37 AM.

    Reason: Hiding mac address

  4. Re: Ubuntu 20.04 Wifi Disassociated / Deauth at exact 10 minute intervals

    Try deactivating the power management

    Code:

    sudo sed -i "s/wifi.powersave = 3/wifi.powersave = 2/g" /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
sudo systemctl restart network-manager.service

  5. Re: Ubuntu 20.04 Wifi Disassociated / Deauth at exact 10 minute intervals

    [Thu Feb 3 22:25:58 2022] wlp3s0: associate with 3c:84:6a:**:**:** (try 1/3)
    [Thu Feb 3 22:25:58 2022] wlp3s0: RX AssocResp from 3c:84:6a:**:**:** (capab=0x1011 status=0 aid=1)
    [Thu Feb 3 22:25:58 2022] wlp3s0: associated
    [Thu Feb 3 22:32:52 2022] wlp3s0: deauthenticating from 3c:84:6a:**:**:** by local choice (Reason: 3=DEAUTH_LEAVING)
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: [ 0] RxErr
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: can’t find device of ID00e5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: can’t find device of ID00e5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: can’t find device of ID00e5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: can’t find device of ID00e5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00002001/00002000
    [Thu Feb 3 22:32:53 2022] pcieport 0000:00:1c.5: [ 0] RxErr
    [Thu Feb 3 22:32:58 2022] wlp3s0: authenticate with 3c:84:6a:**:**:**
    [Thu Feb 3 22:32:58 2022] wlp3s0: send auth to 3c:84:6a:**:**:** (try 1/3)
    [Thu Feb 3 22:32:58 2022] wlp3s0: authenticated
    [Thu Feb 3 22:32:58 2022] wlp3s0: associate with 3c:84:6a:**:**:** (try 1/3)
    [Thu Feb 3 22:32:58 2022] wlp3s0: RX AssocResp from 3c:84:6a:**:**:** (capab=0x1011 status=0 aid=1)
    [Thu Feb 3 22:32:58 2022] wlp3s0: associated
    [Thu Feb 3 22:32:58 2022] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
    [Thu Feb 3 22:42:58 2022] wlp3s0: disassociated from 3c:84:6a:**:**:** (Reason: 1=UNSPECIFIED)
    [Thu Feb 3 22:43:04 2022] wlp3s0: authenticate with 3c:84:6a:**:**:**
    [Thu Feb 3 22:43:04 2022] wlp3s0: send auth to 3c:84:6a:**:**:** (try 1/3)
    [Thu Feb 3 22:43:04 2022] wlp3s0: authenticated
    [Thu Feb 3 22:43:04 2022] wlp3s0: associate with 3c:84:6a:**:**:** (try 1/3)
    [Thu Feb 3 22:43:04 2022] wlp3s0: RX AssocResp from 3c:84:6a:**:**:** (capab=0x1011 status=0 aid=1)
    [Thu Feb 3 22:43:04 2022] wlp3s0: associated

    Did not work Is there something more i can share? That deauth is the network manager restart i did after changing the powersave settings.

    You can see again exactly 10 minutes after the successful connection it disconnected and reconnected.

  6. Re: Ubuntu 20.04 Wifi Disassociated / Deauth at exact 10 minute intervals

    Feb 04 00:55:03 w1sd0m-Inspiron whoopsie[1425]: [00:55:03] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
    Feb 04 00:55:03 w1sd0m-Inspiron whoopsie[1425]: [00:55:03] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
    Feb 04 00:55:03 w1sd0m-Inspiron whoopsie[1425]: [00:55:03] online
    Feb 04 00:55:13 w1sd0m-Inspiron systemd[1]: NetworkManager-dispatcher.service: Succeeded.
    Feb 04 01:01:19 w1sd0m-Inspiron gnome-shell[4881]: [4947:4:0204/010119.473450:ERROR:node_controller.cc(585)] Trying to re-add dropped peer E887F84C11DF3A0C.82C457E73090852E
    Feb 04 01:03:17 w1sd0m-Inspiron gnome-shell[4881]: [4947:4:0204/010317.768235:ERROR:node_controller.cc(585)] Trying to re-add dropped peer 9117EB32FD856292.F82C6F62603DCFD7
    Feb 04 01:04:26 w1sd0m-Inspiron kernel: wlp3s0: disassociated from 3c:84:6a:**:**:** (Reason: 1=UNSPECIFIED)
    Feb 04 01:04:26 w1sd0m-Inspiron wpa_supplicant[1059]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=3c:84:6a:**:**:** reason=1
    Feb 04 01:04:26 w1sd0m-Inspiron wpa_supplicant[1059]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
    Feb 04 01:04:26 w1sd0m-Inspiron NetworkManager[55748]: <warn> [1643916866.2856] sup-iface[0x561034fcb910,wlp3s0]: connection disconnected (reason 1)
    Feb 04 01:04:26 w1sd0m-Inspiron NetworkManager[55748]: <info> [1643916866.2914] device (wlp3s0): supplicant interface state: completed -> disconnected
    Feb 04 01:04:26 w1sd0m-Inspiron NetworkManager[55748]: <info> [1643916866.2915] device (p2p-dev-wlp3s0): supplicant management interface state: completed -> disconnected
    Feb 04 01:04:26 w1sd0m-Inspiron gnome-shell[1679]: An active wireless connection, in infrastructure mode, involves no access point?
    Feb 04 01:04:26 w1sd0m-Inspiron NetworkManager[55748]: <info> [1643916866.3906] device (wlp3s0): supplicant interface state: disconnected -> scanning
    Feb 04 01:04:26 w1sd0m-Inspiron NetworkManager[55748]: <info> [1643916866.3907] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning
    Feb 04 01:04:26 w1sd0m-Inspiron gnome-shell[4881]: [4875:4908:0204/010426.654984:ERROR:connection_factory_impl.cc(425 )] Failed to connect to MCS endpoint with error -106
    Feb 04 01:04:27 w1sd0m-Inspiron wpa_supplicant[1059]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
    Feb 04 01:04:31 w1sd0m-Inspiron wpa_supplicant[1059]: wlp3s0: SME: Trying to authenticate with 3c:84:6a:**:**:** (SSID=’Tz_5G’ freq=5180 MHz)
    Feb 04 01:04:31 w1sd0m-Inspiron kernel: wlp3s0: authenticate with 3c:84:6a:**:**:**
    Feb 04 01:04:31 w1sd0m-Inspiron kernel: wlp3s0: send auth to 3c:84:6a:**:**:** (try 1/3)
    Feb 04 01:04:31 w1sd0m-Inspiron kernel: wlp3s0: authenticated
    Feb 04 01:04:31 w1sd0m-Inspiron NetworkManager[55748]: <info> [1643916871.2634] device (wlp3s0): supplicant interface state: scanning -> authenticating
    Feb 04 01:04:31 w1sd0m-Inspiron NetworkManager[55748]: <info> [1643916871.2635] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> authenticating
    Feb 04 01:04:31 w1sd0m-Inspiron wpa_supplicant[1059]: wlp3s0: Trying to associate with 3c:84:6a:**:**:** (SSID=’Tz_5G’ freq=5180 MHz)
    Feb 04 01:04:31 w1sd0m-Inspiron kernel: wlp3s0: associate with 3c:84:6a:**:**:** (try 1/3)
    Feb 04 01:04:31 w1sd0m-Inspiron kernel: wlp3s0: RX AssocResp from 3c:84:6a:**:**:** (capab=0x1011 status=0 aid=1)
    Feb 04 01:04:31 w1sd0m-Inspiron wpa_supplicant[1059]: wlp3s0: Associated with 3c:84:6a:**:**:**
    Feb 04 01:04:31 w1sd0m-Inspiron wpa_supplicant[1059]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
    Feb 04 01:04:31 w1sd0m-Inspiron kernel: wlp3s0: associated

    Herer are the sudo journalctl logs

Tags for this Thread

Bookmarks

Bookmarks


Posting Permissions

Источник

Deauthentication Reason Code Table

The following table describes the deauthentication reason codes.

Previous authentication no longer valid.

Deauthenticated because sending station (STA) is leaving or has left Independent Basic Service Set (IBSS) or ESS.

Disassociated due to inactivity.

Disassociated because WAP device is unable to handle all currently associated STAs.

Class 2 frame received from nonauthenticated STA.

Class 3 frame received from nonassociated STA.

Disassociated because sending STA is leaving or has left Basic Service Set (BSS).

STA requesting (re)association is not authenticated with responding STA.

Disassociated because the information in the Power Capability element is unacceptable.

Disassociated because the information in the Supported Channels element is unacceptable.

Disassociated due to BSS Transition Management.

Invalid element, that is, an element defined in this standard for which the content does not meet the specifications in Clause 8.

Message integrity code (MIC) failure.

4-Way Handshake timeout.

Group Key Handshake timeout.

Element in 4-Way Handshake different from (Re)Association Request/ Probe Response/Beacon frame.

Invalid group cipher.

Invalid pairwise cipher.

Unsupported RSNE version.

Invalid RSNE capabilities.

IEEE 802.1X authentication failed.

Cipher suite rejected because of the security policy.

Источник

Reason class 3 error nonassoc sta

I’m having some annoying wifi problems.
I run a pretty minimal Ubuntu 14.04.2 server installation with LXDE (mostly based on this guide: http://thepcspy.com/read/building-a-kiosk-computer-ubuntu-1404-chrome/)

I run this on a Gigabyte Brix GB-BXCEH-3205.

I’m having some annoying wifi connection problems. I’ve tried this both with the internal wifi adapter and with a external one: TL-WN722N.
The problem is that regularly I cannot connect from other machines to the Brix anymore. I try this with SSH. Usually when I leave the machine alone for a few hours and try to connect I have no access through SSH and I also don’t see the machine when I do a scan of my network. When I enter the terminal on the Brix and try ‘ping www.google.nl (http://www.google.nl)’ it always works. After that I can also again connect from the outside to the machine again.

I get a lot of ‘deauthenticated’ messages in my syslog. Seems related, but so far I could not prove the relation 100% by looking at the times.

I tried to add a lot of debug info. This is all with a working internet connection at the moment, but problems earlier this day (around 14.42 in log).
Any help would be much appreciated. It is crippling my setup.

Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.262119] wlan0: deauthenticated from 50:60:28:2a:34:83 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.311620] cfg80211: Calling CRDA to update world regulatory domain
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.314366] cfg80211: World regulatory domain updated:
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.314371] cfg80211: DFS Master region: unset
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.314372] cfg80211: (start_freq — end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.314376] cfg80211: (2402000 KHz — 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.314378] cfg80211: (2457000 KHz — 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.314380] cfg80211: (2474000 KHz — 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.314382] cfg80211: (5170000 KHz — 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:16:27 pandora-client-1 kernel: [ 3842.314384] cfg80211: (5735000 KHz — 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.799855] wlan0: authenticate with 50:60:28:29:b3:13
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.803012] wlan0: send auth to 50:60:28:29:b3:13 (try 1/3)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.809709] wlan0: authenticated
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.810111] wlan0: associate with 50:60:28:29:b3:13 (try 1/3)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.814802] wlan0: RX AssocResp from 50:60:28:29:b3:13 (capab=0x1011 status=0 aid=5)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.816550] wlan0: associated
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.816636] cfg80211: Calling CRDA for country: NL
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.821391] cfg80211: Regulatory domain changed to country: NL
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.821395] cfg80211: DFS Master region: unset
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.821397] cfg80211: (start_freq — end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.821400] cfg80211: (2402000 KHz — 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.821402] cfg80211: (5170000 KHz — 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.821404] cfg80211: (5250000 KHz — 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm), (0 s)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.821406] cfg80211: (5490000 KHz — 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm), (0 s)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.821408] cfg80211: (57240000 KHz — 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Jul 16 13:16:30 pandora-client-1 kernel: [ 3845.896812] wlan0: Limiting TX power to 19 (30 — 11) dBm as advertised by 50:60:28:29:b3:13
Jul 16 13:17:01 pandora-client-1 CRON[1853]: (root) CMD ( cd / && run-parts —report /etc/cron.hourly)
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.922679] wlan0: deauthenticated from 50:60:28:29:b3:13 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.962118] cfg80211: Calling CRDA to update world regulatory domain
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.964864] cfg80211: World regulatory domain updated:
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.964869] cfg80211: DFS Master region: unset
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.964870] cfg80211: (start_freq — end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.964874] cfg80211: (2402000 KHz — 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.964876] cfg80211: (2457000 KHz — 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.964878] cfg80211: (2474000 KHz — 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.964880] cfg80211: (5170000 KHz — 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:48:37 pandora-client-1 kernel: [ 5771.964882] cfg80211: (5735000 KHz — 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.199126] wlan0: authenticate with 50:60:28:2a:34:93
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.202162] wlan0: send auth to 50:60:28:2a:34:93 (try 1/3)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.203839] wlan0: authenticated
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.204696] wlan0: associate with 50:60:28:2a:34:93 (try 1/3)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.208795] wlan0: RX AssocResp from 50:60:28:2a:34:93 (capab=0x1011 status=0 aid=6)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.210255] wlan0: associated
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.210313] cfg80211: Calling CRDA for country: NL
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215083] wlan0: Limiting TX power to 19 (30 — 11) dBm as advertised by 50:60:28:2a:34:93
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215112] cfg80211: Regulatory domain changed to country: NL
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215114] cfg80211: DFS Master region: unset
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215116] cfg80211: (start_freq — end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215119] cfg80211: (2402000 KHz — 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215121] cfg80211: (5170000 KHz — 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215123] cfg80211: (5250000 KHz — 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm), (0 s)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215125] cfg80211: (5490000 KHz — 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm), (0 s)
Jul 16 13:48:40 pandora-client-1 kernel: [ 5775.215127] cfg80211: (57240000 KHz — 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Jul 16 14:17:01 pandora-client-1 CRON[2042]: (root) CMD ( cd / && run-parts —report /etc/cron.hourly)
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.601113] wlan0: deauthenticated from 50:60:28:2a:34:93 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.661884] cfg80211: Calling CRDA to update world regulatory domain
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.666999] cfg80211: World regulatory domain updated:
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.667005] cfg80211: DFS Master region: unset
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.667006] cfg80211: (start_freq — end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.667010] cfg80211: (2402000 KHz — 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.667012] cfg80211: (2457000 KHz — 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.667014] cfg80211: (2474000 KHz — 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.667016] cfg80211: (5170000 KHz — 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:18:53 pandora-client-1 kernel: [ 7587.667018] cfg80211: (5735000 KHz — 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.946019] wlan0: authenticate with 50:60:28:2a:34:83
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.949394] wlan0: send auth to 50:60:28:2a:34:83 (try 1/3)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.952254] wlan0: authenticated
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.956358] wlan0: associate with 50:60:28:2a:34:83 (try 1/3)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.972445] wlan0: RX AssocResp from 50:60:28:2a:34:83 (capab=0x1431 status=0 aid=1)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.976508] wlan0: associated
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.976574] cfg80211: Calling CRDA for country: NL
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.979355] cfg80211: Regulatory domain changed to country: NL
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.979360] cfg80211: DFS Master region: unset
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.979362] cfg80211: (start_freq — end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.979365] cfg80211: (2402000 KHz — 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.979367] cfg80211: (5170000 KHz — 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.979369] cfg80211: (5250000 KHz — 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm), (0 s)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.979371] cfg80211: (5490000 KHz — 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm), (0 s)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7590.979373] cfg80211: (57240000 KHz — 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Jul 16 14:18:57 pandora-client-1 kernel: [ 7591.073082] wlan0: Limiting TX power to 5 (20 — 15) dBm as advertised by 50:60:28:2a:34:83
Jul 16 14:44:53 pandora-client-1 kernel: [ 9146.869946] usb 1-4: new low-speed USB device number 3 using xhci_hcd
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.073489] usb 1-4: New USB device found, idVendor=04d9, idProduct=1603
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.073495] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.073498] usb 1-4: Product: USB Keyboard
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.073500] usb 1-4: Manufacturer:
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.073660] usb 1-4: ep 0x81 — rounding interval to 64 microframes, ep desc says 80 microframes
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.073668] usb 1-4: ep 0x82 — rounding interval to 64 microframes, ep desc says 80 microframes
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.109569] usbcore: registered new interface driver usbhid
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.109573] usbhid: USB HID core driver
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.112511] input: USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:04D9:1603.0001/input/input9
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.166216] hid-generic 0003:04D9:1603.0001: input,hidraw0: USB HID v1.10 Keyboard [ USB Keyboard] on usb-0000:00:14.0-4/input0
Jul 16 14:44:53 pandora-client-1 kernel: [ 9147.168609] input: USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:04D9:1603.0002/input/input10
Jul 16 14:44:54 pandora-client-1 kernel: [ 9147.222177] hid-generic 0003:04D9:1603.0002: input,hidraw1: USB HID v1.10 Device [ USB Keyboard] on usb-0000:00:14.0-4/input1
Jul 16 14:44:55 pandora-client-1 kernel: [ 9148.777242] usb 1-3: new low-speed USB device number 4 using xhci_hcd
Jul 16 14:44:55 pandora-client-1 kernel: [ 9148.908419] usb 1-3: New USB device found, idVendor=046d, idProduct=c05a
Jul 16 14:44:55 pandora-client-1 kernel: [ 9148.908427] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 16 14:44:55 pandora-client-1 kernel: [ 9148.908430] usb 1-3: Product: USB Optical Mouse
Jul 16 14:44:55 pandora-client-1 kernel: [ 9148.908432] usb 1-3: Manufacturer: Logitech
Jul 16 14:44:55 pandora-client-1 kernel: [ 9148.908673] usb 1-3: ep 0x81 — rounding interval to 64 microframes, ep desc says 80 microframes
Jul 16 14:44:55 pandora-client-1 kernel: [ 9148.910902] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C05A.0003/input/input11
Jul 16 14:44:55 pandora-client-1 kernel: [ 9148.965391] hid-generic 0003:046D:C05A.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:14.0-3/input0
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.591530] wlan0: deauthenticated from 50:60:28:2a:34:83 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.701443] cfg80211: Calling CRDA to update world regulatory domain
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.704724] cfg80211: World regulatory domain updated:
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.704729] cfg80211: DFS Master region: unset
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.704731] cfg80211: (start_freq — end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.704734] cfg80211: (2402000 KHz — 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.704737] cfg80211: (2457000 KHz — 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.704739] cfg80211: (2474000 KHz — 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.704741] cfg80211: (5170000 KHz — 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:45:28 pandora-client-1 kernel: [ 9181.704742] cfg80211: (5735000 KHz — 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.002318] wlan0: authenticate with 50:60:28:29:b3:13
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.005709] wlan0: send auth to 50:60:28:29:b3:13 (try 1/3)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.007127] wlan0: authenticated
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.008146] wlan0: associate with 50:60:28:29:b3:13 (try 1/3)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.012786] wlan0: RX AssocResp from 50:60:28:29:b3:13 (capab=0x1011 status=0 aid=3)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.015275] wlan0: associated
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.015330] cfg80211: Calling CRDA for country: NL
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.018073] cfg80211: Regulatory domain changed to country: NL
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.018078] cfg80211: DFS Master region: unset
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.018079] cfg80211: (start_freq — end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.018083] cfg80211: (2402000 KHz — 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.018085] cfg80211: (5170000 KHz — 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.018087] cfg80211: (5250000 KHz — 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm), (0 s)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.018089] cfg80211: (5490000 KHz — 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm), (0 s)
Jul 16 14:45:31 pandora-client-1 kernel: [ 9185.018091] cfg80211: (57240000 KHz — 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Jul 16 14:45:32 pandora-client-1 kernel: [ 9185.380327] wlan0: Limiting TX power to 19 (30 — 11) dBm as advertised by 50:60:28:29:b3:13

Linux pandora-client-1 4.1.1-040101-generic #201507030635 SMP Fri Jul 3 10:38:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

lspci -nnk | grep -iA2 net

02:00.0 Network controller [0280]: Intel Corporation Wireless 3160 [8086:08b3] (rev 83)
Subsystem: Intel Corporation Dual Band Wireless AC 3160 [8086:8070]
Kernel driver in use: iwlwifi
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
Subsystem: Gigabyte Technology Co., Ltd Motherboard [1458:e000]
Kernel driver in use: r8169

Bus 003 Device 002: ID 8087:8001 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 005: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 006: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:720 (720.0 B) TX bytes:720 (720.0 B)

p3p1 Link encap:Ethernet HWaddr fc:aa:14:eb:d9:cc
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr f4:06:69:17:5d:45
inet addr:10.100.0.45 Bcast:10.100.255.255 Mask:255.255.0.0
inet6 addr: fe80::f606:69ff:fe17:5d45/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65963 errors:0 dropped:2 overruns:0 frame:0
TX packets:21020 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:88296881 (88.2 MB) TX bytes:2617808 (2.6 MB)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.100.0.1 0.0.0.0 UG 0 0 0 wlan0
10.100.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0

wlan0 IEEE 802.11abgn ESSID:»DHS_Offices»
Mode:Managed Frequency:5.5 GHz Access Point: 50:60:28:29:B3:13
Bit Rate=6 Mb/s Tx-Power=19 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=31/70 Signal level=-79 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:3 Invalid misc:5 Missed beacon:0

p3p1 no wireless extensions.

lo no wireless extensions.

Module Size Used by
hid_generic 16384 0
usbhid 53248 0
ctr 16384 2
ccm 20480 2
arc4 16384 2
intel_rapl 20480 0
iosf_mbi 16384 1 intel_rapl
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
coretemp 16384 0
kvm_intel 155648 0
kvm 491520 1 kvm_intel
iwlmvm 294912 0
mac80211 745472 1 iwlmvm
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
ghash_clmulni_intel 16384 0
cryptd 20480 1 ghash_clmulni_intel
btusb 49152 0
iwlwifi 200704 1 iwlmvm
btbcm 16384 1 btusb
btintel 16384 1 btusb
bluetooth 516096 4 btbcm,btusb,btintel
cfg80211 552960 3 iwlwifi,mac80211,iwlmvm
snd_hda_codec_hdmi 53248 1
lpc_ich 24576 0
snd_soc_rt5640 94208 0
snd_hda_codec_realtek 90112 1
snd_hda_codec_generic 77824 1 snd_hda_codec_realtek
snd_soc_rl6231 16384 1 snd_soc_rt5640
snd_hda_intel 32768 1
i915 1097728 5
snd_hda_controller 32768 1 snd_hda_intel
snd_hda_codec 122880 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_c odec_generic,snd_hda_intel,snd_hda_controller
snd_hda_core 32768 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_c odec_generic,snd_hda_codec,snd_hda_controller
snd_hwdep 16384 1 snd_hda_codec
snd_soc_core 196608 1 snd_soc_rt5640
snd_compress 20480 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_pcm 106496 8 snd_soc_rt5640,snd_soc_core,snd_hda_codec_hdmi,snd _hda_codec,snd_hda_intel,snd_hda_controller,snd_pc m_dmaengine
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
snd_rawmidi 32768 1 snd_seq_midi
video 20480 1 i915
snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
dw_dmac 16384 0
drm_kms_helper 126976 1 i915
snd_timer 32768 2 snd_pcm,snd_seq
dw_dmac_core 28672 1 dw_dmac
snd_soc_sst_acpi 16384 0
drm 352256 6 i915,drm_kms_helper
i2c_hid 20480 0
hid 114688 3 i2c_hid,hid_generic,usbhid
mei_me 24576 0
snd 86016 14 snd_hda_codec_realtek,snd_soc_core,snd_hwdep,snd_t imer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmid i,snd_hda_codec_generic,snd_hda_codec,snd_hda_inte l,snd_seq_device,snd_compress
8250_dw 16384 0
i2c_designware_platform 16384 0
mei 90112 1 mei_me
i2c_designware_core 16384 1 i2c_designware_platform
spi_pxa2xx_platform 24576 0
shpchp 40960 0
tpm_crb 16384 0
soundcore 16384 1 snd
acpi_pad 20480 0
mac_hid 16384 0
i2c_algo_bit 16384 1 i915
lp 20480 0
nls_iso8859_1 16384 1
parport 45056 1 lp
sdhci_acpi 16384 0
sdhci 45056 1 sdhci_acpi
r8169 81920 0
mii 16384 1 r8169
ahci 36864 3
libahci 32768 1 ahci

wlan0 Scan completed :
Cell 01 — Address: 50:60:28:29:B3:13
Channel:100
Frequency:5.5 GHz (Channel 100)
Quality=28/70 Signal level=-82 dBm
Encryption key:on
ESSID:»DHS_Offices»
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000099025300dda
Extra: Last beacon: 1153368ms ago
IE: Unknown: 000B4448535F4F666669636573
IE: Unknown: 01088C129824B048606C
IE: Unknown: 030164
IE: Unknown: 070A4E4C20240817640B1E00
IE: Unknown: 20010B
IE: Unknown: 23021300
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 3302510B
IE: Unknown: 46050200010000
IE: Unknown: 2D1A6C001BFFFF000000000000000000000000000000000000 000000
IE: Unknown: 3D1664080800000000000000000000000000000000000000
IE: Unknown: DD180050F2020101820003A5000027A5000042435E0062432F 00
IE: Unknown: DD1E00904C336C001BFFFF0000000000000000000000000000 00000000000000
IE: Unknown: DD1A00904C3464080800000000000000000000000000000000 000000
IE: Unknown: DD42000F7DF950602829B300BF81E826585200130000000000 000000000001FC000000000000000000000000000000000000 00000000000000000000000000000000FA44

p3p1 Interface doesn’t support scanning.

lo Interface doesn’t support scanning.

auto wlan0
iface wlan0 inet static
pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
post-down killall -q wpa_supplicant
address 10.100.0.45
gateway 10.100.0.1
netmask 255.255.0.0
dns-nameservers 8.8.8.8 8.8.4.4

network= <
ssid=»DHS_Offices»
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
#psk=»t03ts3nb0rd»
psk=bb699f3efe3cc51f29a40b2371c2635d1283a4af98a6b5 0f856db28bde45d20f
>

Источник

Источник
WIFI_REASON_LOCAL_GENERATE_FROM_USER 

Locally Generate Disconnect from user side

WIFI_REASON_UNSPECIFIED 

Unspecified reason

WIFI_REASON_PREV_AUTH_NOT_VALID 

Previous authentication no longer valid

WIFI_REASON_DEAUTH_LEAVING 

Deauthenticated because sending STA is leaving (or has left) IBSS or ESS

WIFI_REASON_DISASSOC_DUE_TO_INACTIVITY 

Disassociated due to inactivity

WIFI_REASON_DISASSOC_AP_BUSY 

Disassociated because AP is unable to handle all currently associated STAs

WIFI_REASON_CLASS2_FRAME_FROM_NONAUTH_STA 

Class 2 frame received from nonauthenticated STA

WIFI_REASON_CLASS3_FRAME_FROM_NONASSOC_STA 

Class 3 frame received from nonassociated STA

WIFI_REASON_DISASSOC_STA_HAS_LEFT 

Disassociated because sending STA is leaving (or has left) BSS

WIFI_REASON_STA_REQ_ASSOC_WITHOUT_AUTH 

STA requesting (re)association is not authenticated with responding STA

WIFI_REASON_PWR_CAPABILITY_NOT_VALID 

Disassociated because the information in the Power Capability element is unacceptable

WIFI_REASON_SUPPORTED_CHANNEL_NOT_VALID 

Disassociated because the information in the Supported Channels element is unacceptable

WIFI_REASON_INVALID_IE 

Invalid element i.e., an element defined in this standard for which the content does not meet the specifications in Clause 8

WIFI_REASON_MICHAEL_MIC_FAILURE 

Message Integrity Code (MIC) failure

WIFI_REASON_4WAY_HANDSHAKE_TIMEOUT 

4-Way Handshake timeout

WIFI_REASON_GROUP_KEY_UPDATE_TIMEOUT 

Group Key Handshake timeout

WIFI_REASON_IE_IN_4WAY_DIFFERS 

Element in 4-Way Handshake different from (Re)Association Request/Probe Response/Beacon frame

WIFI_REASON_GROUP_CIPHER_NOT_VALID 

Invalid group cipher

WIFI_REASON_PAIRWISE_CIPHER_NOT_VALID 

Invalid pairwise cipher

WIFI_REASON_AKMP_NOT_VALID 

Invalid AKMP

WIFI_REASON_UNSUPPORTED_RSN_IE_VERSION 

Unsupported RSNE version

WIFI_REASON_INVALID_RSN_IE_CAPAB 

Invalid RSNE capabilities

WIFI_REASON_IEEE_802_1X_AUTH_FAILED 

IEEE 802.1X authentication failed

WIFI_REASON_CIPHER_SUITE_REJECTED 

Cipher suite rejected because of the security policy

WIFI_REASON_TDLS_TEARDOWN_UNREACHABLE 

TDLS direct-link teardown due to TDLS peer STA unreachable via the TDLS direct link

WIFI_REASON_TDLS_TEARDOWN_UNSPECIFIED 

TDLS direct-link teardown for unspecified reason

WIFI_REASON_DISASSOC_LOW_ACK 

Disassociated because excessive number of frames need to be acknowledged, but are not acknowledged due to AP transmissions and/or poor channel conditions

WIFI_REASON_MESH_PEERING_CANCELLED 

SME cancels the mesh peering instance with the reason other than reaching the maximum number of peer mesh STAs

WIFI_REASON_MESH_MAX_PEERS 

The mesh STA has reached the supported maximum number of peer mesh STAs

WIFI_REASON_MESH_CONFIG_POLICY_VIOLATION 

The received information violates the Mesh Configuration policy configured in the mesh STA profile

WIFI_REASON_MESH_CLOSE_RCVD 

The mesh STA has received a Mesh Peering Close message requesting to close the mesh peering

WIFI_REASON_MESH_MAX_RETRIES 

The mesh STA has resent dot11MeshMaxRetries Mesh Peering Open messages, without receiving a Mesh Peering Confirm message

WIFI_REASON_MESH_CONFIRM_TIMEOUT 

The confirmTimer for the mesh peering instance times out

WIFI_REASON_MESH_INVALID_GTK 

The mesh STA fails to unwrap the GTK or the values in the wrapped contents do not match

WIFI_REASON_MESH_INCONSISTENT_PARAMS 

The mesh STA receives inconsistent information about the mesh parameters between Mesh Peering Management frames

WIFI_REASON_MESH_INVALID_SECURITY_CAP 

The mesh STA does not have proxy information for this external destination

Источник

Понравилась статья? Поделить с друзьями:
  • Half life как изменить fov
  • Habitat 2 ошибка 01 как исправить
  • Half life source engine error
  • Half life opposing force fatal error
  • Half life fatal error failed to initialize authentication interface exiting