[ath9k-devel] multiple virtual ad-hoc interfaces

[ath9k-devel] multiple virtual ad-hoc interfaces

[gtolon at inti.gob.ar]

Hi

We are trying to use 2 virtual interfaces in ad-hoc mode using the iw  
utility and an atheros chipset 9285, but we can?t bring up both them.  
When we try with the second a "device or resource bussy" message  
appears. Thank you in advance.

gtlcm

[ath9k-devel] multiple virtual ad-hoc interfaces

[Pavel Roskin]

On 06/23/2011 03:06 PM, gtolon at inti.gob.ar wrote:
> Hi
>
> We are trying to use 2 virtual interfaces in ad-hoc mode using the iw
> utility and an atheros chipset 9285, but we can?t bring up both them.
> When we try with the second a "device or resource bussy" message
> appears. Thank you in advance.

This limitation is intentional.  The driver doesn't support more than 
one ad-hoc interface.  From drivers/net/wireless/ath/ath9k/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;
}

-- 
Regards,
Pavel Roskin

[ath9k-devel] multiple virtual ad-hoc interfaces

[Adrian Chadd]

Is there a wiki page which describes why, in a way that normal users
can (hopefully) understand?

(I think I understand why, but I shouldn't be allowed anywhere near
user-facing documentation.)



Adrian

On 24 June 2011 05:20, Pavel Roskin <proski@gnu.org> wrote:
> On 06/23/2011 03:06 PM, gtolon at inti.gob.ar wrote:
>> Hi
>>
>> We are trying to use 2 virtual interfaces in ad-hoc mode using the iw
>> utility and an atheros chipset 9285, but we can?t bring up both them.
>> When we try with the second a "device or resource bussy" message
>> appears. Thank you in advance.
>
> This limitation is intentional. ?The driver doesn't support more than
> one ad-hoc interface. ?From drivers/net/wireless/ath/ath9k/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;
> }
>
> --
> Regards,
> Pavel Roskin
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] multiple virtual ad-hoc interfaces

[Mohammed Shafi]

On Fri, Jun 24, 2011 at 5:18 AM, Adrian Chadd <adrian@freebsd.org> wrote:
> Is there a wiki page which describes why, in a way that normal users
> can (hopefully) understand?
>
> (I think I understand why, but I shouldn't be allowed anywhere near
> user-facing documentation.)

Hi Adrian,

I heard that it is because of the TSF problem we can't have any other
interface with an Ad-hoc interface(with inputs from Vasanth).
you have any other thoughts.

>
>
>
> Adrian
>
> On 24 June 2011 05:20, Pavel Roskin <proski@gnu.org> wrote:
>> On 06/23/2011 03:06 PM, gtolon at inti.gob.ar wrote:
>>> Hi
>>>
>>> We are trying to use 2 virtual interfaces in ad-hoc mode using the iw
>>> utility and an atheros chipset 9285, but we can?t bring up both them.
>>> When we try with the second a "device or resource bussy" message
>>> appears. Thank you in advance.
>>
>> This limitation is intentional. ?The driver doesn't support more than
>> one ad-hoc interface. ?From drivers/net/wireless/ath/ath9k/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;
>> }
>>
>> --
>> Regards,
>> Pavel Roskin
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>



-- 
shafi

[ath9k-devel] multiple virtual ad-hoc interfaces

[Adrian Chadd]

On 24 June 2011 13:18, Mohammed Shafi <shafi.wireless@gmail.com> wrote:

> I heard that it is because of the TSF problem we can't have any other
> interface with an Ad-hoc interface(with inputs from Vasanth).
> you have any other thoughts.

I've not done much digging in this area yet, so I'm not sure whether
you could possibly keep multiple adhoc TSFs in sync.

Felix likely knows better than I.


Adrian

[ath9k-devel] multiple virtual ad-hoc interfaces

[gaston]

