Apple Wireless Devices Wont Connect with Static DHCP Mappings
-
Hey All,
I'm having an issue with some static DHCP mappings. I am adding all my devices to the router using static DHCP mapping as i would like to have fine grain control over the ip addresses they use.
Here is the network breakdown of my fresh 2.3.3 install…
10.10.1.1/24 -- DHCP pool 10.10.1.150 -- 10.10.1.200... i am using LinkAgg (LACP) from my pfsense box to a HP 1920 16 port switch and have other devices connected directly to that or to two other managed switches (also connected to the HP 1920 with LinkAgg LACP).
I was inputting all the devices and their MAC addresses and everything was going along fine until i tried to test a iPad. At first the iPad connected to the router (through a Ubiquity AC-AP-Pro connected to the HP 1920 switch) and pulled an ip address that was in the DHCP Pool i had allotted. I entered the static map address of 10.10.1.85 and put all the proper info in to setup the mapping. I then removed the DHCP Lease and tested the iPad. To run the test i "forgot" the network and reconnected as if it was the first time the iPad was connecting and i received an ip address of 169.254.6.92. I know this is the loopback address and was curious as to why it is not getting the proper static mapped IP.
I thought that it might be an error in the order of operation that i added the device and so i removed the static map and let the iPad reconnect to the router via DHCP. I then tried to change the DHCP lease on the lease's page and add the reservation from the "+" icon on the right. This also resulted in two "lease's" showing up, with one for the reservation i added (.85) and the other with the ip address it had pulled automatically from DHCP. I removed the lease once more and reset the iPad. When it booted back up it had the same 169.254.6.92 address...
I am hoping i'm missing something silly and would appreciate any help with this issue. I also am aware that the pfsense machine is connected to a switch that has an access point connected to it and that all my wireless devices are connected through this unit... so there may be some issues down the line...
I did try to connect an android device with a reservation and it also would not receive the ip address that was reserved... And lastly i tried an apple TV that would not take the reservation via WiFi, but did over ethernet.
So i'm thinking there is something wrong with my Access point configuration. Again, wireless devices can pull DHCP no problem, but the reservations are not pushing.
Thank you for your time and effort!
-
So im stupid… It looks like i was filling in all the "Client Identifier" info with a description of the device... You know... so i could identify it... So stupid!
I also found that i had broken the DHCP service with misstep and was wondering why so many of my devices were connecting and reconnecting and when there was issues with the IPv6 DHCP Service...
On that note make sure to look at the RFC 4361 if you are interested in what the Client Identifier is and what it is used for!
Thank you to anyone who was out there thinking about a possible solution to my problem...
Sorry for being a big big NOOB! :P :) :P
-
an ip address of 169.254.6.92. I know this is the loopback address
Actually, it's not a loopback address. The IPv4 loopback addresses are 127.0.0.0/8. The 169.254.0.0/16 addresses are link-local, which provide an IPv4 address when a DHCP server is not available and an address has not been manually configured.
-
Thank you for clarifying that for me! Yes the loop back addresses are something different than link locale addresses. Thank you for your response and the tutelage!!
