All of lore.kernel.org
 help / color / mirror / Atom feed
* [ath9k-devel] How to block a concrete channel?
@ 2013-04-22 19:11 ` Francisco Cuesta
  0 siblings, 0 replies; 6+ messages in thread
From: Francisco Cuesta @ 2013-04-22 19:11 UTC (permalink / raw)
  To: ath9k-devel

Hello,

I'm working with ath9k driver, and I would like to know how to block
completely a channel/frequency, for instance if the hardware allows to
tune of Channel 14, and I want to completeley block it to.

I do know that on the crda database you can set up some flags like
CHAN_PASSIVE_SCAN or CHAN_RADAR, in order to allow just some
behaviours on that channel, as well as, you can leave out the
frequency of such database in which this channel appears so that
channel would be disabled. But for instance, I have found the state
IEEE80211_CHAN_DISABLED, so how could I proccee in case I wanted to
block the channel 14? Should I set this flag on the band of that
channel? ( This will lead to forbid completely such band right?)

What is more, where are these flags applied? I mean at driver's level,
kernel's level or  nl80211 interface level...

Thank you very much in advance!

regards

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

* How to block a concrete channel?
@ 2013-04-22 19:11 ` Francisco Cuesta
  0 siblings, 0 replies; 6+ messages in thread
From: Francisco Cuesta @ 2013-04-22 19:11 UTC (permalink / raw)
  To: linux-wireless, ath9k-devel

Hello,

I'm working with ath9k driver, and I would like to know how to block
completely a channel/frequency, for instance if the hardware allows to
tune of Channel 14, and I want to completeley block it to.

I do know that on the crda database you can set up some flags like
CHAN_PASSIVE_SCAN or CHAN_RADAR, in order to allow just some
behaviours on that channel, as well as, you can leave out the
frequency of such database in which this channel appears so that
channel would be disabled. But for instance, I have found the state
IEEE80211_CHAN_DISABLED, so how could I proccee in case I wanted to
block the channel 14? Should I set this flag on the band of that
channel? ( This will lead to forbid completely such band right?)

What is more, where are these flags applied? I mean at driver's level,
kernel's level or  nl80211 interface level...

Thank you very much in advance!

regards

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

* [ath9k-devel] How to block a concrete channel?
  2013-04-22 19:11 ` Francisco Cuesta
  (?)
@ 2013-04-23  6:43 ` Matthias May
  2013-04-23  7:08   ` Francisco Cuesta
  -1 siblings, 1 reply; 6+ messages in thread
From: Matthias May @ 2013-04-23  6:43 UTC (permalink / raw)
  To: ath9k-devel

On 22/04/13 21:11, Francisco Cuesta wrote:
> Hello,
>
> I'm working with ath9k driver, and I would like to know how to block
> completely a channel/frequency, for instance if the hardware allows to
> tune of Channel 14, and I want to completeley block it to.
>
> I do know that on the crda database you can set up some flags like
> CHAN_PASSIVE_SCAN or CHAN_RADAR, in order to allow just some
> behaviours on that channel, as well as, you can leave out the
> frequency of such database in which this channel appears so that
> channel would be disabled. But for instance, I have found the state
> IEEE80211_CHAN_DISABLED, so how could I proccee in case I wanted to
> block the channel 14? Should I set this flag on the band of that
> channel? ( This will lead to forbid completely such band right?)
>
> What is more, where are these flags applied? I mean at driver's level,
> kernel's level or  nl80211 interface level...
>
> Thank you very much in advance!
>
> regards
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
You could "disable" the channel by removing it in 
./drivers/net/wireless/ath/ath9k/init.c
Don't forget to adjust the ATH9K_NUM_CHANNELS in 
./drivers/net/wireless/ath/ath9k/hw.h

regards

-- 
Matthias May
Software Engineer

Neratec Solutions AG
Postfach 83, CH-8608 Bubikon, Switzerland
Direct: +41 55 253 2074
Office: +41 55 253 2000
Fax:    +41 55 253 2070
email:  matthias.may at neratec.com
Web:   www.neratec.com

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

* [ath9k-devel] How to block a concrete channel?
  2013-04-23  6:43 ` [ath9k-devel] " Matthias May
@ 2013-04-23  7:08   ` Francisco Cuesta
  2013-04-23  8:29     ` Sujith Manoharan
  0 siblings, 1 reply; 6+ messages in thread
From: Francisco Cuesta @ 2013-04-23  7:08 UTC (permalink / raw)
  To: ath9k-devel

Hi Matthias,  thanks for replying!

Then, is it better to erase the channel from those files instead of
setting a flag?? Could you tell me what implies marking a channel with
IEEE80211_CHAN_DISABLED? I mean, what level would it be disabled at or
what would be consequences of using that flag at level user?