> On 06/23/2011 03:06 PM, gtolon at inti.gob.ar wrote:
>> Hi
>>
>> We are trying to use 2 virtual interfaces in ad-hoc mode using the iw
>> utility and an atheros chipset 9285, but we can?t bring up both them.
>> When we try with the second a "device or resource bussy" message
>> appears. Thank you in advance.
>
> This limitation is intentional.  The driver doesn't support more than 
> one ad-hoc interface.  From drivers/net/wireless/ath/ath9k/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;
>
>
> -- 
> Regards,
> Pavel Roskin
>

Hello, i'm having the same issue with multiple ad-hocs interfaces. The
limitation is just for ad-hoc interfaces, or any beaconing interfaces?
Because i need two interfaces, Ad-Hoc and AP Mode simultaneously, is
that possible with this driver?
Thanks in advance,

P?rez, Gast?n Ezequiel

[ath9k-devel] multiple virtual ad-hoc interfaces

[Mohammed Shafi]

On Fri, Jun 24, 2011 at 5:59 PM, gaston <gperez@inti.gob.ar> wrote:
>> On 06/23/2011 03:06 PM, gtolon at inti.gob.ar wrote:
>>> Hi
>>>
>>> We are trying to use 2 virtual interfaces in ad-hoc mode using the iw
>>> utility and an atheros chipset 9285, but we can?t bring up both them.
>>> When we try with the second a "device or resource bussy" message
>>> appears. Thank you in advance.
>>
>> This limitation is intentional. ?The driver doesn't support more than
>> one ad-hoc interface. ?From drivers/net/wireless/ath/ath9k/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;
>>
>>
>> --
>> Regards,
>> Pavel Roskin
>>
>
> Hello, i'm having the same issue with multiple ad-hocs interfaces. The
> limitation is just for ad-hoc interfaces, or any beaconing interfaces?
> Because i need two interfaces, Ad-Hoc and AP Mode simultaneously, is
> that possible with this driver?
> Thanks in advance,

*if you have one interface as ad-hoc you cannot have other interface.
limitation of the drive due to TSF.
*mac80211 restricts you cannot more than 1 ad-hoc interface.

I really don't know much about the details why is it like that... need
to look at the code :)

>
> P?rez, Gast?n Ezequiel
>
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>



-- 
shafi

[ath9k-devel] multiple virtual ad-hoc interfaces

[gtolon at inti.gob.ar]

Finally we used hostapd to set an AP in wlan1, and created a virtual  
interface in ad-hoc mode using iw. When tryed to bring up the ad-hoc  
after the AP a "invalid argument" error appeared, but bringing the AP  
down, then the ad-hoc up and the AP up again it seemed to work OK.  
We?ll keep testing this configuration. Thank you very much for your  
answers.

Mohammed Shafi <shafi.wireless@gmail.com> ha escrito:

> On Fri, Jun 24, 2011 at 5:59 PM, gaston <gperez@inti.gob.ar> wrote:
>>> On 06/23/2011 03:06 PM, gtolon at inti.gob.ar wrote:
>>>> Hi
>>>>
>>>> We are trying to use 2 virtual interfaces in ad-hoc mode using the iw
>>>> utility and an atheros chipset 9285, but we can?t bring up both them.
>>>> When we try with the second a "device or resource bussy" message
>>>> appears. Thank you in advance.
>>>
>>> This limitation is intentional. ?The driver doesn't support more than
>>> one ad-hoc interface. ?From drivers/net/wireless/ath/ath9k/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;
>>>
>>>
>>> --
>>> Regards,
>>> Pavel Roskin
>>>
>>
>> Hello, i'm having the same issue with multiple ad-hocs interfaces. The
>> limitation is just for ad-hoc interfaces, or any beaconing interfaces?
>> Because i need two interfaces, Ad-Hoc and AP Mode simultaneously, is
>> that possible with this driver?
>> Thanks in advance,
>
> *if you have one interface as ad-hoc you cannot have other interface.
> limitation of the drive due to TSF.
> *mac80211 restricts you cannot more than 1 ad-hoc interface.
>
> I really don't know much about the details why is it like that... need
> to look at the code :)
>
>>
>> P?rez, Gast?n Ezequiel
>>
>>
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>
>
> --
> shafi
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>