Hello!
I have a single IAP-215 is setup as a standalone AP with a DHCP server (192.168.22.1 pool).
I am have a client that is behaving in a silly way (client issue, not AP issue) where it sometimes does not send out a DHCP Discover.
I have seen in the AP logs that the client successfully authenticates and associates and the client indicates a successful connection. The client does show up in the AP clients table with an IP address of 192.168.3.1.
I am assuming that the above is just a default IP address that is entered if the DHCP Discover isn't heard at all. Is this correct?
Why would we not see an IP address of 0.0.0.0 instead?
We have also seen one client switch from a valid IP address to a 192.168.6.1 address while 192.168.3.1 is in the client table.
One of the ports on the system the AP is connected to is 192.168.3.1 so we ended up with an IP address conflict. If the 192.168.3.1 is a default, is there any way we can change the default ip address assignment?
What about when a lease time runs out? Is the client removed from the table or does it get a new dummy IP address?
The first solution is that the vendor needs to fix their client to properly send out a DHCP Discover, but I am trying to understand how the AP is expected to behave in this situation so we can anticipate possible other IP address conflicts.
Regards,
zummarius