Thanks again,

regards!

2013/4/23 Matthias May <matthias.may@neratec.com>:
> On 22/04/13 21:11, Francisco Cuesta wrote:
>> Hello,
>>
>> I'm working with ath9k driver, and I would like to know how to block
>> completely a channel/frequency, for instance if the hardware allows to
>> tune of Channel 14, and I want to completeley block it to.
>>
>> I do know that on the crda database you can set up some flags like
>> CHAN_PASSIVE_SCAN or CHAN_RADAR, in order to allow just some
>> behaviours on that channel, as well as, you can leave out the
>> frequency of such database in which this channel appears so that
>> channel would be disabled. But for instance, I have found the state
>> IEEE80211_CHAN_DISABLED, so how could I proccee in case I wanted to
>> block the channel 14? Should I set this flag on the band of that
>> channel? ( This will lead to forbid completely such band right?)
>>
>> What is more, where are these flags applied? I mean at driver's level,
>> kernel's level or  nl80211 interface level...
>>
>> Thank you very much in advance!
>>
>> regards
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> You could "disable" the channel by removing it in
> ./drivers/net/wireless/ath/ath9k/init.c
> Don't forget to adjust the ATH9K_NUM_CHANNELS in
> ./drivers/net/wireless/ath/ath9k/hw.h
>
> regards
>
> --
> Matthias May
> Software Engineer
>
> Neratec Solutions AG
> Postfach 83, CH-8608 Bubikon, Switzerland
> Direct: +41 55 253 2074
> Office: +41 55 253 2000
> Fax:    +41 55 253 2070
> email:  matthias.may at neratec.com
> Web:   www.neratec.com
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

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

* [ath9k-devel] How to block a concrete channel?
  2013-04-23  7:08   ` Francisco Cuesta
@ 2013-04-23  8:29     ` Sujith Manoharan
  2013-04-23 11:12       ` Francisco Cuesta
  0 siblings, 1 reply; 6+ messages in thread
From: Sujith Manoharan @ 2013-04-23  8:29 UTC (permalink / raw)
  To: ath9k-devel

Francisco Cuesta wrote:
> Then, is it better to erase the channel from those files instead of
> setting a flag?? Could you tell me what implies marking a channel with
> IEEE80211_CHAN_DISABLED? I mean, what level would it be disabled at or
> what would be consequences of using that flag at level user?

IEEE80211_CHAN_DISABLED is set by the regulatory infrastructure in cfg80211,
based on rules obtained from CRDA. The consequence of setting this flag for
a channel would be that it is no longer available for usage.

For example:

iw list | grep -i "disabled"

* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5640 MHz [128] (disabled)

Sujith

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

* [ath9k-devel] How to block a concrete channel?
  2013-04-23  8:29     ` Sujith Manoharan
@ 2013-04-23 11:12       ` Francisco Cuesta
  0 siblings, 0 replies; 6+ messages in thread
From: Francisco Cuesta @ 2013-04-23 11:12 UTC (permalink / raw)
  To: ath9k-devel

Sujith thanks for replying!

I understand. If you let me  ask another question, so, regarding to
flags,  can you avoid the use of a channel (keep usingh the 14)  as AP
or mesh just setting up a flag for that channel but without disabling
it completely? I mean, that channel will appear on the iw list,
however if you tune it you cannot create an AP.

Thanks again!

regards

2013/4/23 Sujith Manoharan <sujith@msujith.org>:
> Francisco Cuesta wrote:
>> Then, is it better to erase the channel from those files instead of
>> setting a flag?? Could you tell me what implies marking a channel with
>> IEEE80211_CHAN_DISABLED? I mean, what level would it be disabled at or
>> what would be consequences of using that flag at level user?
>
> IEEE80211_CHAN_DISABLED is set by the regulatory infrastructure in cfg80211,
> based on rules obtained from CRDA. The consequence of setting this flag for
> a channel would be that it is no longer available for usage.
>
> For example:
>
> iw list | grep -i "disabled"
>
> * 5600 MHz [120] (disabled)
> * 5620 MHz [124] (disabled)
> * 5640 MHz [128] (disabled)
>
> Sujith

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

end of thread, other threads:[~2013-04-23 11:12 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-22 19:11 [ath9k-devel] How to block a concrete channel? Francisco Cuesta
2013-04-22 19:11 ` Francisco Cuesta
2013-04-23  6:43 ` [ath9k-devel] " Matthias May
2013-04-23  7:08   ` Francisco Cuesta
2013-04-23  8:29     ` Sujith Manoharan
2013-04-23 11:12       ` Francisco Cuesta

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.