Forum › Forums › New users › New Users and General Questions › [Solved] How do I enable 5 GHz DFS Wi-Fi Channels?
- This topic has 8 replies, 2 voices, and was last updated Apr 8-7:13 am by dfswifi.
-
AuthorPosts
-
April 5, 2020 at 9:39 am #34381Member
dfswifi
Is there a guide on how to enable 5 GHz DFS Wi-Fi channels in antiX? I can’t find anything by googling.
I have a Wi-Fi access point using 5 GHz DFS Wi-Fi channels. It works just fine and other devices (including my Ubuntu laptop) can connect to it. However, my antiX laptop doesn’t even see the Wi-Fi access point, even if the Wi-Fi card in the laptop supports the 5 GHz DFS Wi-Fi channels.
Non-DFS channels (channels lower than 48) work just fine. The laptop is a Dell Latitude E6510.
$ iw list | grep MHz | grep -v disabled
* 5160 MHz [32] (23.0 dBm)
* 5170 MHz [34] (23.0 dBm)
* 5180 MHz [36] (23.0 dBm)
* 5190 MHz [38] (23.0 dBm)
* 5200 MHz [40] (23.0 dBm)
* 5210 MHz [42] (23.0 dBm)
* 5220 MHz [44] (23.0 dBm)
* 5230 MHz [46] (23.0 dBm)
* 5240 MHz [48] (23.0 dBm)
* 5260 MHz [52] (20.0 dBm) (radar detection)
* 5270 MHz [54] (20.0 dBm) (radar detection)
* 5280 MHz [56] (20.0 dBm) (radar detection)
* 5290 MHz [58] (20.0 dBm) (radar detection)
* 5300 MHz [60] (20.0 dBm) (radar detection)
* 5310 MHz [62] (20.0 dBm) (radar detection)
* 5320 MHz [64] (20.0 dBm) (radar detection)
* 5330 MHz [66] (20.0 dBm) (radar detection)
* 5340 MHz [68] (20.0 dBm) (radar detection)
* 5480 MHz [96] (27.0 dBm) (radar detection)
* 5490 MHz [98] (27.0 dBm) (radar detection)
* 5500 MHz [100] (27.0 dBm) (radar detection)
* 5510 MHz [102] (27.0 dBm) (radar detection)
* 5520 MHz [104] (27.0 dBm) (radar detection)
* 5530 MHz [106] (27.0 dBm) (radar detection)
* 5540 MHz [108] (27.0 dBm) (radar detection)
* 5550 MHz [110] (27.0 dBm) (radar detection)
* 5560 MHz [112] (27.0 dBm) (radar detection)
* 5570 MHz [114] (27.0 dBm) (radar detection)
* 5580 MHz [116] (27.0 dBm) (radar detection)
* 5590 MHz [118] (27.0 dBm) (radar detection)
* 5600 MHz [120] (27.0 dBm) (radar detection)
* 5610 MHz [122] (27.0 dBm) (radar detection)
* 5620 MHz [124] (27.0 dBm) (radar detection)
* 5630 MHz [126] (27.0 dBm) (radar detection)
* 5640 MHz [128] (27.0 dBm) (radar detection)
* 5650 MHz [130] (27.0 dBm) (radar detection)
* 5660 MHz [132] (27.0 dBm) (radar detection)
* 5670 MHz [134] (27.0 dBm) (radar detection)
* 5680 MHz [136] (27.0 dBm) (radar detection)
* 5690 MHz [138] (27.0 dBm) (radar detection)
* 5700 MHz [140] (27.0 dBm) (radar detection)
* 5710 MHz [142] (27.0 dBm) (radar detection)$ iw reg get
global country FI: DFS-ETSI
(2400 – 2483 @ 40), (N/A, 20), (N/A)
(5150 – 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 – 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 – 5725 @ 160), (N/A, 27), (0 ms), DFS
(57000 – 66000 @ 2160), (N/A, 40), (N/A)$ iwlist wlan0 freq
wlan0 32 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Channel 12 : 2.467 GHz
Channel 13 : 2.472 GHz
Channel 32 : 5.16 GHz
Channel 34 : 5.17 GHz
Channel 36 : 5.18 GHz
Channel 38 : 5.19 GHz
Channel 40 : 5.2 GHz
Channel 42 : 5.21 GHz
Channel 44 : 5.22 GHz
Channel 46 : 5.23 GHz
Channel 48 : 5.24 GHz
Channel 52 : 5.26 GHz
Channel 54 : 5.27 GHz
Channel 56 : 5.28 GHz
Channel 58 : 5.29 GHz
Channel 60 : 5.3 GHz
Channel 62 : 5.31 GHz
Channel 64 : 5.32 GHz
Channel 66 : 5.33 GHz
Channel 68 : 5.34 GHz
Channel 96 : 5.48 GHz
Current Frequency:5.18 GHz (Channel 36)- This topic was modified 3 years, 1 month ago by dfswifi.
April 5, 2020 at 10:17 am #34386Member
Xecure
::I know 5GHz wifi works on antiX with connman (using it right now), but no idea about DFS.
My output:
$ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A)No DFS country is seton my end.
If your country is’t “FI”, and you know your DFS code, set it using
iw reg set countrycode
replacing “countrycode” with the correct country code
If FI is correct and it is set in your antiX system, then I don’t know how to follow up. Sorry.antiX Live system enthusiast.
General Live Boot Parameters for antiX.April 5, 2020 at 10:18 am #34387Member
Xecure
::However, my antiX laptop doesn’t even see the Wi-Fi access point
Does it see other access points?
antiX Live system enthusiast.
General Live Boot Parameters for antiX.April 5, 2020 at 10:29 am #34389Memberdfswifi
::Yes, it can see other 5 GHz access points, but none of the DFS access points.
FI is my correct country code and I set it with iw reg set.
April 5, 2020 at 10:45 am #34392Member
Xecure
::I will be guessing now, and probably you have already checked all this before.
Have you tested the exact same hardware on other linux systems (like the Ubuntu you mention)? Does it work there? Do both use the exact same wifi driver and firmware?
If only antiX has this problem, it may be related to connman (I don’t think so), and maybe ceni does detect it (try to see if ceni can detect the SSID).I can’t help much with this here, sorry about this. Maybe someone else has any idea.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.April 5, 2020 at 12:00 pm #34397Memberdfswifi
::I got the DFS channels to work with AntiX on my Ubuntu laptop using AntiX 19.2 with kernel 4.19. I’ll have to test the Latitude with the same version and/or Ubuntu.
April 7, 2020 at 1:15 pm #34462Memberdfswifi
::So, turns out the issue is specific to antiX. I tried antiX 19.2 with kernel 4.19 and the DFS channels are nonfunctional, same as on antiX 17.1. As soon as I boot into Ubuntu everything works just fine on the Latitude. Perhaps it’s a driver issue? Ubuntu uses different drivers.
antiX:
lspci -nnk | grep -i Broadcom -a3
03:00.0 Network controller [0280]: Broadcom Limited BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Dell Wireless 1520 Half-size Mini PCIe Card [1028:000e]
Kernel driver in use: wl
Kernel modules: bcma, wl$ ethtool -i wlan0
driver: wl0
version: 6.30.223.271 (r587334)
firmware-version:
expansion-rom-version:
bus-info:
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no$ modinfo wl
filename: /lib/modules/4.19.100-antix.1-amd64-smp/updates/dkms/wl.ko
license: MIXED/Proprietary
license: MIXED/Proprietary
srcversion: 60D2D7E603B418654C8C9AA
alias: pci:v*d*sv*sd*bc02sc80i*
depends: cfg80211
retpoline: Y
name: wl
vermagic: 4.19.100-antix.1-amd64-smp SMP preempt mod_unload modversions
parm: passivemode:int
parm: wl_txq_thresh:int
parm: oneonly:int
parm: piomode:int
parm: instance_base:int
parm: nompc:int
parm: intf_name:string$ modinfo bcma
filename: /lib/modules/4.19.100-antix.1-amd64-smp/kernel/drivers/bcma/bcma.ko
license: GPL
description: Broadcom’s specific AMBA driver
srcversion: E1D7E12AEBABFBE93AE1A69
alias: pci:v000014E4d0000A8DCsv*sd*bc*sc*i*
alias: pci:v000014E4d0000A8DBsv*sd*bc*sc*i*
alias: pci:v000014E4d00004727sv*sd*bc*sc*i*
alias: pci:v000014E4d000043B1sv*sd*bc*sc*i*
alias: pci:v000014E4d000043AAsv*sd*bc*sc*i*
alias: pci:v000014E4d000043A9sv*sd*bc*sc*i*
alias: pci:v000014E4d000043A0sv*sd*bc*sc*i*
alias: pci:v000014E4d00004365sv0000103Csd0000804Abc*sc*i*
alias: pci:v000014E4d00004365sv0000105Bsd0000E092bc*sc*i*
alias: pci:v000014E4d00004365sv00001028sd00000018bc*sc*i*
alias: pci:v000014E4d00004365sv00001028sd00000016bc*sc*i*
alias: pci:v000014E4d00004360sv*sd*bc*sc*i*
alias: pci:v000014E4d00004359sv*sd*bc*sc*i*
alias: pci:v000014E4d00004358sv*sd*bc*sc*i*
alias: pci:v000014E4d00004357sv*sd*bc*sc*i*
alias: pci:v000014E4d00004353sv*sd*bc*sc*i*
alias: pci:v000014E4d00004331sv*sd*bc*sc*i*
alias: pci:v000014E4d0000A8D8sv*sd*bc*sc*i*
alias: pci:v000014E4d00004313sv*sd*bc*sc*i*
alias: pci:v000014E4d00000576sv*sd*bc*sc*i*
depends:
retpoline: Y
intree: Y
name: bcma
vermagic: 4.19.100-antix.1-amd64-smp SMP preempt mod_unload modversionsUbuntu:
$ lspci -nnk | grep Broad -a3
03:00.0 Network controller [0280]: Broadcom Limited BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Dell Wireless 1520 Half-size Mini PCIe Card [1028:000e]
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma$ ethtool -i wlp3s0b1
driver: brcmsmac
version: 4.18.0-15-generic
firmware-version: 610.812
expansion-rom-version:
bus-info: bcma0:1
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no$ modinfo bcma
filename: /lib/modules/4.18.0-15-generic/kernel/drivers/bcma/bcma.ko
license: GPL
description: Broadcom’s specific AMBA driver
srcversion: A58277A768AAB23C742A248
alias: pci:v000014E4d0000A8DCsv*sd*bc*sc*i*
alias: pci:v000014E4d0000A8DBsv*sd*bc*sc*i*
alias: pci:v000014E4d00004727sv*sd*bc*sc*i*
alias: pci:v000014E4d000043B1sv*sd*bc*sc*i*
alias: pci:v000014E4d000043AAsv*sd*bc*sc*i*
alias: pci:v000014E4d000043A9sv*sd*bc*sc*i*
alias: pci:v000014E4d000043A0sv*sd*bc*sc*i*
alias: pci:v000014E4d00004365sv0000103Csd0000804Abc*sc*i*
alias: pci:v000014E4d00004365sv0000105Bsd0000E092bc*sc*i*
alias: pci:v000014E4d00004365sv00001028sd00000018bc*sc*i*
alias: pci:v000014E4d00004365sv00001028sd00000016bc*sc*i*
alias: pci:v000014E4d00004360sv*sd*bc*sc*i*
alias: pci:v000014E4d00004359sv*sd*bc*sc*i*
alias: pci:v000014E4d00004358sv*sd*bc*sc*i*
alias: pci:v000014E4d00004357sv*sd*bc*sc*i*
alias: pci:v000014E4d00004353sv*sd*bc*sc*i*
alias: pci:v000014E4d00004331sv*sd*bc*sc*i*
alias: pci:v000014E4d0000A8D8sv*sd*bc*sc*i*
alias: pci:v000014E4d00004313sv*sd*bc*sc*i*
alias: pci:v000014E4d00000576sv*sd*bc*sc*i*
depends:
retpoline: Y
intree: Y
name: bcma
vermagic: 4.18.0-15-generic SMP mod_unload
signat: PKCS#7
signer:
sig_key:
sig_hashalgo: md4$ modinfo brcmsmac
filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/broadcom/brcm80211/brcmsmac/brcmsmac.ko
firmware: brcm/bcm43xx_hdr-0.fw
firmware: brcm/bcm43xx-0.fw
license: Dual BSD/GPL
description: Broadcom 802.11n wireless LAN driver.
author: Broadcom Corporation
srcversion: 4BEB6B7AE55429E2BCAC16F
alias: bcma:m04BFid0812rev18cl*
alias: bcma:m04BFid0812rev17cl*
alias: bcma:m04BFid0812rev11cl*
depends: mac80211,bcma,brcmutil,cfg80211,cordic
retpoline: Y
intree: Y
name: brcmsmac
vermagic: 4.18.0-15-generic SMP mod_unload
signat: PKCS#7
signer:
sig_key:
sig_hashalgo: md4April 8, 2020 at 4:04 am #34479Member
Xecure
::…
antiX:lspci -nnk | grep -i Broadcom -a3
03:00.0 Network controller [0280]: Broadcom Limited BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Dell Wireless 1520 Half-size Mini PCIe Card [1028:000e]
Kernel driver in use: wl
Kernel modules: bcma, wlUbuntu:
$ lspci -nnk | grep Broad -a3
03:00.0 Network controller [0280]: Broadcom Limited BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Dell Wireless 1520 Half-size Mini PCIe Card [1028:000e]
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcmaMeaning antiX uses wl as wireless driver while ubuntu uses bcma.
I believe bcma was blacklisted in antiX for some broadcom problems, but you can easily whitelist it and load it using the Network Assistant.On your antiX system, Go to Control Center > Maintenance > Network Assistant Then move to the “Linux drivers” tab and choose the bcma driver from the list. Try testing it out by loading it first (Load button). and check if the driver used by the system changes. If it works you can then “Unblacklist Driver”.
Test to see if you can get this to work.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.April 8, 2020 at 7:13 am #34488Memberdfswifi
::Worked like a charm. Issue resolved. Thanks!
I can see why bcma was blacklisted, tho. Wireless performance with it is utter shite.
-
AuthorPosts
- You must be logged in to reply to this topic.