Oops, i failed to mention that i had only tested it on Linux. Your page seems to refer to a windows product, which appears to be not necessary under linux.
I'm not sure "promiscuous mode" has a meaning on WiFi network: the (almost) equivalent of this is in the WiFi world is the monitor mode. The monitor mode causes your card to capture all packet on the selected WiFi channel.
Additionnally, when not in monitor mode, your network interface will act as an Ethernet interface (the network card driver will rewrite the 802.11 packets to Ethernet packets before passing them up to the protocols stack). Because of this, any sniffer will see normal Ethernet packets. However, in monitor mode, your driver will pass raw 802.11 packets, which you will be able to sniff.
However, i've no clue about how to enable monitor mode under Windows. I've got it to work under Linux with Orinoco, Prism2-based, and Atheros-based cards.
Hum, as long as your wireless card is in monitor mode (http://en.wikipedia.org/wiki/Monitor_mode , this mode is controlled by the OS, so ethereal doesn't even know about it), ethereal can read and analyze with 802.11 packets just fine.
Furthermore, it's not even limited to "regular" data packets (IP or ARP packets encapsulated into 802.11 ) . You can see things like 802.11 association/authentication/probes packets (it's funny how some people believe that preventing the AP from announcing its network name (ESSID) adds security, as the ESSID is transmitted in the association / probes packets)
I think a "wake-up message" system is not that hard to do.
One can filter a port with iptables/ipfw/whatever (with a rule that sends back RST, so the port appears closed), and then, put a little daemon that uses libpcap to passively sniff the network (like tcpdump).
The daemon can wait for the magic packet, and then add a firewall rule to allow the authorized client to connect to the port...The magic packet can be any IP packet, doesn't has to be a TCP packet to the same port, doesn't even has to be a TCP packet..
Slashdot Mirror
Oops, i failed to mention that i had only tested it on Linux. Your page seems to refer to a windows product, which appears to be not necessary under linux.
I'm not sure "promiscuous mode" has a meaning on WiFi network: the (almost) equivalent of this is in the WiFi world is the monitor mode. The monitor mode causes your card to capture all packet on the selected WiFi channel.
Additionnally, when not in monitor mode, your network interface will act as an Ethernet interface (the network card driver will rewrite the 802.11 packets to Ethernet packets before passing them up to the protocols stack). Because of this, any sniffer will see normal Ethernet packets. However, in monitor mode, your driver will pass raw 802.11 packets, which you will be able to sniff.
However, i've no clue about how to enable monitor mode under Windows. I've got it to work under Linux with Orinoco, Prism2-based, and Atheros-based cards.
Hum, as long as your wireless card is in monitor mode (http://en.wikipedia.org/wiki/Monitor_mode , this mode is controlled by the OS, so ethereal doesn't even know about it), ethereal can read and analyze with 802.11 packets just fine.
Furthermore, it's not even limited to "regular" data packets (IP or ARP packets encapsulated into 802.11 ) . You can see things like 802.11 association/authentication/probes packets (it's funny how some people believe that preventing the AP from announcing its network name (ESSID) adds security, as the ESSID is transmitted in the association / probes packets)
I think a "wake-up message" system is not that hard to do.
One can filter a port with iptables/ipfw/whatever (with a rule that sends back RST, so the port appears closed), and then, put a little daemon that uses libpcap to passively sniff the network (like tcpdump).
The daemon can wait for the magic packet, and then add a firewall rule to allow the authorized client to connect to the port...The magic packet can be any IP packet, doesn't has to be a TCP packet to the same port, doesn't even has to be a TCP packet..