RinCat / RTL88x2BU-Linux-Driver

Realtek RTL88x2BU WiFi USB Driver for Linux
GNU General Public License v2.0
1.25k stars 197 forks source link

Wifi-Password not accepted #67

Open guckuck opened 3 years ago

guckuck commented 3 years ago

I cannot connect to my wifi-network. The password is not accepted. The password is correct.

I can connect to a wifi-network without password (for example Telekom-FON).

My System: TP-Link Archer T3U Plus lubuntu 18.04 (4.15.0-128-generic) 32bit Speedport Pro Plus (German Telekom) (3 wifis: 2,4 GHz, 5 Ghz with same ssid, TELEKOM-FON).


syslog:
Jan  3 23:49:13 tux kernel: [ 1223.816135] RTW: unknown vendor specific information element ignored (vendor OUI 50:6f:9a len=7)
Jan  3 23:49:13 tux kernel: [ 1223.816138] RTW: IEEE 802.11 element parse ignored unknown element (id=108 elen=2)
Jan  3 23:49:13 tux kernel: [ 1223.816141] RTW: IEEE 802.11 element parse ignored unknown element (id=107 elen=7)
Jan  3 23:49:13 tux kernel: [ 1223.904815] RTW: [HALMAC][TRACE]cfg_usb_rx_agg_88xx ===>
Jan  3 23:49:13 tux kernel: [ 1223.905686] RTW: [HALMAC][TRACE]cfg_usb_rx_agg_88xx <===
Jan  3 23:49:13 tux kernel: [ 1223.905812] RTW: [HALMAC][TRACE]cfg_csi_rate_88xx ===>
Jan  3 23:49:13 tux kernel: [ 1223.906440] RTW: rtl8822b_fillh2ccmd(wlx984827a71691): id=0x42 buf= 0x00 0x00 0x36 0x40 0x00 0x00 0x00
Jan  3 23:49:13 tux kernel: [ 1224.020849] RTW: IEEE 802.11 element parse ignored unknown element (id=7 elen=52)
Jan  3 23:49:13 tux kernel: [ 1224.020865] RTW: IEEE 802.11 element parse ignored unknown element (id=32 elen=1)
Jan  3 23:49:13 tux kernel: [ 1224.020867] RTW: IEEE 802.11 element parse ignored unknown element (id=195 elen=4)
Jan  3 23:49:13 tux kernel: [ 1224.020870] RTW: unknown vendor specific information element ignored (vendor OUI 00:26:86 len=34)
Jan  3 23:49:13 tux kernel: [ 1224.020871] RTW: Unknown Broadcom information element ignored (type=4 len=5)
Jan  3 23:49:13 tux kernel: [ 1224.020873] RTW: unknown vendor specific information element ignored (vendor OUI 00:26:86 len=6)
Jan  3 23:49:13 tux kernel: [ 1224.020875] RTW: IEEE 802.11 element parse ignored unknown element (id=127 elen=8)
Jan  3 23:49:13 tux kernel: [ 1224.020876] RTW: unknown vendor specific information element ignored (vendor OUI 50:6f:9a len=7)
Jan  3 23:49:13 tux kernel: [ 1224.020878] RTW: IEEE 802.11 element parse ignored unknown element (id=108 elen=2)
Jan  3 23:49:13 tux kernel: [ 1224.020879] RTW: IEEE 802.11 element parse ignored unknown element (id=107 elen=7)
Jan  3 23:49:13 tux kernel: [ 1224.225718] RTW: IEEE 802.11 element parse ignore

I hope, somebody can help me.

Best regards Kay

RinCat commented 3 years ago

Not enough logs, unknown element are expected.

MahouShoujoMivutilde commented 3 years ago

Do you use networkmanager with wpa_supplicant?

Had similar experience with comfast cf 913ac v2 today.

Switching to iwd (as suggested here) helped.

guckuck commented 3 years ago

Do you use networkmanager with wpa_supplicant?

Had similar experience with comfast cf 913ac v2 today.

Switching to iwd (as suggested here) helped.

Thanks, I will test that. Sadly there is no package for Ubuntu 18.4 (32 bit), so I have to compile it for myself.

