HELP, More DHCP Issues

[s814jdh]

The switches I've seen go bad have ports fail or start spewing malformed frames. ARP (convert IP to MAC address) is a layer 3 thing, which consumer switches don't concern themselves with. I'd suspect a device behind the switch, or possibly a switching loop that'd forward frames back into the network.

OK, so let's assume that somehow the switch (or something connected to it) was the root cause for why it was that all of the wireless clients were declining the IPs being suggested by the DHCP server on the 66u. My question then remains, why did changing the SSID change that? Seems like if there were packets interfering with that, those same packets would still be there after the SSID change. For that matter, when I changed the IP subnet to the 192.168.2 network, why didn't that fix the issue?

I am just puzzled over this one. I suppose it could be that there is something with the iOS devices that was the root cause. There were 7 of them (all running iOS 6.0.1) and apple did just release iOS 6.0.2 on 12/18/2012 that "fixes a bug that could impact Wi-Fi." Maybe we should just chalk it up to that being the issue and that somehow changing the SSID was a workaround for whatever Apple thinks they have now fixed with 6.0.2.

Sure wish Apple was a little more clear on what the patches do.

 

[RMerlin]

Apple has been having numerous issues with Wifi since iOS 6.0. I was surprised to read that they are still trying to fix these in 6.0.2. You would think Wifi support on their mobile platform would be something they had stabilized years ago.

 

[s814jdh]

Apple has been having numerous issues with Wifi since iOS 6.0. I was surprised to read that they are still trying to fix these in 6.0.2. You would think Wifi support on their mobile platform would be something they had stabilized years ago.

I like some Apple products even though I think they are overpriced, but don't believe myself to be a fanboy. I don't usually try to defend Apple much, but as to the stability of wi-fi issue it seems reasonable to me that they may be dealing with different versions of wireless chipsets that end up having unique problems. My iPhone 5 is the only one of my iOS devices (iPad 2, iPad 3, iPhone 3GS, iPhone 4) that said it needed the 6.0.2 update. So in this specific case I do cut Apple a little slack on still working on wi-fi connectivity issues.

Like I posted earlier, sure wish Apple didn't assume we were all idiots incapable of understanding what is being fixed with patches. If something like "in some cases iOS was always declining DHCP IP suggestions" was in the release notes as one of the things they had seen, would have made this entire thread unnecessary.

 

[KevTech]

Another endless thread that has been thrown off the main topic.

 

[s814jdh]

Another endless thread that has been thrown off the main topic.

I thought for the most part we did pretty well with this one. Most of it had to do with how DHCP works with clients and theories about why changing the SSID fixed the problem. Still don't think we came down to the root cause, no way I am going to try anything since it is working.

Overall point of the thread now would be that if you see issues with DHCP suggested IPs being declined, try changing the SSID.

 

[Dazman]

I'll have to see if I have the same issue as well.

I shut my router off at night, not the modem, and my iPhones and iPads will fail to connect after 12 hrs or so. Not always but it does happen. I never checked the log before resetting the router and I never tried connecting a non apple device to the 5Ghz band (all apple devices connect to the 5Ghz band), but the 2.4Ghz band was working fine at the time for gaming devices.

 

[Dazman]

Well my iphone wouldn't connect to 5Ghz so I connect to the 2Ghz band and then I was able to connect back to the 5Ghz after I selected Renew lease on the iPhone it came back. Strange.