That's correct. I uninstalled the wireless package, installed the wifi-qcom-ac package, configured wlan1 and wlan2 interfaces again, and...clients can't associate. I've returned to the wireless package for now, but I was wondering if anyone has any general tips. (I see someone else just posted a similar problem.)1. question is not clear. You loaded wifi-qcom-ac driver on AC2 and then having problems ? Or something else ?
OK, excellent. Once I get past #1 I'll add CAPsMAN to the mix.2. you can specify on interface basis which ones participate in capsman and which not. But you can also define that separate SSID as a separate config in capsman, leaving everything on AC2 as default (for a cap device) as it can be.
Just the DHCP server section? Any other sections?3. You need to show config or anyone can guess away ...
The hAP ac^3 offers a little better wireless radio coverage, and for that reason it's working better to have the ac^3 and ac^2 in their respective physical locations. But I'll give that idea some more thought.4. Not really but for my understanding, why don't you swap ac3 and ac2 from place in your network ? Having wifi-qcom-ac installed that ac2 is going to be VERY space restricted on storage and the only thing it might still reliably do then is ... being an access point. Nothing more.
The fact you're going to foresee capsman, DNS, DoH on AC3, ... all are indications of this as well. It's more logical then to have ac3 facing ISP router directly.
My view, others may disagree.
It's not the most urgent task item, but it's an option the ISP offers.5. no comment. Don't really know what that is. But the little I do know is that it is basically 6to4, so actually using IPv4. If not real IPv6, why bother ?
Why do you need IPv6 if IPv4 still works for you ? Just a question.
Statistics: Posted by BBCWatcher — Sun Jan 28, 2024 2:19 pm