All of lore.kernel.org
 help / color / mirror / Atom feed
* [ath9k-devel] multi-vif and multi-wiphy in ath9k
@ 2011-06-17 22:56 ABM Musa
  2011-06-20  5:40 ` Mohammed Shafi
  0 siblings, 1 reply; 4+ messages in thread
From: ABM Musa @ 2011-06-17 22:56 UTC (permalink / raw)
  To: ath9k-devel

Hi,

I am trying to have both mesh and station interface in ath9k with tplink-1043nd. But I am not able to make the both interface up at the same time using ifconfig. It seems that ath9k supports multi-vif and multi-wiphy but I am not getting any good documentation about them. Following link seems to have not much info about vif 
http://wireless.kernel.org/en/users/Documentation/iw/vif

multi-wiphy commands from this post seems to be not working for me.
http://lwn.net/Articles/321690/

Can you please point me to some how-to regarding vif and multi-wiphy and is it possible to have combination of mesh, station and ap at the same time using single radio?

Thanks,
Musa

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] multi-vif and multi-wiphy in ath9k
  2011-06-17 22:56 [ath9k-devel] multi-vif and multi-wiphy in ath9k ABM Musa
@ 2011-06-20  5:40 ` Mohammed Shafi
  2011-06-21 17:05   ` ABM Musa
  0 siblings, 1 reply; 4+ messages in thread
From: Mohammed Shafi @ 2011-06-20  5:40 UTC (permalink / raw)
  To: ath9k-devel

On Sat, Jun 18, 2011 at 4:26 AM, ABM Musa <amusa2@uic.edu> wrote:
> Hi,
>
> I am trying to have both mesh and station interface in ath9k with tplink-1043nd. But I am not able to make the both interface up at the same time using ifconfig. It seems that ath9k supports multi-vif and multi-wiphy but I am not getting any good documentation about them. Following link seems to have not much info about vif
> http://wireless.kernel.org/en/users/Documentation/iw/vif

I am sure you would have change the mac-address for the virtual
interface... please get some debug message ATH_DBG_CONFIG

>
> multi-wiphy commands from this post seems to be not working for me.
> http://lwn.net/Articles/321690/

commit 7545daf498c43e548506212310e6c75382d2731d
Author: Felix Fietkau <nbd@openwrt.org>
Date:   Mon Jan 24 19:23:16 2011 +0100

    ath9k: remove support for virtual wiphys

    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

ommit 34302397e5b980ce561366b63504e9d82948e8b8
Author: Felix Fietkau <nbd@openwrt.org>
Date:   Mon Jan 24 19:23:15 2011 +0100

    ath9k: remove the virtual wiphy debugfs interface

    It does not make much sense to keep the current virtual wiphy implementation
    any longer - it adds significant complexity, has very few users and is still
    very experimental. At some point in time, it will be replaced by a proper
    implementation in mac80211.

    By making the code easier to read and maintain, removing virtual
wiphy support
    helps with fixing the remaining driver issues and adding further
improvements.

    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>


>
> Can you please point me to some how-to regarding vif and multi-wiphy and is it possible to have combination of mesh, station and ap at the same time using single radio?

>
> Thanks,
> Musa
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>



-- 
shafi

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] multi-vif and multi-wiphy in ath9k
  2011-06-20  5:40 ` Mohammed Shafi
@ 2011-06-21 17:05   ` ABM Musa
  2011-06-22 14:48     ` Mohammed Shafi
  0 siblings, 1 reply; 4+ messages in thread
From: ABM Musa @ 2011-06-21 17:05 UTC (permalink / raw)
  To: ath9k-devel

Thanks for your reply. I assigned different mac addresses to mesh and station interface and it works. However, while pinging from both mesh interface and station interface, I found many packet drop in the mesh interface. Is it the default behavior if I try to use two different active interface with a single radio? Also the station gets disassociated after sometime.

-Musa
On Jun 20, 2011, at 12:40 AM, Mohammed Shafi wrote:

