-
Notifications
You must be signed in to change notification settings - Fork 757
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
WPA broken for wifi after 24.7 update #8080
Comments
FreeBSD and wireless isn't a great combination, we usually advise to use separate access points (https://docs.opnsense.org/manual/wireless.html). |
might be the same as #8079 |
Thanks for the helpful reply. That's unfortunate, I really liked having it contained in one device for home use, and really don't need any more power cords or usb cables in my rats nest of wires 😆 . I'm curious, if it's not advised and not currently supported/functioning - why not just remove wireless APs from opnsense? |
No problem, you're welcome. Did you check the other issue that came in after yours? It might contain the fix for your issue as well (see the
We considered it at some point, but left the efforts at the community. If someone points to a bug and figures out why it fails, we sometimes intervene and offer a fix (like with the other ticket). Our efforts on this subject are just highly limited, also because of the limited commercial interest (we don't build equipment with wireless for example). |
Applying a patch in FreeBSD is a little beyond me. Has this patch been pushed to the master branch? Also you wouldn't happen to know why, prior to the 24.7 update that broke the AP, my AP would stop being able to connect whenever an update was available. I would inevitably have to run the update to keep using my internet connection, which is what landed me in this position. Is this a security feature that could be disabled by any chance? |
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
After updating to 24.7, wifi AP stops broadcasting and I cannot get it working again. This broke back in August and still doesn't seem to be working after the last four updates.
Please see this thread for numerous detailed reports.
The text was updated successfully, but these errors were encountered: