#274: ioctl invalid argument
---------------------------------------+------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: other | Version: trunk
Resolution: | Keywords:
Patch_attached: 0 |
---------------------------------------+------------------------------------
Comment (by [EMAIL PROTECTED]):
I had the same problem on my atheros card after I upgraded to revision
1437. The cause of the problem is exactly as svens suggests. An ath0
interface already exists. It's not listed using the ifconfig command, but
the iwconfig command. Once 'wlanconfig ath0 destroy' is called, you can
pull up ath0 with 'wlanconfig ath0 create wlandev wifi0 wlanmode ap' (or
sta).
I think the trouble comes in because ath0 is automatically created. I
don't know when madwifi-ng started doing this. I upgraded from an older
version (I forget which one). I just ran into the same problem once I
upgraded to 1437 and rebooted my machine, as issue, per the instruction
the wlanconfig command.
So the question is: should madwifi-ng automatically create the ath0
interface?
--
Ticket URL: <http://madwifi.org/ticket/274>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
