

Depending on the OS, this is either presented as a different API or as a true 802.11 network interface.

What you actually need is an interface that can fetch true 802.11 frames. And remember that receiving frames for other stations is unreliable, because the AP will retransmit these frames until the other station received it correctly, not until you receive it correctly. And 802.11 has support for AP that both allow encryption and clear text, so you cannot even enable that feature when connected to a open access point.

More importantly: Even if promiscuous mode on that interface is meant to enable receiving frames for other stations, these frames can not be presented as Ethernet frames: A 802.11 frame has 3 or 4 addresses, can have their payload encrypted and has many other fields that Ethernet does not have. On an switched Ethernet network, turning on promiscuous mode will not allow you to receive Ethernet frames that are not for you (it will merely enable you to see multicast frames that you are not interested in), so the 802.11-as-ethernet interface should do just the same thing. This means that this "promiscuous" flag is only enabled on an Ethernet-like network interface.

You can already guess what you would see when capturing in promiscuous mode on a 802.11 managed interface: you get Ethernet frames that bear little resemblance with the actual 802.11 frames that got transmitted/received. The implication is that, on most OS, a 802.11 station is presented as an Ethernet interface, which carries Ethernet frames.
