#650: monitor mode vap - strange values for access point
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: madwifi: other | Version:
Keywords: | Patch_attached: 0
-----------------------------------+----------------------------------------
When you create a monitor mode VAP, it automatically uses an unusual value
for the AP. This value seems somewhat random. Perhaps madwifi is failing
to initialize some memory?
Example:
{{{
# wlanconfig ath1 create wlandev wifi0 wlanmode monitor
ath1
# ifconfig ath1 up
# iwconfig ath1
ath1 IEEE 802.11g ESSID:""
Mode:Monitor Frequency:2.462 GHz Access Point:
06:12:17:79:1E:6E
Bit Rate:0 kb/s Tx-Power:19 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=19/94 Signal level=-76 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
# wlanconfig ath2 create wlandev wifi0 wlanmode monitor
ath2
# ifconfig ath2 up
# iwconfig ath2
ath2 IEEE 802.11g ESSID:""
Mode:Monitor Frequency:2.462 GHz Access Point:
0A:12:17:79:1E:6E
Bit Rate:0 kb/s Tx-Power:19 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=14/94 Signal level=-81 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
}}}
Note that the Access Point values should be 00:00:00:00:00:00. Also note
that they change slightly with each attempt.
This happens with r1590, with ubuntu linux kernel 2.6.15-23-686 1 SMP
PREEMPT. I do not see this behavior on RHEL 4 with kernel 2.6.9-34.EL 1.
--
Ticket URL: <http://madwifi.org/ticket/650>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
