#1109: MadWifi trunk/0.9.2 ad-hoc network invisible to Windows
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: madwifi: other | Version: trunk
Resolution: | Keywords: ad-hoc windows
Patch_attached: 0 |
-------------------------------------+--------------------------------------
Comment (by anonymous):
In fact, I thought I have found the reason why these cards failure in Ad-
hoc mode. Madwifi, iwl didn't transmit the beacons every 100ms. If you
adapted a zd1211rw, you could see the beacons, but these madwifi, iwl
didn't. In IEEE80211, if a node/cell didn't broadcast beacons for a time
for example 1 minute, it would be looked as power off or out of the
wireless range. All of you could found the same result if you adapted a
zd1211rw/madwifi/iwl, switch the wireless mode to monitor mode and capture
the wireless packages(Note: NOT IP package, but 80211 packages) with
wireshark. Again, with the card didn't switch to monitor mode, can only
capture IP packages. Only in monitor mode you could capture beacon
packages.
--
Ticket URL: <http://madwifi.org/ticket/1109#comment:10>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
