Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1283286 > unrolled thread
| Started by | Neil Hellfeldt <hellfeldt@esteem.com> |
|---|---|
| First post | 2015-12-03 20:40 +0100 |
| Last post | 2015-12-03 20:40 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
WDS interface always busy, cannot be brought up Neil Hellfeldt <hellfeldt@esteem.com> - 2015-12-03 20:40 +0100
| From | Neil Hellfeldt <hellfeldt@esteem.com> |
|---|---|
| Date | 2015-12-03 20:40 +0100 |
| Subject | WDS interface always busy, cannot be brought up |
| Message-ID | <qBHTr-TI-3@gated-at.bofh.it> |
commit 65a124dd719d6e90591e4756bb04e1719489705e prevents WDS interface
type from bring brought up.
Simple Test:
before this you must have a AP interface, I used hostapd to create it so
I don't have a single liner to show that.
iw dev wlan0 interface add wlan0wds0 type wds
ip link set dev wlan0wds0 address 00:11:22:33:44:55
iw dev wlan0wds0 set peer 00:66:77:88:99:AA
ifconfig wlan0wds0 up
Konsole output ifconfig: SIOCSIFFLAGS: Device or resource busy
The commit: says it checks for channel availability.
WDS do not use there own channels. They use the channel of the ap
interface that already exists,
because of this cfg80211_check_combinations will always return -EBUSY.
That do to this test statement
if (num == 0)
return -EBUSY;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web