| View previous topic :: View next topic |
| Author |
Message |
BastiL
Tux's lil' helper
Joined: 15 Aug 2004
Posts: 111
|
 Posted: Thu Aug 18, 2022 7:07 am Post subject: SOLVED: WLAN no longer working |
 |
|
Hello all,
I realized my WLAN is no longer working. As I had a network cable plugged over the last few days I am not really sure when the problem started and if it is connected to an upgrade of kernel or similar.
To debug, I followed this guide: https://wiki.gentoo.org/wiki/Wifi
"lspci -k" shows the hardware as follows:
| Code: |
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter
Subsystem: Hewlett-Packard Company Realtek RTL8822BE 802.11ac 2 × 2 Wi-Fi + Bluetooth 4.2 Combo Adapter (MU-MIMO supported)
Kernel driver in use: rtw_8822be
Kernel modules: rtw88_8822be
|
Looks fine to me. Required kernel modules and driver are present and used.
I do have the "wlan0" interface as well, as "ifconfig" tells me:
| Code: |
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 4c:eb:bd:c3:a3:c9 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
|
However, neither the Network tool in LXDE nor "wpa_gui" detects any device.... So what is wrong there? What can I do to solve this?
Last edited by BastiL on Fri Aug 19, 2022 6:59 am; edited 1 time in total |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31675
Location: here
|
| Posted: Thu Aug 18, 2022 7:26 am Post subject: |
|
|
tkip use flag is enabled on net-wireless/wpa_supplicant package?
_________________
Questions are guaranteed in life; Answers aren't.
"Those who would give up essential liberty to purchase a little temporary safety,
deserve neither liberty nor safety."
- Ben Franklin
https://www.news.admin.ch/it/nsb?id=103968 |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 3023
|
| Posted: Thu Aug 18, 2022 8:09 am Post subject: |
|
|
Any chance you're using testing 1.38.4 version of network manager? If so, it's has most probably pulled in iwd, which in my opinion is not ready to use. Also it conflicts with wpa_supplicant and you might have forgotten to run depclean, which should have unmerged it after such an update. If you're using udev, that most probably is the case as udev should have renamed wlan0 to something else, but iwd insists on creating and working with its own interfaces.
Another possibility is, as fedeliallalinea mentioned - your wifi network is using tkip and it's disabled by the default for wpa_supplicant, which is the default for some time now.
Regards,
Georgi
Last edited by logrusx on Thu Aug 18, 2022 8:12 am; edited 2 times in total |
|
| Back to top |
|
|
BastiL
Tux's lil' helper
Joined: 15 Aug 2004
Posts: 111
|
| Posted: Thu Aug 18, 2022 8:10 am Post subject: |
|
|
| fedeliallalinea wrote: | | tkip use flag is enabled on net-wireless/wpa_supplicant package? |
No it's not, and I don't think it ever was. This is depreciated since 2009, so why is it needed? |
|
| Back to top |
|
|
BastiL
Tux's lil' helper
Joined: 15 Aug 2004
Posts: 111
|
| Posted: Thu Aug 18, 2022 8:16 am Post subject: |
|
|
| logrusx wrote: | | Any chance you're using testing 1.38.4 version of network manager? If so, it's has most probably pulled in iwd, which in my opinion is not ready to use. Also it conflicts with wpa_supplicant and you might have forgotten to run depclean, which should have unmerged it after such an update. If you're using udev, that most probably is the case as udev should have renamed wlan0 to something else, but iwd insists on creating and working with its own interfaces. |
Yes I am on testing, so I do have 1.38.4 of networkmanager. Also it pulls iwd, as useflag is set. My understanding is you recommend disabling useflag "iwd" of networkmanager-Package for now.
And yes again udev is used on my system.
I will try rebuilding networkmanager with "iwd" useflag disabled. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 3023
|
| Posted: Thu Aug 18, 2022 8:20 am Post subject: |
|
|
| BastiL wrote: | | logrusx wrote: | | Any chance you're using testing 1.38.4 version of network manager? If so, it's has most probably pulled in iwd, which in my opinion is not ready to use. Also it conflicts with wpa_supplicant and you might have forgotten to run depclean, which should have unmerged it after such an update. If you're using udev, that most probably is the case as udev should have renamed wlan0 to something else, but iwd insists on creating and working with its own interfaces. |
Yes I am on testing, so I do have 1.38.4 of networkmanager. Also it pulls iwd, as useflag is set. My understanding is you recommend disabling useflag "iwd" of networkmanager-Package for now.
And yes again udev is used on my system.
I will try rebuilding networkmanager with "iwd" useflag disabled. |
I was still on 1.38.2 until yesterday when another user reported similar issue. I decided to test 1.38.4 with iwd enabled, which will be the new default for NM, but although it worked, I'm not happy with it. It often times does not connect automatically and I have the impression it slows my system down. Instead of testing to see if that impression is true, I decided to spare myself the trouble and see what it will be if I disable iwd and it works as usual.
Regards,
Georgi |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23498
|
| Posted: Thu Aug 18, 2022 1:55 pm Post subject: |
|
|
| BastiL wrote: | | fedeliallalinea wrote: | | tkip use flag is enabled on net-wireless/wpa_supplicant package? |
No it's not, and I don't think it ever was. This is depreciated since 2009, so why is it needed? |
Until earlier this year, wpa_supplicant defaulted to USE=tkip. This caused many users to have a working insecure setup, often based on access points that should have been reconfigured or replaced years ago. We had numerous threads when the default changed to USE=-tkip, and users who relied on an insecure TKIP-based access point lost their network access. Many were advised to fix their network to work without TKIP, but some opted to return to running an insecure TKIP-based setup instead. If you have not been using TKIP, then there is no need for you to change this. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 3023
|
| Posted: Thu Aug 18, 2022 2:09 pm Post subject: |
|
|
| And I would add plenty of ISP's still ship crappy routers that default to TKIP... |
|
| Back to top |
|
|
BastiL
Tux's lil' helper
Joined: 15 Aug 2004
Posts: 111
|
| Posted: Fri Aug 19, 2022 6:59 am Post subject: |
|
|
| logrusx wrote: |
I was still on 1.38.2 until yesterday when another user reported similar issue. I decided to test 1.38.4 with iwd enabled, which will be the new default for NM, but although it worked, I'm not happy with it. It often times does not connect automatically and I have the impression it slows my system down. Instead of testing to see if that impression is true, I decided to spare myself the trouble and see what it will be if I disable iwd and it works as usual.
|
I can confirm that rebuiling network manager 1.38.4 with useflag "iwd" disabled solved the problem for me. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
