This firmware release expands system visibility and reporting while improving controller reliability and IPv6 behavior. It includes updates to core networking services and refinements to IPv6 handling to support more consistent AP operation.
Update dnsmasq to 2.90.
Improve connection reliability to controller.
Improve compatibility with local controllers on IPv6.
Eliminate redundant IPv6 neighbor solicitations related to hardware acceleration.
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:
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.
After updating AP6 firmware from 2.4a to 2.4b, wireless clients no longer receive IPv4 addresses via DHCP. The AP does not forward DHCP Discover/Request packets to the upstream router. Manually assigning a static IP restores connectivity immediately.
Initiated a manual update to both AP6’s with 2.4b version and have lost all SonOff home automation units and a Ketotec thermostat.
Units are connected but no data flow to/from them.
Is there a way to rollback to 2.4a ?
Update: All units have slowly come back and are fully functional but were “dead” for around 70 minutes !
Update: Wifi units are cycling on & off.
AP6’s shutting off WiFi to all equipment on WiFi (2.4 & 5GHz) at random.
Ticket raised so hoping that a rollback is possible asap.
So…. I think the dnsmasq update maybe got borked? (Of course, my network is a playground right now, so I could be troubleshooting my own problem- Much to the rage of my wife). It looks like as soon as I swallowed the update, all my APs started running DHCP.
I’ve got this in the logs:
Feb 23 19:45:22 192.168.1.44 dnsmasq-dhcp[3988]: DHCPDISCOVER(lo) 16:9b:5e:6b:e2:21
Feb 23 19:45:22 192.168.1.44 dnsmasq-dhcp[3988]: DHCPOFFER(lo) 10.188.50.217 16:9b:5e:6b:e2:21
Feb 23 19:45:22 192.168.1.44 dnsmasq-dhcp[3988]: ARP-cache injection failed: Invalid argument
Feb 23 19:45:22 192.168.1.44 dnsmasq-dhcp[3988]: DHCPREQUEST(lo) 192.168.1.103 16:9b:5e:6b:e2:21
Feb 23 19:45:22 192.168.1.44 dnsmasq-dhcp[3988]: DHCPNAK(lo) 192.168.1.103 16:9b:5e:6b:e2:21 wrong server-ID
DHCP offers for 10.188.x.x will only be emitted if your normal DHCP server appears to be ignoring DHCP requests (as detected by the AP). Do you have any hostname filters in your configuration, and/or are you running PiHole, etc?
DHCP server is on Opnsense, which also swallowed a dnsmasq update. Looking in the logs, it is indeed filtering some hosts from getting the IPs they are requesting.
The way I read the DHCP backup was that it was for the network gear itself, not that it would provide DHCP for all clients. That’s good to know.
My Son lodged the ticket with your team the number of which I do not know.
I can say that your team has rolled the version back to 2.4a and all my SonOff units and other WiFi enabled camera’s, thermostats, temperature sensors and echoshow’s totalling 45 devices are now online and stable again.
Many thanks to your team for rescuing my system.
Interesting. I’ll need to know that ticket so we can make sure whatever issue caused your problems is resolved before we release the next firmware, but my guess is that it’s the same issue @Tomas saw, which issue has been resolved in an internal firmware release already.
I don’t know if it was the update or my troubleshooting, but it seems like either my AP or my PoE injector just died.
I just ran the update. During the update, the AP LED went out several times and then stayed on continuously. After the AP LED had been on continuously for a while and my phone still couldn’t connect to the Wi-Fi I checked and couldn’t find my Wi-Fi among the visible SSIDs.
I then unplugged the cable from the AP (it gets its power from a Tp-Link POE160S PoE injector) and after plugging it back in, the PoE injector LED was only flashing green (from the Tp-Link manual: “Flashing Green: Abnormal PoE power supply”).
Before I pulled out the cable, the PoE injector was constantly showing a green light (from the Tp-Link manual: “Steady Green: Power on, normal PoE power supply”).
I replaced the POE injector but the AP6 Pro still won’t start up, the LED isn’t lit. I tried starting it up with “Power-On-Reset” but the result is the same. I think it’s dead…
What should I do in this case? I purchased the AP in February 2025.
Do you have any custom terminated cables anywhere in the path from the switch or Route10? Or, any bad cables? If so, an unfortunate coincidence of cable issue may be the case? Otherwise no ideas except for what you already attempted.
Random disconnects - usually 1 per mid-morning. I thought this was an ISP issue, but checking the connection logs I haven’t seen any disconnects and the uptime has not reset. I get kicked off my work VPN and it lasts at least 1-3 minutes and then resumes back to normal.
Slow Wi-Fi speeds. I have a 120/40 Mbps connection and previously was able to saturate that connection easily via Wi-Fi but speed test wirelessly are now ~25 Mbps up and down. Wired speeds are normal. AP6-PRO connected to Route 10 which reports at 1000 Mbps link speed. All wireless devices are exhibiting this speed almost like a speed limit is in place but there are none that I set, occurs across different Wi-Fi networks, and nothing in this setup has changed.
None of this was happening prior so I’m thinking it must be relating to the update.