Cannot create hotspot when wifi connected on iwlwifi after Linux kernel 6.11
Opened this issue · 4 comments
Describe the bug
Unable to create hotspot when connected to any WIFI, when running with Linux kernel version >= 6.11.0
Also, unable to connect to WIFI when hotspot on, when running with Linux kernel version >= 6.11.0
There is no such problem on Linux kernel 6.10
To Reproduce
Steps to reproduce the behavior:
- Connect to any WIFI on a OS with kernel version >= 6.11.0
- Run
linux-wifi-hotspot - Click on 'Create hotspot'
- Fail to create hotspot and show
Not running
Expected behavior
Hotspot enabled, which is that case when kernel version <= 6.10
Screenshots
Desktop (please complete the following information):
- OS: Debian
- Version: 12
- Card: ax200
Additional context
I have done bisect off kernel to find out some hints.
Between 6.10 and 6.11, such commit breaks all WIFI:
commit 5c38bedac16a946402b627621b3d4bfcc9952479
Author: Johannes Berg <johannes.berg@intel.com>
Date: Tue Jun 18 20:03:02 2024 +0300
wifi: iwlwifi: mvm: unify and fix interface combinations
AP interfaces fundamentally cannot leave the channel, so multi-
channel operation with them isn't really possible. We shouldn't
advertise support for such, at least not as long as we don't
have full multi-radio support. Thus, remove the AP bit from the
interface combinations for two channels and add another set for
just one channel that has it.
Also, to avoid duplicating everything even more, unify the NAN
and non-NAN cases.
And such commit fixs WIFI. However, after that, hotspot is not fixed.
commit 4278d88fedcfde1b91a5cfa96acb0e06d7742e12 (HEAD)
Author: Johannes Berg <johannes.berg@intel.com>
Date: Tue Jul 2 13:00:00 2024 +0200
wifi: iwlwifi: mvm: fix interface combinations
The NAN code referenced in this commit isn't actually
present in the driver (any more), and the commit didn't
add the extra NAN entry. Thus, the -1 is incorrect.
It seems that Intel bans multi-channel off iwlwifi so that hotspot broken.
@CicadaSeventeen has a regression bug report been made on the linux kernel side yet?
@CicadaSeventeen has a regression bug report been made on the linux kernel side yet?
Kernel people refused to fix it.
see :
What is their rationale behind not fixing this? I read the link you gave but me being new to linux just dont understand this.
This feature is just too important for my usecase.