EAP 783 Crashes when using MLO and new iPhone 16 Pro
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have 4 EAP 783 controlled by a OC200, 3 are powered by a TP Link SX3206HPP v1.20, one is connected via mesh and uses a POE++ injector. They have worked great, except I recently got my first MLO capable WiFi 7 devices in 2 new iPhone 16 Pros.
Whenever the iPhone 16 Pros connect to the EAP 783 with MLO enabled on the wireless network, it crashes. Usually it's an immediate crash, but rarely I can get connected briefly and things work for 30-60 minutes, then another EAP crash. I'm thinking there may be some incompatibility or firmware bug and am hoping to find assistance or beta firmware.
I was also suspicous of MLO just using more power and it being an issue, but the SX3206HPP can provide 60W per port and upto 200W total. The switch reports 141W unused free power. So I'm at a loss outside of a bad interaction with the new iPhone's WiFi 7 MLO support and a firmware bug.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Sounds like there's a private beta but it's not super stable. It fixes the MLO issue but has other issues.
- Copy Link
- Report Inappropriate Content
@Vincent-TP is there an ETA for a resolution?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Any update when this is going live? Early Christmas gift perhaps? Original note said end of November so curious if other changes getting included as well.
- Copy Link
- Report Inappropriate Content
How's that update going, TP-Link?
- Copy Link
- Report Inappropriate Content
New firmware is posted.
- Copy Link
- Report Inappropriate Content
Is this the same as the beta firmware that's been out, or any changes since that?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 3250
Replies: 28
Voters 0
No one has voted for it yet.