iw dev twpoxer limit in mBm or not
hi. On ubuntu 18.10 using kernel 4.18.0-10-generic and iw-4.14 on a Broadcom Corp. BCM43142 wifi interface using wl driver, i run sudo iw dev wlp2s0 set txpower limit 21 and iw dev reports back a txpower of 21 dBm But the doc at https://wireless.wiki.kernel.org/en/users/documentation/iw#setting_tx_power and the output of `iw dev help` states that the txpower is to be expressed in mDm not dBm. So I am confused. Can I use suod iw dev wlp2s0 set txpower limit 2100 wihtout frying my card ? Moreover, how is that even possible given that I have set the regdom to FR and that max output power is supposed to be 20dBm in Europe ? Thanks
Re: second wifi card enforce CN reg dom
It's the second time that you (Ben and Steve) are implying that I might break the law. But why are you saying that ? I am not gonna repeat myself again. And for the patch, it is also implied that I am able to write one. 2018-04-12 19:11 GMT+02:00 Ben Greear <gree...@candelatech.com>: > On 04/12/2018 10:05 AM, solsTiCe d'Hiver wrote: >> >> Hi. >> >> I thought I made myself clear. >> I leave in France. My system(s) is/are set up to use FR as default >> regulatory domain. >> >> But when I plug in that tp-link card, I am restricted to use CN >> regulatory domain. Why am I the only one to see this as a problem ? >> >> I know that one can only have one regdom defined on the system. I have >> set it up myself. So why is it changed behind my back by some card or >> whatever ? >> Like I said, I am left with the option, to disable crda, or to use 2 >> systems, one for each card ! >> >> Or may be try Windows when this is not messed up like that ??? Well, >> it's not on Windows that I will be able to use monitor mode, anyway. > > > You can hack the ath9k-htc driver to allow over-riding the regdom > of the NIC, but that requires an out of tree patch and is probably > against the law in your country since the NIC may then not be able to > pass the regulatory requirements. > > Thanks, > Ben > > >> >> Never mind. >> >> 2018-04-12 17:52 GMT+02:00 Dan Williams <d...@redhat.com>: >>> >>> On Thu, 2018-04-12 at 08:18 -0700, Steve deRosier wrote: >>>> >>>> On Thu, Apr 12, 2018 at 3:51 AM, Arend van Spriel >>>> <arend.vanspr...@broadcom.com> wrote: >>>>> >>>>> On 4/12/2018 10:42 AM, solsTiCe d'Hiver wrote: >>>>>> >>>>>> >>>>>> Hi. >>>>>> >>>>>> This is beyond my comprehension that you could assert this is a >>>>>> non issue. >>>>> >>>>> >>>>> >>>>> Well. I am just saying that it is by design. There is no way for >>>>> the >>>>> regulatory code to determine where you and your hardware actually >>>>> reside so >>>>> instead it takes a conservative approach. >>>>> >>>> >>>> To say it another way: mixing regulatory domains on your host system >>>> should result in a _smaller_ set of channels - ie only those channels >>>> at the intersection of the two. >>>> >>>> And another wrinkle to consider - one of the 802.11 amendments (can't >>>> remember which one) actually causes the radio to listen to the >>> >>> >>> 802.11d I believe, from the early 2000s. >>> >>> Dan >>> >>>> beacons >>>> around it, determine what the local regulatory domain is based on the >>>> beacons it hears, and then lock to that regulatory domain. It's >>>> possible for that information to be propagated up to the card's host >>>> and the regulatory domain then would affect both cards. That's how >>>> it's supposed to work, though I don't factually know Linux does this >>>> in all cases. Could it be you're somewhere where CN is the local >>>> regulatory domain and the TL-WN722N has this feature? >>>> >>>> In any case, as Arend points out, despite the hand-wringing that >>>> regulatory domains cause users trying to do something particular, >>>> between certain rules and regulations and certain manufacturers bad >>>> interpretations and implementations around it, there's little that >>>> can >>>> be done about it. Fact is, your radio must comply to whatever >>>> regulatory domain you are in, otherwise it's breaking the rules. And >>>> people breaking the regulatory rules is part of what's gotten >>>> governments to pass even worse (for us OSS guys) laws that tighten >>>> those rules down further. >>>> >>>> You asked who to contact. Its not the LKML - it's your relevant >>>> government body. And certain manufacturers who improperly interpret >>>> said rules because it's easier for them. >>>> >>>> - Steve >>>> >>>> -- >>>> Steve deRosier >>>> Cal-Sierra Consulting LLC >>>> https://www.cal-sierra.com/ >> >> > > > -- > Ben Greear <gree...@candelatech.com> > Candela Technologies Inc http://www.candelatech.com >
Re: second wifi card enforce CN reg dom
Hi. I thought I made myself clear. I leave in France. My system(s) is/are set up to use FR as default regulatory domain. But when I plug in that tp-link card, I am restricted to use CN regulatory domain. Why am I the only one to see this as a problem ? I know that one can only have one regdom defined on the system. I have set it up myself. So why is it changed behind my back by some card or whatever ? Like I said, I am left with the option, to disable crda, or to use 2 systems, one for each card ! Or may be try Windows when this is not messed up like that ??? Well, it's not on Windows that I will be able to use monitor mode, anyway. Never mind. 2018-04-12 17:52 GMT+02:00 Dan Williams <d...@redhat.com>: > On Thu, 2018-04-12 at 08:18 -0700, Steve deRosier wrote: >> On Thu, Apr 12, 2018 at 3:51 AM, Arend van Spriel >> <arend.vanspr...@broadcom.com> wrote: >> > On 4/12/2018 10:42 AM, solsTiCe d'Hiver wrote: >> > > >> > > Hi. >> > > >> > > This is beyond my comprehension that you could assert this is a >> > > non issue. >> > >> > >> > Well. I am just saying that it is by design. There is no way for >> > the >> > regulatory code to determine where you and your hardware actually >> > reside so >> > instead it takes a conservative approach. >> > >> >> To say it another way: mixing regulatory domains on your host system >> should result in a _smaller_ set of channels - ie only those channels >> at the intersection of the two. >> >> And another wrinkle to consider - one of the 802.11 amendments (can't >> remember which one) actually causes the radio to listen to the > > 802.11d I believe, from the early 2000s. > > Dan > >> beacons >> around it, determine what the local regulatory domain is based on the >> beacons it hears, and then lock to that regulatory domain. It's >> possible for that information to be propagated up to the card's host >> and the regulatory domain then would affect both cards. That's how >> it's supposed to work, though I don't factually know Linux does this >> in all cases. Could it be you're somewhere where CN is the local >> regulatory domain and the TL-WN722N has this feature? >> >> In any case, as Arend points out, despite the hand-wringing that >> regulatory domains cause users trying to do something particular, >> between certain rules and regulations and certain manufacturers bad >> interpretations and implementations around it, there's little that >> can >> be done about it. Fact is, your radio must comply to whatever >> regulatory domain you are in, otherwise it's breaking the rules. And >> people breaking the regulatory rules is part of what's gotten >> governments to pass even worse (for us OSS guys) laws that tighten >> those rules down further. >> >> You asked who to contact. Its not the LKML - it's your relevant >> government body. And certain manufacturers who improperly interpret >> said rules because it's easier for them. >> >> - Steve >> >> -- >> Steve deRosier >> Cal-Sierra Consulting LLC >> https://www.cal-sierra.com/
Re: second wifi card enforce CN reg dom
Nobody cares about this ? Should I report this as a bug to the LKML ? or elsewhere ? to ath9k_htc dev ? to crda dev ? Please. 2018-04-10 21:57 GMT+02:00 solsTiCe d'Hiver <solstice.dhi...@gmail.com>: > hi. > > I am trying to capture on 2 channels at the same time with 2 cards. > > One card is TP-Link TL-W722N v1 using ath9k_htc and the second one is > an Alfa AWUS051NH v2 using rt2800usb. > > I have tried this, first, on raspberry pi 0 W using archlinux-arm and > reproduced the issue on a netbook using archlinux x64 too using latest > kernel and drivers. (seems to happen on ubuntu 17.10 on dell laptop > too) > > So when the Alfa card is used alone using the default reg dom FR, one > can change to 112 channel for example (using iw dev wlan1 set channel > 112) > > But once the tp-link is plugged in, reg dom seems to become CN and one > can't change the alfa card to 112 channel. > > iw reg get output change from > global > country FR: DFS-ETSI > (2402 - 2482 @ 40), (N/A, 20), (N/A) > (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW > (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS > (57000 - 66000 @ 2160), (N/A, 40), (N/A) > to > global > country 98: DFS-UNSET > (2402 - 2482 @ 40), (N/A, 20), (N/A) > (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW > (57240 - 59400 @ 2160), (N/A, 28), (N/A) > (59400 - 63720 @ 2160), (N/A, 40), (N/A) > (63720 - 65880 @ 2160), (N/A, 28), (N/A) > > phy#2 > country CN: DFS-FCC > (2402 - 2482 @ 40), (N/A, 20), (N/A) > (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW > (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW > (5735 - 5835 @ 80), (N/A, 30), (N/A) > (57240 - 59400 @ 2160), (N/A, 28), (N/A) > (59400 - 63720 @ 2160), (N/A, 44), (N/A) > (63720 - 65880 @ 2160), (N/A, 28), (N/A) > > > and all the channels above 100 are marked as disabled in iw list > output (after the plug not before) for the alfa card > > It is as if the TL-WN722N has CN reg dom hard-coded and that switches > it globally to CN too ??? > > Is this a bug in ath9k_htc ? a bug with the TL-WN722N card ??
second wifi card enforce CN reg dom
hi. I am trying to capture on 2 channels at the same time with 2 cards. One card is TP-Link TL-W722N v1 using ath9k_htc and the second one is an Alfa AWUS051NH v2 using rt2800usb. I have tried this, first, on raspberry pi 0 W using archlinux-arm and reproduced the issue on a netbook using archlinux x64 too using latest kernel and drivers. (seems to happen on ubuntu 17.10 on dell laptop too) So when the Alfa card is used alone using the default reg dom FR, one can change to 112 channel for example (using iw dev wlan1 set channel 112) But once the tp-link is plugged in, reg dom seems to become CN and one can't change the alfa card to 112 channel. iw reg get output change from global country FR: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A) to global country 98: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (57240 - 59400 @ 2160), (N/A, 28), (N/A) (59400 - 63720 @ 2160), (N/A, 40), (N/A) (63720 - 65880 @ 2160), (N/A, 28), (N/A) phy#2 country CN: DFS-FCC (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 59400 @ 2160), (N/A, 28), (N/A) (59400 - 63720 @ 2160), (N/A, 44), (N/A) (63720 - 65880 @ 2160), (N/A, 28), (N/A) and all the channels above 100 are marked as disabled in iw list output (after the plug not before) for the alfa card It is as if the TL-WN722N has CN reg dom hard-coded and that switches it globally to CN too ??? Is this a bug in ath9k_htc ? a bug with the TL-WN722N card ??
