| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1848f4fa-bc38-44b3-a6c2-8c97a765bfb1@quicinc.com>
Date: Tue, 10 Dec 2024 10:32:31 +0800
From: "Yu Zhang (Yuriy)" <quic_yuzha@...cinc.com>
To: Janusz Dziedzic <janusz.dziedzic@...il.com>
CC: Jose Ignacio Tornos Martinez <jtornosm@...hat.com>,
<ath11k@...ts.infradead.org>, <jjohnson@...nel.org>,
<kvalo@...nel.org>, <linux-kernel@...r.kernel.org>,
<linux-wireless@...r.kernel.org>, <quic_cjhuang@...cinc.com>,
<vbenes@...hat.com>
Subject: Re: [PATCH] wifi: ath11k: allow APs combination when dual stations
are supported
On 12/9/2024 7:23 PM, Janusz Dziedzic wrote:
> wt., 3 gru 2024 o 11:57 Yu Zhang (Yuriy) <quic_yuzha@...cinc.com> napisał(a):
>>
>>
>>
>> On 12/3/2024 5:48 PM, Jose Ignacio Tornos Martinez wrote:
>>>> Which chip do you use?
>>> Since I am not totally sure about the useful information, let me show you
>>> the kernel logs:
>>> $ dmesg | grep ath11k
>>> [ 3.659388] ath11k_pci 0000:01:00.0: BAR 0 [mem 0x84200000-0x843fffff 64bit]: assigned
>>> [ 3.659405] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)
>>> [ 3.659649] ath11k_pci 0000:01:00.0: MSI vectors: 32
>>> [ 3.659653] ath11k_pci 0000:01:00.0: wcn6855 hw2.1
>>> [ 4.871571] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0xff soc_id 0x400c0210
>>> [ 4.871586] ath11k_pci 0000:01:00.0: fw_version 0x11088c35 fw_build_timestamp 2024-04-17 08:34 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
>>> [ 5.241485] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
>>>
>> yes, you also use wcn6855 hw2.1.
>>> If I try to setup 2 APs with your interface combination I get this:
>>> # iw list | grep -A6 "valid interface combinations:"
>>> valid interface combinations:
>>> * #{ managed } <= 2, #{ AP, P2P-client, P2P-GO } <= 16, #{ P2P-device } <= 1,
>>> total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }
>>>
>>> * #{ managed } <= 2, #{ AP, P2P-client, P2P-GO } <= 16, #{ P2P-device } <= 1,
>>> total <= 3, #channels <= 2, STA/AP BI must match
>>> HT Capability overrides:
>> 2 combinations are to support DBS and DFS.
>> Combinations is correct. channels=2, max interfaces=3.
>>
> Small question from my side. If phyX will support 3 bands (2.4/5/6)
> what this channes<=2 limitation mean here for APs?
> a) can I setup APs on 2412 and 5180
> b) or even can setup APs on 2412 and 2462?
> c) or setup APs on 5180 and 6055?
> How could I know a or b or c is allowed?
>
all allowed, but recommend more 2.4g + 5g and 2.4g + 6g.
> BTW, do you plan to share same firmware (with 2 possible APs) for
> ath12k and WCN7850?
>
WCN7850 use different firmware, when ath11k done will plan about ath12k
about it.
And by the way, if you try in ath11k with 2 aps?
> BR
> Janusz
>
>> And you want setup sta + sap + sap, right?
>> When up the second sap will meet error? Could you pls share the error logs?
>>
>> I'm not very sure if you add all interface with managed type, and do
>> "ifconfig xxx up" before running hostapd.
>>
>> You can try add second and third interface with
>> "iw dev xx interface add xx type __ap".
>>
>>
>>> # iw dev
>>> phy#0
>>> Interface wlp1s0_1
>>> ifindex 6
>>> wdev 0x4
>>> addr a2:42:d2:1e:89:a3
>>> type managed
>>> txpower 16.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>> Interface wlp1s0_0
>>> ifindex 5
>>> wdev 0x3
>>> addr 52:e9:be:33:6a:61
>>> ssid test-qe-wpa2-psk
>>> type AP
>>> channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz
>>> txpower 14.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>> Interface wlp1s0
>>> ifindex 3
>>> wdev 0x1
>>> addr c8:94:02:b5:fe:fb
>>> type managed
>>> txpower 16.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>> Or even this with no AP up:
>>> # iw dev
>>> phy#0
>>> Interface wlp1s0_1
>>> ifindex 6
>>> wdev 0x4
>>> addr ca:e5:84:22:10:ec
>>> type managed
>>> txpower 16.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>> Interface wlp1s0_0
>>> ifindex 5
>>> wdev 0x3
>>> addr 9e:4e:c5:ea:4c:e9
>>> type AP
>>> txpower 16.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>> Interface wlp1s0
>>> ifindex 3
>>> wdev 0x1
>>> addr c8:94:02:b5:fe:fb
>>> type managed
>>> txpower 16.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>>
>>> If I use the parameter to ignore the feature and configure the interface combination as before:
>>> # iw list | grep -A4 "valid interface combinations:"
>>> valid interface combinations:
>>> * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 16, #{ P2P-device } <= 1,
>>> total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
>>>
>>> HT Capability overrides:
>>> # iw dev
>>> phy#1
>>> Interface wlp1s0_1
>>> ifindex 7
>>> wdev 0x100000004
>>> addr 82:90:89:90:c1:37
>>> ssid test-qe-wpa3-psk
>>> type AP
>>> channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz
>>> txpower 16.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>> Interface wlp1s0_0
>>> ifindex 6
>>> wdev 0x100000003
>>> addr 6a:ef:d0:db:10:f0
>>> ssid test-qe-wpa2-psk
>>> type AP
>>> channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz
>>> txpower 16.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>> Interface wlp1s0
>>> ifindex 4
>>> wdev 0x100000001
>>> addr c8:94:02:b5:fe:fb
>>> type managed
>>> txpower 16.00 dBm
>>> multicast TXQ:
>>> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
>>> 0 0 0 0 0 0 0 0 0
>>>
>>> Thanks
>>>
>>> Best regards
>>> Jose Ignacio
>>>
>>
>>
>
>
Powered by blists - more mailing lists