# AP Firmware 2.2v Released! **URL:** \ **Category:** Access Points\ **Tags:** firmware\ **Created:** [December 11, 2025, 10:57pm UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316 "2025-12-11T22:57:13Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Alta-MikeD](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-miked/32/1942_2.png) [@Alta-MikeD](https://forum.alta.inc/u/Alta-MikeD)\ **Post date:** [December 11, 2025, 10:57pm UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/1 "2025-12-11T22:57:13Z")
This update includes refinements that enhance hotspot operation and provide improved insight into client activity. - Add support for displaying password/voucher used in Devices List. - Resolve issue when incorrect hotspot certificate is used when Let’s Encrypt certificate is renewed. **This update is being rolled out now.** You can manually initiate the upgrade if you’d like, or it will automatically update overnight (if auto-updates are enabled). The complete, up-to-date change log is available here: > [@AP - Release Notes](https://forum.alta.inc/t/ap-release-notes/318#p-717-h-22v-1): > > Thanks for all of your feedback helping improve the Alta products! 2.2w Released on 12/11/2025 Improve stability in statistics task. 2.2v Released on 12/11/2025 Add support for displaying password/voucher used in Devices List. Resolve issue when incorrect hotspot certificate is used when Let’s Encrypt certificate is renewed. 2.2u Released on 11/25/2025 Resolve issues with passwordless captive portal requiring password. 2.2t Released on 11/17/2025 Add support for WiFi Vouchers. Add su… As always, if you have questions or encounter any issues, feel free to reply here or start a new topic. Please include details about the issue so we can assist you effectively. ---
**Author:** ![jmszuch](https://forum.alta.inc/letter_avatar_proxy/v4/letter/j/b2d939/32.png) [@jmszuch](https://forum.alta.inc/u/jmszuch)\ **Post date:** [December 11, 2025, 11:42pm UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/2 "2025-12-11T23:42:30Z")
Thanks, Mike! Update seemed to install OK, but I started seeing this crash logged after updating a couple of APs manually. ```auto Dec 11 18:38:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:37:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:37:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:36:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:34:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:33:45 LivingRoomAP daemon.info procd: Instance radsecproxy::instance1 s in a crash loop 6 crashes, 0 seconds since last crash Dec 11 18:33:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:32:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:32:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:31:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:31:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:30:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:30:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:29:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:29:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:28:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:28:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:27:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:27:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:26:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:26:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:25:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:25:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:24:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:24:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:23:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:23:01 LivingRoomAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:22:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:21:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:20:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:19:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:18:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:17:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:16:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:15:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:14:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:13:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:12:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:11:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:10:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:09:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:08:12 LivingRoomAP daemon.info procd: Instance radsecproxy::instance1 s in a crash loop 6 crashes, 0 seconds since last crash Dec 11 18:08:01 HallwayAP user.notice root: sent crash from /var/run/oops/2 Dec 11 18:08:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:07:05 HallwayAP user.notice root: failed to send crash (/var/run/oops/1): curl: (6) Could not resolve host: manage.alta.inc Dec 11 18:06:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:05:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:04:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:03:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 ``` Seemed to continue even after rebooting the access points again. Wireless devices seem to be operating properly at the moment, but I wanted to post this just in case anyone else spotted this behavior. I’ll try to post an update if I notice it continuing tonight. Quick edit: This seems to precede these crashes that are being logged ```auto Dec 11 18:52:01 HallwayAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962801] bfe0: 76eb6fac 76995ac4 0000feff 76f64174 60000010 ffffffff Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962794] bfc0: 00000000 01ca9db0 00000000 01ca9db0 76b847fc 00000000 00000002 76b4ece0 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962786] bfa0: 00000000 00000000 01ca9c68 00000000 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962780] Exception stack(0x95f3bfb0 to 0x95f3bff8) Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962775] [<80312bb8>] (do_DataAbort) from [<80301d5c>] (__dabt_usr+0x3c/0x40) Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962767] [<80312a18>] (do_page_fault) from [<80312bb8>] (do_DataAbort+0x38/0xb8) Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962759] [<8031266c>] (__do_user_fault) from [<80312a18>] (do_page_fault+0x2e4/0x324) Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962750] [<808e743c>] (dump_stack) from [<8031266c>] (__do_user_fault+0xbc/0xfc) Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962739] [<8030aaf4>] (show_stack) from [<808e743c>] (dump_stack+0x88/0xa8) Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962728] [<8030e9b0>] (unwind_backtrace) from [<8030aaf4>] (show_stack+0x10/0x14) Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962706] Hardware name: ipq5018-ap6pro, Version: 2.2v Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962701] CPU: 1 PID: 14520 Comm: rcstats Tainted: P 5.4.213 #0 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962694] Control: 10c0383d Table: 5859c06a DAC: 00000055 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962690] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962684] r3 : 00000000 r2 : 01ca9c68 r1 : 00000000 r0 : 00000000 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962680] r7 : 01ca9db0 r6 : 00000000 r5 : 01ca9db0 r4 : 00000000 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962676] r10: 00000002 r9 : 00000000 r8 : 76b847fc Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962673] sp : 76995ac4 ip : 76eb6fac fp : 76b4ece0 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962669] pc : [<76f64174>] lr : [<0000feff>] psr: 60000010 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962665] LR is at 0xfeff Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962661] PC is at 0x76f64174 Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962650] Hardware name: ipq5018-ap6pro, Version: 2.2v Dec 11 18:52:00 HallwayAP kern.warn kernel: [1033.962647] CPU: 1 PID: 14520 Comm: rcstats Tainted: P 5.4.213 #0 Dec 11 18:52:00 HallwayAP kern.err kernel: [1033.962630] [00000000] *pgd=5802f835, *pte=00000000, *ppte=00000000 Dec 11 18:52:00 HallwayAP kern.err kernel: [1033.962626] pgd = 240a8854 Dec 11 18:52:00 HallwayAP kern.err kernel: [1033.962618] rcstats: unhandled page fault (11) at 0x00000000, code 0x017 Dec 11 18:52:00 HallwayAP kern.err kernel: [1033.962602] 8<--- cut here --- ``` Second Edit: Seeing this on an AP at another test site as well unfortunately ☹ Seems to specifically be affecting stat collection? ```auto Dec 11 18:59:01 TestAP user.notice root: sent crash from /var/run/oops/1 Dec 11 18:59:01 TestAP user.notice root: scanning... Dec 11 18:59:00 TestAP kern.warn kernel: [145.473877] bfe0: 76ef1fac 769d0ac4 0000feff 76f9f174 60000010 ffffffff Dec 11 18:59:00 TestAP kern.warn kernel: [145.473870] bfc0: 00000000 01730f10 00000000 01730f10 0173124c 00000003 00000001 76ae7f90 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473862] bfa0: 00000000 00000000 01730dbc 00000000 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473855] Exception stack(0x9101bfb0 to 0x9101bff8) Dec 11 18:59:00 TestAP kern.warn kernel: [145.473850] [<80312bb8>] (do_DataAbort) from [<80301d5c>] (__dabt_usr+0x3c/0x40) Dec 11 18:59:00 TestAP kern.warn kernel: [145.473840] [<80312a18>] (do_page_fault) from [<80312bb8>] (do_DataAbort+0x38/0xb8) Dec 11 18:59:00 TestAP kern.warn kernel: [145.473832] [<8031266c>] (__do_user_fault) from [<80312a18>] (do_page_fault+0x2e4/0x324) Dec 11 18:59:00 TestAP kern.warn kernel: [145.473822] [<808e743c>] (dump_stack) from [<8031266c>] (__do_user_fault+0xbc/0xfc) Dec 11 18:59:00 TestAP kern.warn kernel: [145.473806] [<8030aaf4>] (show_stack) from [<808e743c>] (dump_stack+0x88/0xa8) Dec 11 18:59:00 TestAP kern.warn kernel: [145.473792] [<8030e9b0>] (unwind_backtrace) from [<8030aaf4>] (show_stack+0x10/0x14) Dec 11 18:59:00 TestAP kern.warn kernel: [145.473759] Hardware name: ipq5018-ap6pro, Version: 2.2v Dec 11 18:59:00 TestAP kern.warn kernel: [145.473755] CPU: 1 PID: 4777 Comm: rcstats Tainted: P 5.4.213 #0 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473748] Control: 10c0383d Table: 5bdf406a DAC: 00000055 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473744] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user Dec 11 18:59:00 TestAP kern.warn kernel: [145.473738] r3 : 00000000 r2 : 01730dbc r1 : 00000000 r0 : 00000000 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473734] r7 : 01730f10 r6 : 00000000 r5 : 01730f10 r4 : 00000000 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473730] r10: 00000001 r9 : 00000003 r8 : 0173124c Dec 11 18:59:00 TestAP kern.warn kernel: [145.473726] sp : 769d0ac4 ip : 76ef1fac fp : 76ae7f90 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473722] pc : [<76f9f174>] lr : [<0000feff>] psr: 60000010 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473718] LR is at 0xfeff Dec 11 18:59:00 TestAP kern.warn kernel: [145.473710] PC is at 0x76f9f174 Dec 11 18:59:00 TestAP kern.warn kernel: [145.473692] Hardware name: ipq5018-ap6pro, Version: 2.2v Dec 11 18:59:00 TestAP kern.warn kernel: [145.473687] CPU: 1 PID: 4777 Comm: rcstats Tainted: P 5.4.213 #0 Dec 11 18:59:00 TestAP kern.err kernel: [145.473669] [00000000] *pgd=5cf09835, *pte=00000000, *ppte=00000000 Dec 11 18:59:00 TestAP kern.err kernel: [145.473664] pgd = 0d153ce3 Dec 11 18:59:00 TestAP kern.err kernel: [145.473653] rcstats: unhandled page fault (11) at 0x00000000, code 0x017 Dec 11 18:59:00 TestAP kern.err kernel: [145.473628] 8<--- cut here --- ``` ---
**Author:** ![Alta-MikeD](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-miked/32/1942_2.png) [@Alta-MikeD](https://forum.alta.inc/u/Alta-MikeD)\ **Post date:** [December 12, 2025, 12:12am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/3 "2025-12-12T00:12:51Z")
Thanks for the report @jmszuch. I’m seeing something here too. At least partially the same.. just got off a call, wanted to acknowledge we’ve seen your report and are investigating. ---
**Author:** ![Alta-MikeD](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-miked/32/1942_2.png) [@Alta-MikeD](https://forum.alta.inc/u/Alta-MikeD)\ **Post date:** [December 12, 2025, 12:17am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/4 "2025-12-12T00:17:19Z")
Confirming there is a bug with `rcstats`, and there is a fix already, too. It was in the build of 2.2v we were testing internally but for some reason it missed the public tag. Investigating further, we’ll follow up. ---
**Author:** ![jmszuch](https://forum.alta.inc/letter_avatar_proxy/v4/letter/j/b2d939/32.png) [@jmszuch](https://forum.alta.inc/u/jmszuch)\ **Post date:** [December 12, 2025, 12:18am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/5 "2025-12-12T00:18:22Z")
Thanks, Mike! Appreciate the update 🙂 ---
**Author:** ![Alta-MikeD](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-miked/32/1942_2.png) [@Alta-MikeD](https://forum.alta.inc/u/Alta-MikeD)\ **Post date:** [December 12, 2025, 1:34am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/6 "2025-12-12T01:34:25Z")
No problem! The update with the `rcstats` fix is currently in testing. We’re doing a final verification and aiming to release tonight, pending that everything looks good. ---
**Author:** ![jmszuch](https://forum.alta.inc/letter_avatar_proxy/v4/letter/j/b2d939/32.png) [@jmszuch](https://forum.alta.inc/u/jmszuch)\ **Post date:** [December 12, 2025, 1:47am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/7 "2025-12-12T01:47:08Z")
Thanks again! Fingers crossed everything looks good after the quick round of testing. Somewhat related as I imagine it may have gotten side lined by this, but is there a new switch firmware release as well? I see it looks like 2.3n is waiting in the wings but there aren’t any release notes quite yet. Thanks! ---
**Author:** ![Alta-MikeD](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-miked/32/1942_2.png) [@Alta-MikeD](https://forum.alta.inc/u/Alta-MikeD)\ **Post date:** [December 12, 2025, 1:52am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/8 "2025-12-12T01:52:45Z")
> [@jmszuch](#): > > I see it looks like 2.3n is waiting in the wings but there aren’t any release notes quite yet. Yeah, I got distracted by the bug report, so I’m sorry, that’s on me. I should’ve had those release notes up already.. Getting them posted now. Thanks! ---
**Author:** ![jmszuch](https://forum.alta.inc/letter_avatar_proxy/v4/letter/j/b2d939/32.png) [@jmszuch](https://forum.alta.inc/u/jmszuch)\ **Post date:** [December 12, 2025, 2:01am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/9 "2025-12-12T02:01:14Z")
Totally understand! Figured I’d ask since I was thinking about it. Much appreciate you getting this and the switch release notes handled 😃 ---
**Author:** ![Alta-MikeD](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-miked/32/1942_2.png) [@Alta-MikeD](https://forum.alta.inc/u/Alta-MikeD)\ **Post date:** [December 12, 2025, 2:01am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/10 "2025-12-12T02:01:48Z")
FWIW, 2.2w is live, release notes, posts, etc are about to go up. No problem! ---
**Author:** ![system](https://forum.alta.inc/uploads/default/original/1X/087669c3d7c0a6495087b41d6f385a6771f2231c.png) [@system](https://forum.alta.inc/u/system)\ **Post date:** [June 10, 2026, 2:01am UTC](https://forum.alta.inc/t/ap-firmware-2-2v-released/6316/11 "2026-06-10T02:01:51Z")
This thread has been automatically closed due to inactivity. If you believe you have the same issue, please create a new post describing your issue. Feel free to link to this post for context if desired.