guckuck commented 3 years ago

Not enough logs, unknown element are expected.

This log shows the first try to connect to my wifi ("Funkloch"). After that fails, it connect automatically with the T-Online FON-Hotspot (without key).


Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1379] device (wlx984827a71691): Activation: (wifi) access point 'Funkloch 6' has security, but secrets are required.
Jan  9 16:17:54 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-DISCONNECTED bssid=e6:08:4f:8f:53:63 reason=3 locally_generated=1
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1380] device (wlx984827a71691): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan  9 16:17:54 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan  9 16:17:54 tux NetworkManager[752]: <warn>  [1610205474.1431] sup-iface[0x1d92508,wlx984827a71691]: connection disconnected (reason -3)
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1432] device (wlx984827a71691): supplicant interface state: completed -> disconnected
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1590] device (wlx984827a71691): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1600] device (wlx984827a71691): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1718] device (wlx984827a71691): Activation: (wifi) connection 'Funkloch 6' has security, and secrets exist.  No new secrets needed.
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1718] Config: added 'ssid' value 'Funkloch'
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1719] Config: added 'scan_ssid' value '1'
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1719] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1719] Config: added 'key_mgmt' value 'WPA-PSK'
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1719] Config: added 'psk' value '<hidden>'
Jan  9 16:17:54 tux wpa_supplicant[751]: wlx984827a71691: Trying to associate with f8:08:4f:8f:53:63 (SSID='Funkloch' freq=5180 MHz)
Jan  9 16:17:54 tux kernel: [ 2554.745053] RTW: rtw_set_802_11_connect(wlx984827a71691)  fw_state=0x00000008
Jan  9 16:17:54 tux NetworkManager[752]: <info>  [1610205474.1890] device (wlx984827a71691): supplicant interface state: disconnected -> associating
Jan  9 16:17:57 tux nautilus[1681]: Attempting to read the recently used resources file at '/home/papa/.local/share/recently-used.xbel', but the parser failed: Datei »/home/papa/.local/share/recently-used.xbel« konnte nicht geöffnet werden: Keine Berechtigung.
Jan  9 16:17:57 tux gedit[2979]: Attempting to read the recently used resources file at '/home/papa/.local/share/recently-used.xbel', but the parser failed: Datei »/home/papa/.local/share/recently-used.xbel« konnte nicht geöffnet werden: Keine Berechtigung.
Jan  9 16:18:00 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-ASSOC-REJECT status_code=1
Jan  9 16:18:00 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan  9 16:18:00 tux NetworkManager[752]: <info>  [1610205480.4603] device (wlx984827a71691): supplicant interface state: associating -> disconnected
Jan  9 16:18:00 tux NetworkManager[752]: <warn>  [1610205480.4603] sup-iface[0x1d92508,wlx984827a71691]: connection disconnected (reason 1)
Jan  9 16:18:00 tux kernel: [ 2561.020027] RTW: WARN _beamforming_leave: f8:08:4f:8f:53:63 is neither beamforming ee or er!!
Jan  9 16:18:00 tux NetworkManager[752]: <info>  [1610205480.5648] device (wlx984827a71691): supplicant interface state: disconnected -> scanning
Jan  9 16:18:01 tux wpa_supplicant[751]: wlx984827a71691: Trying to associate with f8:08:4f:8f:53:64 (SSID='Funkloch' freq=2462 MHz)
Jan  9 16:18:01 tux kernel: [ 2561.788170] RTW: rtw_set_802_11_connect(wlx984827a71691)  fw_state=0x00000008
Jan  9 16:18:01 tux NetworkManager[752]: <info>  [1610205481.2365] device (wlx984827a71691): supplicant interface state: scanning -> associating
Jan  9 16:18:07 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-ASSOC-REJECT status_code=1
Jan  9 16:18:07 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan  9 16:18:07 tux NetworkManager[752]: <info>  [1610205487.3683] device (wlx984827a71691): supplicant interface state: associating -> disconnected
Jan  9 16:18:07 tux NetworkManager[752]: <warn>  [1610205487.3683] sup-iface[0x1d92508,wlx984827a71691]: connection disconnected (reason 1)
Jan  9 16:18:07 tux kernel: [ 2567.928166] RTW: WARN _beamforming_leave: f8:08:4f:8f:53:64 is neither beamforming ee or er!!
Jan  9 16:18:07 tux NetworkManager[752]: <info>  [1610205487.4728] device (wlx984827a71691): supplicant interface state: disconnected -> scanning
Jan  9 16:18:11 tux wpa_supplicant[751]: wlx984827a71691: Trying to associate with f8:08:4f:8f:53:63 (SSID='Funkloch' freq=5180 MHz)
Jan  9 16:18:11 tux kernel: [ 2572.212532] RTW: rtw_set_802_11_connect(wlx984827a71691)  fw_state=0x00000008
Jan  9 16:18:11 tux NetworkManager[752]: <info>  [1610205491.6578] device (wlx984827a71691): supplicant interface state: scanning -> associating
Jan  9 16:18:17 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-ASSOC-REJECT status_code=1
Jan  9 16:18:17 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan  9 16:18:17 tux NetworkManager[752]: <info>  [1610205497.8648] device (wlx984827a71691): supplicant interface state: associating -> disconnected
Jan  9 16:18:17 tux NetworkManager[752]: <warn>  [1610205497.8649] sup-iface[0x1d92508,wlx984827a71691]: connection disconnected (reason 1)
Jan  9 16:18:17 tux kernel: [ 2578.424382] RTW: WARN _beamforming_leave: f8:08:4f:8f:53:63 is neither beamforming ee or er!!
Jan  9 16:18:18 tux NetworkManager[752]: <info>  [1610205498.8699] device (wlx984827a71691): supplicant interface state: disconnected -> scanning
Jan  9 16:18:19 tux NetworkManager[752]: <warn>  [1610205499.4638] device (wlx984827a71691): Activation: (wifi) association took too long
Jan  9 16:18:19 tux NetworkManager[752]: <info>  [1610205499.4639] device (wlx984827a71691): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan  9 16:18:19 tux NetworkManager[752]: <warn>  [1610205499.4654] device (wlx984827a71691): Activation: (wifi) asking for new secrets
Jan  9 16:18:19 tux NetworkManager[752]: <info>  [1610205499.5491] device (wlx984827a71691): supplicant interface state: scanning -> inactive
Jan  9 16:18:19 tux kernel: [ 2580.117057] RTW: nolinked power save enter
Jan  9 16:18:26 tux kernel: [ 2587.364336] IPv6: ADDRCONF(NETDEV_UP): wlx984827a71691: link is not ready
Jan  9 16:18:26 tux NetworkManager[752]: <warn>  [1610205506.8008] device (wlx984827a71691): User canceled the secrets request.
Jan  9 16:18:26 tux NetworkManager[752]: <info>  [1610205506.8009] device (wlx984827a71691): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Jan  9 16:18:26 tux NetworkManager[752]: <info>  [1610205506.8011] manager: NetworkManager state is now DISCONNECTED
Jan  9 16:18:26 tux NetworkManager[752]: <warn>  [1610205506.8015] device (wlx984827a71691): Activation: failed for connection 'Funkloch 6'
Jan  9 16:18:26 tux NetworkManager[752]: <info>  [1610205506.8020] device (wlx984827a71691): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan  9 16:18:26 tux kernel: [ 2587.391305] RTW: [HALMAC][ALWAYS]shall R reg twice!!
Jan  9 16:18:26 tux gnome-shell[1355]: An active wireless connection, in infrastructure mode, involves no access point?
Jan  9 16:18:27 tux kernel: [ 2588.376183] RTW: txpath=0x3, rxpath=0x3
Jan  9 16:18:27 tux kernel: [ 2588.376186] RTW: txpath_1ss:0x1, num:1
Jan  9 16:18:27 tux kernel: [ 2588.376187] RTW: txpath_2ss:0x3, num:2
Jan  9 16:18:27 tux kernel: [ 2588.423685] start_addr=(0x20000), end_addr=(0x40000), buffer_size=(0x20000), smp_number_max=(16384)
Jan  9 16:18:27 tux kernel: [ 2588.432434] RTW: wlx984827a71691- hw port(0) mac_addr =98:48:27:a7:16:91
Jan  9 16:18:27 tux kernel: [ 2588.457812] RTW: nolinked power save leave
Jan  9 16:18:31 tux nautilus[1681]: Attempting to read the recently used resources file at '/home/papa/.local/share/recently-used.xbel', but the parser failed: Datei »/home/papa/.local/share/recently-used.xbel« konnte nicht geöffnet werden: Keine Berechtigung.
Jan  9 16:18:31 tux gedit[2979]: Attempting to read the recently used resources file at '/home/papa/.local/share/recently-used.xbel', but the parser failed: Datei »/home/papa/.local/share/recently-used.xbel« konnte nicht geöffnet werden: Keine Berechtigung.
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.0895] policy: auto-activating connection 'Telekom_FON 1'
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.0920] device (wlx984827a71691): Activation: starting connection 'Telekom_FON 1' (650f36a2-1ac1-4c07-abcb-36d887175c66)
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.0925] device (wlx984827a71691): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.0928] manager: NetworkManager state is now CONNECTING
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.0997] device (wlx984827a71691): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.1016] device (wlx984827a71691): Activation: (wifi) connection 'Telekom_FON 1' requires no security.  No secrets needed.
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.1019] Config: added 'ssid' value 'Telekom_FON'
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.1020] Config: added 'scan_ssid' value '1'
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.1022] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan  9 16:18:32 tux NetworkManager[752]: <info>  [1610205512.1024] Config: added 'key_mgmt' value 'NONE'
Jan  9 16:18:32 tux kernel: [ 2592.664532] RTW: nolinked power save enter
Jan  9 16:18:32 tux wpa_supplicant[751]: wlx984827a71691: Trying to associate with e6:08:4f:8f:53:63 (SSID='Telekom_FON' freq=5180 MHz)
Jan  9 16:18:32 tux kernel: [ 2592.717684] RTW: [HALMAC][ALWAYS]shall R reg twice!!
Jan  9 16:18:33 tux kernel: [ 2593.700436] RTW: txpath=0x3, rxpath=0x3
Jan  9 16:18:33 tux kernel: [ 2593.700438] RTW: txpath_1ss:0x1, num:1
Jan  9 16:18:33 tux kernel: [ 2593.700440] RTW: txpath_2ss:0x3, num:2
Jan  9 16:18:33 tux kernel: [ 2593.747186] start_addr=(0x20000), end_addr=(0x40000), buffer_size=(0x20000), smp_number_max=(16384)
Jan  9 16:18:33 tux kernel: [ 2593.755684] RTW: wlx984827a71691- hw port(0) mac_addr =98:48:27:a7:16:91
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.2215] device (wlx984827a71691): supplicant interface state: inactive -> associating
Jan  9 16:18:33 tux kernel: [ 2593.782812] RTW: nolinked power save leave
Jan  9 16:18:33 tux kernel: [ 2593.782829] RTW: rtw_set_802_11_connect(wlx984827a71691)  fw_state=0x00000008
Jan  9 16:18:33 tux kernel: [ 2594.047099] RTW: start auth
Jan  9 16:18:33 tux kernel: [ 2594.048065] RTW: auth success, start assoc
Jan  9 16:18:33 tux kernel: [ 2594.050733] RTW: assoc success
Jan  9 16:18:33 tux wpa_supplicant[751]: wlx984827a71691: Associated with e6:08:4f:8f:53:63
Jan  9 16:18:33 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-CONNECTED - Connection to e6:08:4f:8f:53:63 completed [id=0 id_str=]
Jan  9 16:18:33 tux wpa_supplicant[751]: bgscan simple: Failed to enable signal strength monitoring
Jan  9 16:18:33 tux wpa_supplicant[751]: wlx984827a71691: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan  9 16:18:33 tux kernel: [ 2594.051530] IPv6: ADDRCONF(NETDEV_CHANGE): wlx984827a71691: link becomes ready
Jan  9 16:18:33 tux kernel: [ 2594.055202] RTW: ============ STA [e6:08:4f:8f:53:63]  ===================
Jan  9 16:18:33 tux kernel: [ 2594.055204] RTW: mac_id : 0
Jan  9 16:18:33 tux kernel: [ 2594.055206] RTW: wireless_mode : 0x44
Jan  9 16:18:33 tux kernel: [ 2594.055207] RTW: mimo_type : 2
Jan  9 16:18:33 tux kernel: [ 2594.055208] RTW: static smps : N
Jan  9 16:18:33 tux kernel: [ 2594.055209] RTW: bw_mode : 80MHz, ra_bw_mode : 80MHz
Jan  9 16:18:33 tux kernel: [ 2594.055210] RTW: rate_id : 9
Jan  9 16:18:33 tux kernel: [ 2594.055212] RTW: rssi : -1 (%), rssi_level : 0
Jan  9 16:18:33 tux kernel: [ 2594.055213] RTW: is_support_sgi : Y, is_vht_enable : Y
Jan  9 16:18:33 tux kernel: [ 2594.055214] RTW: disable_ra : N, disable_pt : N
Jan  9 16:18:33 tux kernel: [ 2594.055216] RTW: is_noisy : N
Jan  9 16:18:33 tux kernel: [ 2594.055217] RTW: txrx_state : 0
Jan  9 16:18:33 tux kernel: [ 2594.055218] RTW: curr_tx_rate : CCK_1M (L)
Jan  9 16:18:33 tux kernel: [ 2594.055219] RTW: curr_tx_bw : 20MHz
Jan  9 16:18:33 tux kernel: [ 2594.055220] RTW: curr_retry_ratio : 0
Jan  9 16:18:33 tux kernel: [ 2594.055222] RTW: ra_mask : 0x00000000fffffff0
Jan  9 16:18:33 tux kernel: [ 2594.055222] 
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.4966] device (wlx984827a71691): supplicant interface state: associating -> completed
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.4967] device (wlx984827a71691): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Telekom_FON'.
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.4985] device (wlx984827a71691): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.4989] dhcp4 (wlx984827a71691): activation: beginning transaction (timeout in 45 seconds)
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5058] dhcp4 (wlx984827a71691): dhclient started with pid 9604
Jan  9 16:18:33 tux dhclient[9604]: DHCPREQUEST of 172.17.2.101 on wlx984827a71691 to 255.255.255.255 port 67 (xid=0x2e263d23)
Jan  9 16:18:33 tux dhclient[9604]: DHCPACK of 172.17.2.101 from 172.17.2.1
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5483] dhcp4 (wlx984827a71691):   address 172.17.2.101
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5483] dhcp4 (wlx984827a71691):   plen 32 (255.255.255.255)
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5484] dhcp (wlx984827a71691):   static route 172.17.2.1/32 via 172.17.2.101 metric 600 mss 0 rt-src dhcp
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5484] dhcp4 (wlx984827a71691):   gateway 172.17.2.1
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5484] dhcp4 (wlx984827a71691):   lease time 600
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5484] dhcp4 (wlx984827a71691):   nameserver '172.17.2.100'
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5484] dhcp4 (wlx984827a71691):   nameserver '172.17.2.200'
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5485] dhcp4 (wlx984827a71691):   domain name 'rtc.fon.local'
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5485] dhcp4 (wlx984827a71691): state changed unknown -> bound
Jan  9 16:18:33 tux avahi-daemon[748]: Joining mDNS multicast group on interface wlx984827a71691.IPv4 with address 172.17.2.101.
Jan  9 16:18:33 tux avahi-daemon[748]: New relevant interface wlx984827a71691.IPv4 for mDNS.
Jan  9 16:18:33 tux avahi-daemon[748]: Registering new address record for 172.17.2.101 on wlx984827a71691.IPv4.
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5548] device (wlx984827a71691): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan  9 16:18:33 tux whoopsie[1012]: [16:18:33] Cannot reach: https://daisy.ubuntu.com
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5566] device (wlx984827a71691): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5570] device (wlx984827a71691): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.5572] manager: NetworkManager state is now CONNECTED_LOCAL
Jan  9 16:18:33 tux dhclient[9604]: bound to 172.17.2.101 -- renewal in 290 seconds.
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.6049] manager: NetworkManager state is now CONNECTED_SITE
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.6050] policy: set 'Telekom_FON 1' (wlx984827a71691) as default for IPv4 routing and DNS
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.6078] device (wlx984827a71691): Activation: successful, device activated.
Jan  9 16:18:33 tux systemd[1]: Starting resolvconf-pull-resolved.service...
Jan  9 16:18:33 tux dbus-daemon[700]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.21' (uid=0 pid=752 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan  9 16:18:33 tux gsd-sharing[1474]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.
Jan  9 16:18:33 tux gsd-sharing[1474]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Jan  9 16:18:33 tux gsd-sharing[1474]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
Jan  9 16:18:33 tux systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan  9 16:18:33 tux systemd[1]: Started resolvconf-pull-resolved.service.
Jan  9 16:18:33 tux dbus-daemon[700]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan  9 16:18:33 tux systemd[1]: Started Network Manager Script Dispatcher Service.
Jan  9 16:18:33 tux nm-dispatcher: req:1 'up' [wlx984827a71691]: new request (1 scripts)
Jan  9 16:18:33 tux nm-dispatcher: req:1 'up' [wlx984827a71691]: start running ordered scripts...
Jan  9 16:18:33 tux systemd-resolved[679]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jan  9 16:18:33 tux systemd[1]: Reloading OpenBSD Secure Shell server.
Jan  9 16:18:33 tux systemd[1]: Reloaded OpenBSD Secure Shell server.
Jan  9 16:18:33 tux systemd-resolved[679]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jan  9 16:18:33 tux NetworkManager[752]: <info>  [1610205513.9579] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan  9 16:18:33 tux whoopsie[1012]: [16:18:33] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/11
Jan  9 16:18:33 tux whoopsie[1012]: [16:18:33] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/11
Jan  9 16:18:33 tux whoopsie[1012]: [16:18:33] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/11
Jan  9 16:18:33 tux nm-dispatcher: req:2 'connectivity-change': new request (1 scripts)
Jan  9 16:18:33 tux systemd[1]: Reloading OpenBSD Secure Shell server.
Jan  9 16:18:33 tux nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Jan  9 16:18:33 tux systemd[1]: Reloaded OpenBSD Secure Shell server.
Jan  9 16:18:34 tux avahi-daemon[748]: Joining mDNS multicast group on interface wlx984827a71691.IPv6 with address fe80::dadb:3b74:829e:88f9.
Jan  9 16:18:34 tux avahi-daemon[748]: New relevant interface wlx984827a71691.IPv6 for mDNS.
Jan  9 16:18:34 tux avahi-daemon[748]: Registering new address record for fe80::dadb:3b74:829e:88f9 on wlx984827a71691.*.
Jan  9 16:18:36 tux whoopsie[1012]: [16:18:36] online```
RinCat commented 3 years ago

Try set echo 5 > /proc/net/rtl88x2bu/log_level and check logs. You may wanna try iwd as mentioned.

guckuck commented 3 years ago

So, I updated my system to Ubuntu 20.10 (64 bit). I had no luck with iwd. Same problem. Cannot connect to my wifi. The fon-hotsport (Telekom_FON) also won't work because no captive portal is shown. But I can connect to this wifi.

Maybe important: I use the same SSID for the 2,4 und 5 GHz network.

I created a new log.

log.txt

RinCat commented 3 years ago

What's your WiFi model and configuration? The driver think the WiFi beacon frame is invalid.

guckuck commented 3 years ago

My router is a Speedport Pro Plus (very new model). As attachment my configuration. I hope, you understand it. It is in german. Do you need more information?

Bildschirmfoto 2021-01-10 um 08 15 31 Bildschirmfoto 2021-01-10 um 08 16 50

RinCat commented 3 years ago

Maybe try change both to 802.11n/ac , the router send beacons said the size is 80, but size only 26. It could be bug in the router.

guckuck commented 3 years ago

I can not change the 2,4 GHz-Network to n/ac. I have the following options: b/g/n; g/n; b/g

I will now test some other options. Maybe I get correct beacons.

guckuck commented 3 years ago

I had no luck. I will buy another wifi-stick for this computer. Thanks for your support and your work.