iPhone 7 stops transmitting

  • 1
  • Question
  • Updated 1 month ago
I am having issues with the iPhone 7 and 7+. I believe the issue is entirely client side, but I'm still the one needing to fix it. We have an 802.1x certifcate based  SSID, and periodically throughout the day iPhone 7's will stop working. The iPhone will show connected, but it not longer shows up in ZoneDirector. Obviously data stops transmitting as well. The only happens after it has been idle for a few hours with user activity. 

This only happens on the new iPhone 7's and 7+'s. I have not been able to recreate it on any other IOS device, even with the same version. As I do not have one to test with I don't believe I would have much luck trying to submit a ticket. Any ideas?
Photo of Steven Veron

Steven Veron

  • 20 Posts
  • 4 Reply Likes

Posted 2 years ago

  • 1
Photo of Mitchell Clouatre

Mitchell Clouatre

  • 1 Post
  • 0 Reply Likes
Same issue here. Seems to work for some time if you wipe the phones network settings but, now real fix. The issue returns with some time.
Photo of Steven Veron

Steven Veron

  • 20 Posts
  • 4 Reply Likes
What type of security and authentication are you doing? I'm running 802.1x, trying to figure out if it's specific to that. 
Photo of Peng Bo

Peng Bo

  • 1 Post
  • 0 Reply Likes
Same here for 802.1x WLAN, as Steven said iPhone 7 will experience connection issue sometimes showing connected. Is there compatibility issue between iPhone 7 and ruckus devices? Currently we are using ZD3000 with r300,zf7363 and zf7372 with firmware version 9.9.1.
Photo of Greg White

Greg White

  • 24 Posts
  • 2 Reply Likes
We run a SZ-124 and we see constant authentications coming in as a result of iphones disassociating from WiFi while in sleep mode, then waking up and doing a full new association+auth. Could be related.  Theres a lot of buzz in online forums about iphones disconnecting from some consumer grade WiFi gear and staying connected to others.  My gut tells me this could have something to do with the way that 802.11 power management is implemented on different vendors.
Photo of Greg White

Greg White

  • 24 Posts
  • 2 Reply Likes
As a follow up to this statement, we eventually discovered that our specific issue was related to NAT behaviour.  We run a Cisco ASR with a NAT pool for SNATing the clients out to the internet.  We ran into some other issues on the ASR relating to address+port exhaustion which lead to a code upgrade.  What was noticed after the code upgrade was the NAT behavior changed, specifically with how it assigned outer source ports.  Before the code upgrade, all source ports were randomized on the outside interface.  After the code upgrade, all source ports were maintained unless there was a conflict, then a randomized source port was used for outgoing sessions.  I believe this change in behaviour made it easier for the iPhones to maintain data paths to messaging services.  Suddenly they all stayed connected while the screens were off, the difference was night and day after the NAT code upgrade.