There is strange behaviour with "IP & MAC Binding" feature implementation. When wired client, which ARP and IP is binded to prevent spoofing, goes offline (turned off or due to power outage), and DHCP lease time is over for any wireless client, it can receive that binded wired IP from DHCP, which leads to no internet connectivity for that said wireless client. Simplifying that, I have 192.168.0.100 ip binded for my desktop rig, and when I shut it down, and then enable wifi on the phone, it usually receives that 192.168.0.100 ip address, and there is no internet connection for the phone. It can be easily reproduced under power outage scenarios, when router reboots to work from the backup power source, but there is no more wired client which is powered and running, so first wireless client can receive wired ip address, that is binded (with that short lease times which are set by default on that router).

It can be fixed easily, by applying permanent DHCP leases for wireless clients, which I did.

So my question is, does such behaviour is by design, or there is some issue with implementation of "IP and MAC Binding"?