> On Sat, Jun 18, 2011 at 4:26 AM, ABM Musa <amusa2@uic.edu> wrote:
>> Hi,
>> 
>> I am trying to have both mesh and station interface in ath9k with tplink-1043nd. But I am not able to make the both interface up at the same time using ifconfig. It seems that ath9k supports multi-vif and multi-wiphy but I am not getting any good documentation about them. Following link seems to have not much info about vif
>> http://wireless.kernel.org/en/users/Documentation/iw/vif
> 
> I am sure you would have change the mac-address for the virtual
> interface... please get some debug message ATH_DBG_CONFIG
> 
>> 
>> multi-wiphy commands from this post seems to be not working for me.
>> http://lwn.net/Articles/321690/
> 
> commit 7545daf498c43e548506212310e6c75382d2731d
> Author: Felix Fietkau <nbd@openwrt.org>
> Date:   Mon Jan 24 19:23:16 2011 +0100
> 
>    ath9k: remove support for virtual wiphys
> 
>    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>    Signed-off-by: John W. Linville <linville@tuxdriver.com>
> 
> ommit 34302397e5b980ce561366b63504e9d82948e8b8
> Author: Felix Fietkau <nbd@openwrt.org>
> Date:   Mon Jan 24 19:23:15 2011 +0100
> 
>    ath9k: remove the virtual wiphy debugfs interface
> 
>    It does not make much sense to keep the current virtual wiphy implementation
>    any longer - it adds significant complexity, has very few users and is still
>    very experimental. At some point in time, it will be replaced by a proper
>    implementation in mac80211.
> 
>    By making the code easier to read and maintain, removing virtual
> wiphy support
>    helps with fixing the remaining driver issues and adding further
> improvements.
> 
>    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>    Signed-off-by: John W. Linville <linville@tuxdriver.com>
> 
> 
>> 
>> Can you please point me to some how-to regarding vif and multi-wiphy and is it possible to have combination of mesh, station and ap at the same time using single radio?
> 
>> 
>> Thanks,
>> Musa
>> 
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>> 
> 
> 
> 
> -- 
> shafi
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] multi-vif and multi-wiphy in ath9k
  2011-06-21 17:05   ` ABM Musa
@ 2011-06-22 14:48     ` Mohammed Shafi
  0 siblings, 0 replies; 4+ messages in thread
From: Mohammed Shafi @ 2011-06-22 14:48 UTC (permalink / raw)
  To: ath9k-devel

On Tue, Jun 21, 2011 at 10:35 PM, ABM Musa <amusa2@uic.edu> wrote:
> Thanks for your reply. I assigned different mac addresses to mesh and station interface and it works. However, while pinging from both mesh interface and station interface, I found many packet drop in the mesh interface. Is it the default behavior if I try to use two different active interface with a single radio? Also the station gets disassociated after sometime.
>

i think we should not do it. in ath9k we cannot have any other
interface when already an Ad-hoc interface is there(I have not gone
into the technical details why it should not). i think the same should
be applicable for mesh too and it may be missing in ath9k ?


> -Musa
> On Jun 20, 2011, at 12:40 AM, Mohammed Shafi wrote:
>
>> On Sat, Jun 18, 2011 at 4:26 AM, ABM Musa <amusa2@uic.edu> wrote:
>>> Hi,
>>>
>>> I am trying to have both mesh and station interface in ath9k with tplink-1043nd. But I am not able to make the both interface up at the same time using ifconfig. It seems that ath9k supports multi-vif and multi-wiphy but I am not getting any good documentation about them. Following link seems to have not much info about vif
>>> http://wireless.kernel.org/en/users/Documentation/iw/vif
>>
>> I am sure you would have change the mac-address for the virtual
>> interface... please get some debug message ATH_DBG_CONFIG
>>
>>>
>>> multi-wiphy commands from this post seems to be not working for me.
>>> http://lwn.net/Articles/321690/
>>
>> commit 7545daf498c43e548506212310e6c75382d2731d
>> Author: Felix Fietkau <nbd@openwrt.org>
>> Date: ? Mon Jan 24 19:23:16 2011 +0100
>>
>> ? ?ath9k: remove support for virtual wiphys
>>
>> ? ?Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>> ? ?Signed-off-by: John W. Linville <linville@tuxdriver.com>
>>
>> ommit 34302397e5b980ce561366b63504e9d82948e8b8
>> Author: Felix Fietkau <nbd@openwrt.org>
>> Date: ? Mon Jan 24 19:23:15 2011 +0100
>>
>> ? ?ath9k: remove the virtual wiphy debugfs interface
>>
>> ? ?It does not make much sense to keep the current virtual wiphy implementation
>> ? ?any longer - it adds significant complexity, has very few users and is still
>> ? ?very experimental. At some point in time, it will be replaced by a proper
>> ? ?implementation in mac80211.
>>
>> ? ?By making the code easier to read and maintain, removing virtual
>> wiphy support
>> ? ?helps with fixing the remaining driver issues and adding further
>> improvements.
>>
>> ? ?Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>> ? ?Signed-off-by: John W. Linville <linville@tuxdriver.com>
>>
>>
>>>
>>> Can you please point me to some how-to regarding vif and multi-wiphy and is it possible to have combination of mesh, station and ap at the same time using single radio?
>>
>>>
>>> Thanks,
>>> Musa
>>>
>>> _______________________________________________
>>> ath9k-devel mailing list
>>> ath9k-devel at lists.ath9k.org
>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>>
>>
>>
>>
>> --
>> shafi
>>
>
>



-- 
shafi

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-06-22 14:48 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-06-17 22:56 [ath9k-devel] multi-vif and multi-wiphy in ath9k ABM Musa
2011-06-20  5:40 ` Mohammed Shafi
2011-06-21 17:05   ` ABM Musa
2011-06-22 14:48     ` Mohammed Shafi

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.