59bbb6f757
Currently, there's a problem that affects regulatory enforcement and connection stability, in that it is possible to switch the channel while connected to a network or joined to an IBSS. The problem comes from the fact that we only validate the channel against the current interface's type, not against any other interface. Thus, you have any type of interface up, additionally bring up a monitor mode interface and switch the channel on the monitor. This will obviously also switch the channel on the other interface. The problem now is that if you do that while sending beacons for IBSS mode, you can switch to a disabled channel or a channel that doesn't allow beaconing. Combined with a managed mode interface connected to an AP instead of an IBSS interface, you can easily break the connection that way. To fix this, this patch validates any channel change with all available interfaces, and disallows such changes on secondary interfaces if another interface is connected to an AP or joined to an IBSS. Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
14 lines
540 B
Makefile
14 lines
540 B
Makefile
obj-$(CONFIG_WIRELESS_EXT) += wext.o
|
|
obj-$(CONFIG_CFG80211) += cfg80211.o
|
|
obj-$(CONFIG_LIB80211) += lib80211.o
|
|
obj-$(CONFIG_LIB80211_CRYPT_WEP) += lib80211_crypt_wep.o
|
|
obj-$(CONFIG_LIB80211_CRYPT_CCMP) += lib80211_crypt_ccmp.o
|
|
obj-$(CONFIG_LIB80211_CRYPT_TKIP) += lib80211_crypt_tkip.o
|
|
|
|
cfg80211-y += core.o sysfs.o radiotap.o util.o reg.o scan.o nl80211.o
|
|
cfg80211-y += mlme.o ibss.o sme.o chan.o
|
|
cfg80211-$(CONFIG_CFG80211_DEBUGFS) += debugfs.o
|
|
cfg80211-$(CONFIG_WIRELESS_EXT) += wext-compat.o wext-sme.o
|
|
|
|
ccflags-y += -D__CHECK_ENDIAN__
|