I have several 2,4Ghz AP (SXT or other routerboard units) all connected via a vlan network to one dhcp server.
Several people are allowed to use this network to go online.
Tablet’s, PC’s (laptops) and smartphones (windows/androids) all connect and get an IP with default gateway etc. and can browse the internet.
Except for Apple devices. Sometimes an apple device works but 80% of the case we seem not to be able to find why they won’t…
The are associated to the AP, good signals even, better sometimes than a android phone beside it, but no IP exchange.
When I try to connect Apple device to local Wifi (MT router) that has local dhcp server (just my office wifi router) it connects and gets an IP inmediately.
If I now compare my local wifi and the remote 2,4Ghz AP’s (I call them hotspot, but they are just simple AP’s in a bridge network where an dhcp server is found at distant and also the border gateway will be found at distance.) I see no real differences apart from the SSID and the fact that the local AP has its local dhcp-server and is routed to the internet where the bridge AP’s are having a vlan interconnecting them towards a central dhcp-server and a remote internet gateway.
But why is this happening ONLY with Apple devices? All other brands have no issues…
Although I would not know what if would differ, I tried it anyway… it doesn’t help.
DHCP-server status stays now ‘offered’ for a some minute or so until the request disappears to be renewed again after a sec.
In the original setting; “Authoritative: after 2s delay” the status went from ‘offered’ to ‘bound’ to ‘waiting’ and back to ‘offered’ again.
There are any differences between the ios devices that actually connect and those who doesn’t?
IOS devices use some sort of algorithm to confirm a lease faster, maybe is related to the VLAN setup, so capturing the traffic from device showing this issue (esp. ARP) can lead you to a clue…
Well, don’t know. On the moment have no other ios devices at hand that can connect.
But I also suspect its the vlan having something to do with it. But I’m not going to change my network because some ios devices won’t get an IP. It works fine for several hundreds of other devices…
Not sure wether it is relevant. We have found some Apple devices to be troublesome on 80211a/b when non Apple devices are already connected to the same AP. Turned out to be the security authentication type. It seems if an AP is allowed to use WPA2 aes and tkip problems arise. If the AP is forced to only use WPA2 aes then the problems go away. The only other oddity we found with some apple devices is they dont like a Punctuation mark like _ in the SSID.
Its an open AP.
We just filter clients by mac. authentication… so no encryption takes place…
Just this morning again, two androids connected without problems, one Iphone connects without problem, one SXT 2,4G connects without problem, but two Ipad can’t connect. They see the network but connection is rejected with the message “check your network provider” (haha, that’s me!)
Any ideas..?
It ONLY happens with Apple devices. We’ve had people with Iphones, Ipads and a MacBook that were not allowed.
But others, even with the same kind of devices have no issue… very, very weird.
Maybe differences in IOS version are causing the failings? check DNS requests when such a device doesn’t connect. I also found that reverse DNS for the router IP should work (insert an static entry in addition to the router FQDN)
i had a similar problem where I would have windows and android devices not getting a dhcp address. 1100 ahx2 router and engenius access points. I found that if i went into the settings for each apple device under TCP/ip there is client ID or dhcp Client ID.I copied the mac address and put it into their. They then got an IP straight away. may be worth trying on one of the devices that fails.
I am pretty sure it won’t solve your issue, but I think you should try to avoid using networks like 20.20.20.0/24 for your local network, unless you have that range assignet to you by IANA.
If you use a legal IP for your local network and happens that you have to access a public server and the DNS returns an IP in your local network, you are screwed up.
hmm, that’s new to me. I thought 20.20.20.0/24 like 10.10.10.0/24 was for private use too. I used it to distinguish from some other part of my networks. But ok, wikipedia is clear.
Maybe the apple internal network or their servers work on 20.20.20.0/?? range and that is what gives the issue. I can give it a try. Is some work but ok, maybe we are lucky…
Finally changed the 20.20.20.0/24 into 192.168.20.0/24 but to no relief. SOME apple devices (so still not all, some work flawless) are not able to pick up an IP from the dhcp-server…
it is happening because apple devices won’t renew IP address if went to sleep so they keep the address while DHCP may give it to other device. Actually the device doesn’t act like it need an address to be assigned. This may be solved by MKT but I am not sure. I didn’t read all the posts but I think this is the problem. I’ve heard about this problem few days on MUM.
I know it is old topic, but after many hours of struggle with 2 MacBook Pro not being able to get IP, complaining about IP already used by another device (when it’s not) I was able to solve the problem by changing protocol-mode from rstp to stp:
/interface bridge> print
Flags: X - disabled, R - running
0 R name=“bridge1” mtu=1500 actual-mtu=1500 l2mtu=1526 arp=enabled
arp-timeout=auto mac-address=XX:XX:XX:XX:XX:XX protocol-mode=stp
priority=0x8000 auto-mac=no admin-mac=XX:XX:XX:XX:XX:XX
max-message-age=20s forward-delay=15s transmit-hold-count=6
ageing-time=5m