Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ath10k-ct: STA limit of 32 concurrent connections #2604

Closed
blocktrron opened this issue Aug 9, 2022 · 0 comments · Fixed by #2607
Closed

ath10k-ct: STA limit of 32 concurrent connections #2604

blocktrron opened this issue Aug 9, 2022 · 0 comments · Fixed by #2607
Labels
1. severity: blocker This issue/pr is required for the next release
Milestone

Comments

@blocktrron
Copy link
Member

blocktrron commented Aug 9, 2022

The ath10k-ct firmware imposes a lower STA limit than the QCA based flavor, namely 32 vs. 128 connected STAs.

This might be an issue in environments with a lot of concurrently connected clients. The ath10k-ct driver allows configuration of these limits using its fwcfg configuration framework.

The STA limit comes from memory constraints within the wireless system. Thus, we need to reduce the number of concurrent vdevs to increase the number of concurrent stations. This is not much of a problem, as Gluon uses a maximum of 4 VAPs per radio.

See https://www.candelatech.com/ath10k-10.4.php#config

@blocktrron blocktrron added this to the 2022.1 milestone Aug 9, 2022
@blocktrron blocktrron added the 1. severity: blocker This issue/pr is required for the next release label Aug 10, 2022
blocktrron added a commit to blocktrron/gluon that referenced this issue Aug 10, 2022
Increase the peer limit for ath10k-ct from 32 to 128 STAs like it is set
for the non-ct firmware / driver.

Closes freifunk-gluon#2604

Signed-off-by: David Bauer <mail@david-bauer.net>
blocktrron added a commit to blocktrron/gluon that referenced this issue Aug 10, 2022
Increase the peer limit for ath10k-ct from 32 to 128 STAs like it is set
for the non-ct firmware / driver. In order to make this work with the
memory constraints of the wireless platform, reduce the number of
concurrent vdevs to the maximum Gluon uses (4).

Closes freifunk-gluon#2604

Signed-off-by: David Bauer <mail@david-bauer.net>
blocktrron added a commit to blocktrron/gluon that referenced this issue Aug 10, 2022
Increase the peer limit for ath10k-ct from 32 to 128 STAs like it is set
for the non-ct firmware / driver. In order to make this work with the
memory constraints of the wireless platform, reduce the number of
concurrent vdevs to the maximum Gluon uses (4).

Closes freifunk-gluon#2604

Signed-off-by: David Bauer <mail@david-bauer.net>
blocktrron added a commit to blocktrron/gluon that referenced this issue Aug 10, 2022
Increase the peer limit for ath10k-ct from 32 to 96 STAs like it is set
for the non-ct firmware / driver. In order to make this work with the
memory constraints of the wireless platform, reduce the number of
concurrent vdevs to the maximum Gluon uses (4).

Closes freifunk-gluon#2604

Signed-off-by: David Bauer <mail@david-bauer.net>
blocktrron added a commit to blocktrron/gluon that referenced this issue Aug 10, 2022
Increase the peer limit for ath10k-ct from 32 to 96 STAs like it is set
for the non-ct firmware / driver. In order to make this work with the
memory constraints of the wireless platform, reduce the number of
concurrent vdevs to the maximum Gluon uses (4).

Closes freifunk-gluon#2604

Signed-off-by: David Bauer <mail@david-bauer.net>
JayBraker pushed a commit to JayBraker/gluon that referenced this issue Apr 12, 2023
Increase the peer limit for ath10k-ct from 32 to 96 STAs like it is set
for the non-ct firmware / driver. In order to make this work with the
memory constraints of the wireless platform, reduce the number of
concurrent vdevs to the maximum Gluon uses (4).

Closes freifunk-gluon#2604

Signed-off-by: David Bauer <mail@david-bauer.net>

Signed-off-by: David Bauer <mail@david-bauer.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. severity: blocker This issue/pr is required for the next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant