Thank you for your answer. I´ll put it in two different cases:
1) with the ath9k driver with comes with compat wireless 2.6.39-1:
Yes, like you said that ´s the message i get from dmesg when i try
to create the ad-hoc interface after another interface is up. However if
i first create the ad-hoc interface then i can bring up the original
wlan0 and run hostapd on it. But when i try to create an IBSS with "ibss
join" i get "device or resource bussy". I don´t know why the order of
interface creation/bringing up is important in this case.
2) with older ath9k versions, for example compat wireless 2.6.32-16:
In this case i can run hostapd in wlan0 and then create and bring
up an ad-hoc interface without problems, furthermore i can join to an
ibss with "iw ibss join" and all works fine.
The main doubt i have is why the case 2) is not supported anymore, if is
something wrong about it. Thank you again.
El 22/07/2011 02:03 a.m., Mohammed Shafi escribió:
> On Fri, Jul 22, 2011 at 1:15 AM, Gabriel Tolón<gto...@inti.gob.ar> wrote:
>> Hi
>>
>> I´ve been using an Atheros 9285 chipset in a 2.6.32-32 kernel with ath9k
>> and two virtual interfaces, one in ad-hoc mode and the other in master
>> mode using hostapd. That configuration worked fine, with some computers
>> connected to the Acces Point and others to the IBSS running in the
>> ad-hoc interface. The only problem was that when bringing up the IBSS
>> (using iw) the interface using hostapd stopped sending beacons, but as
>> far as i understood all kept working thanks to the probe requests and
>> responses.
>>
>> Then i upgraded the ath9k driver using compat wireless-2.6.32.16 and all
>> worked like before. But when i used the ath9k driver of compat
>> wireless-2.6.39-1 i couldn ´t bring the IBSS up when the hostapd was
>> running (i could bring the ad hoc interface up, but not the IBSS with
>> "iw ibss join"). I´d like to know if this configuration is not supported
>> or will not be supported anymore, and if it could be possible to have
>> the AP beaconing together with an IBSS. Thank you!
> you would have got ?
> [ 2841.528600] ath: Cannot create ADHOC interface when other
> interfaces already exist.
>
> because of this check in main.c
>
> if ((ah->opmode == NL80211_IFTYPE_ADHOC) ||
> ((vif->type == NL80211_IFTYPE_ADHOC)&&
> sc->nvifs> 0)) {
> ath_err(common, "Cannot create ADHOC interface when other"
> " interfaces already exist.\n");
> ret = -EINVAL;
> goto out;
> }
>
>
>
>
>>
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel@lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
