Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Smoblikat

macrumors newbie
Original poster
Mar 15, 2019
5
0
Hello everyone, I am the network administrator for a primarily apple organization and I am having an extremely strange issue. I posted this on another forum, but I figured its time to hop on an apple specific forum to get some help, this is a copy/paste from my other post:

I have a guest network, very basic setup, it has its own VLAN (we can call it 5) and I am using a virtual interface on my firewall as the gateway for the internet (same setup as my printer subnet from my other routing thread). I am assigning DHCP from my server subnet, with an IP helper on the firewall interface, and there is just one policy on the FW that points the guest interface to the WAN interface, nothing special whatsoever, no communication with my other subnets. DHCP is handing out 8.8.8.8 as the only DNS server, and all clients can receive the appropriate IP address on the subnet. All of my non apple clients can get to the internet beautifully, windows devices, android devices, chrome/pixel devices, and even my personal macbook that runs OSX 10.6, the issue I am having is that none of the iPhones/iPads and modern apple computers can actually browse the internet. I can verify that they are at least able to communicate out to the WAN and onto the internet by browsing directly to an IP rather than DNS name, but most websites simply return some answer about not allowing traffic directly to an IP address, but the fact that I can get to the website to see that answer pretty much proves that the connection is being made. Obviously this seems like some sort of DNS issue, but its ONLY on modern apple devices, so im wondering if there are any other apple admins out there that know of some trick to make these devices play nicely? Im going to play around with some stuff now, but I wanted to get the question out there first to see if there is any low hanging fruit im missing. Im borrowing someones iphone to test with now, ive done all the things as far as forgetting the network, resetting network settings etc..

Is there anything special that newer apple stuff does as far as name resolution goes? Also, since posting this thread on another forum, ive noticed that some of the macbooks dont pick up DHCP either, while some do. This issue affects certain devices differently than others, and I have no clue why. I just freshly imaged a macbook, and it doesnt pull DHCP, but with a manual IP config I can ping the other hosts on the network, yet not the actual gateway of the guest network. This issue ONLY affects devices on wifi, using a thunderbolt to ethernet adapter into a switchport configured for teh guest VLAN immediately lets me pull DHCP and get to the internet without issues.

Any help would be greatly appreciated
 

sevoneone

macrumors 6502a
May 16, 2010
957
1,302
What access points are you using? We had a similar issue with UniFi APs at one of our offices awhile back. Just about any Apple device made between 2015 and 2017 would connect fine but timeout on DHCP. Rebooting the APs solved the problem for anywhere from two days to a week before the same problem started coming back. I was able to find limited information about it Being a known issue with a specific WiFi chipset Apple used in some devices and the then current UniFi firmware. Eventually we rolled back the firmware on the APs and the problem went away. That was nearly a year ago though and we’ve since updated the firmware on our APs and are keeping them on the most recent release again With no problems.
 
  • Like
Reactions: Smoblikat

Smoblikat

macrumors newbie
Original poster
Mar 15, 2019
5
0
What access points are you using? We had a similar issue with UniFi APs at one of our offices awhile back. Just about any Apple device made between 2015 and 2017 would connect fine but timeout on DHCP. Rebooting the APs solved the problem for anywhere from two days to a week before the same problem started coming back. I was able to find limited information about it Being a known issue with a specific WiFi chipset Apple used in some devices and the then current UniFi firmware. Eventually we rolled back the firmware on the APs and the problem went away. That was nearly a year ago though and we’ve since updated the firmware on our APs and are keeping them on the most recent release again With no problems.

Amazing, I was almost going to roll back the firmware on my AP's (Aruba 315) due to another site (thats working fine) having an identical config, but the AP's there are using V6.5, while my problem site is on V8.3. I decided against it as I was about to do a whole wireless upgrade on the working site to AP 505's, with firmware 8.6, and my third site is using AP 315's with V8.5.0.10 (also upgraded this weekend). I wanted to wait to get the exact firmware version from my third site so I could match the firmware between both of my sites that are using AP 315's. Im going to try a firmware upgrade tomorrow on my problem site to 8.5.0.10 and see if that solves the issue, my current workaround is having the IAP master handle DHCP for the Guest VLAN, which does seem to be working, but I dont specifically know why having DHCP on the AP itself lets the apples connect, while having it on my actual server/Gateway port on the firewall wont.

Thanks for the input, I definitely appreciate it.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.