#441: duplicate node list entries in ad-hoc mode
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone: version 0.9.0 - move to
new codebase
Component: madwifi: 802.11 stack | Version: trunk
Resolution: | Keywords: adhoc duplicate node
Patch_attached: 1 |
----------------------------------------+-----------------------------------
Comment (by kiru):
This issue is not just in ad-hoc mode but in Master / sta mode, too.
evidence:
{{{
solymar:~# cat /proc/net/madwifi/ath1/associated_sta
macaddr: <00:02:6f:21:ed:ca>
rssi 7
last_rx 461809.013259
macaddr: <00:02:6f:21:ed:ca>
rssi 5
last_rx 409416.334921
macaddr: <00:02:6f:21:ed:ca>
rssi 5
last_rx 390508.993286
macaddr: <00:02:6f:21:ed:ca>
rssi 10
last_rx 380482.406664
macaddr: <00:02:6f:21:ed:ca>
rssi 11
last_rx 380360.579050
macaddr: <00:02:6f:21:ed:ca>
rssi 9
last_rx 380228.862818
macaddr: <00:02:6f:21:ed:ca>
rssi 21
last_rx 0.008000
solymar:~# iwconfig ath1
ath1 IEEE 802.11a ESSID:"gyerebe"
Mode:Managed Frequency:5.2 GHz Access Point: 00:02:6F:21:ED:CA
Bit Rate:12 Mb/s Tx-Power:17 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=20/94 Signal level=-75 dBm Noise level=-95 dBm
Rx invalid nwid:25 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
solymar:~#
}}}
The other side is a mikrotik in AP mode.
I think it happened, when the driver losts the connection with the other
side.
I've written a [http://www.madiwifi.org/ticket/334 ticket] on an other ad-
hoc problem. Is there any nexus between these tickets?
--
Ticket URL: <http://madwifi.org/ticket/441>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity