#2042: ieee80211_unref_node: NULL ieee80211_node *
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: georg
Type: defect | Status: assigned
Priority: minor | Milestone:
Component: madwifi: 802.11 stack | Version: trunk
Resolution: | Keywords: NULL ieee80211_node *
Patch_attached: 1 | Pending: 0
----------------------------------------+-----------------------------------
Comment (by [EMAIL PROTECTED]):
Replying to [comment:10 georg]:
> so, instead of disabling the error output, have you tried the other
patch attached to the ticket?
>
> Could you tell more about your scenario? What mode is the device in? Is
there more than one VAP?
I didn't try the other patch, didn't think it was relevant, because it
only mentioned adhoc mode. I'm always in infrastructure mode or monitor
mode.
There's never more than one VAP, to my knowledge.
Most times, I'm using NetworkManager on Fedora 9 in infrastructure mode as
a client, or I'm using kismet. Using kismet disables NM and tears down
NM's VAP while kismet is running, and it makes another VAP in monitor
mode.
--
Ticket URL: <http://madwifi.org/ticket/2042#comment:11>
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
