As far as 'blocked devices' getting an IP Address, I can't really say? Logic says they should not under any circumstances? That doesn't mean what the router might do? I 'googled' if a blocked MAC address can get an IP Address and can NOT find anything about that, not a single link?

Now if you are using TIME to block, it is possible it is on the LAN and when the time hits, it might be logging it blocked it?

As for seeing multiple entries of getting IP Addresses, I see it SPECIFICALLY with my wife's PC that is at 192.168.1.40 (I too assign the PC specific IP Address so I know I can always get to this even if 'sharing' doesn't work well (which does happen). For instance:

[Time synchronized with NTP server] Friday, May 04,2018 19:09:46
[Internet connected] IP address: 67.8.xx.xx, Friday, May 04,2018 19:09:45
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 18:57:50
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 18:57:38
[DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:5B, Friday, May 04,2018 18:30:51
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 17:45:15
[Time synchronized with NTP server] Friday, May 04,2018 17:43:40
[Internet connected] IP address: 67.8.xx.xx, Friday, May 04,2018 17:43:39

See different time, and one 18 seconds apart...

[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 13:34:28
[Time synchronized with NTP server] Friday, May 04,2018 13:24:23
[Internet connected] IP address: 67.8.xx.xx, Friday, May 04,2018 13:24:22
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 12:48:15
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 12:10:51
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 12:10:38
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 12:00:52
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Friday, May 04,2018 12:00:31
[Time synchronized with NTP server] Friday, May 04,2018 11:58:25
[Internet connected] IP address: 67.8.xx.xx, Friday, May 04,2018 11:58:24

Some more...

I for the LIFE of me can NOT resolve why this happens. I checked when she wakes up here computer (which goes to sleep, and if sleeping long enough I know the USB wireless adapter seems to disconnect as when she does wake up the computer sometimes the Wireless Connectoid on the Systray shows no connection momentarily) and NEVER correlate those actions to log entries? I don't think it is Windows causing this, and if you run IPCONFIG /ALL you should see LEASE times of 24 hours:

Lease Obtained. . . . . . . . . . : Sunday, May 6, 2018 3:27:23 PM
Lease Expires . . . . . . . . . . : Monday, May 7, 2018 3:27:23 PM

The above is for MY machine, I was out and came back in and woke it up. So it got a NEW LEASE it seems. This PC is hard wired, and it does correlate the time of the DHCP lease to the LOG:

[DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:5B, Sunday, May 06,2018 15:27:23

I sort of have a feeling that for WIRELESS it is different? Possibly it checks periodically to see if it is still connected OR it sense it has lost the IP Address and reestablishes it? Still, I can not reconcile all the DHCP entries in the log to any PC operations.

Secondly, I 'believe' that LOGGING is a very WEAK point in NG's routers. You can't log everything easily. It is possible some logging (like DoS attacks) are completely wrong or incomplete (I've seen ones that clearly have missing letters in what was logged). I'm sort of thinking in this case it isn't a DHCP request/assignment, but the Wireless device waking up and asking the router if it still has the same IP Address and the router logged that as a DHCP request. That goes back to the method old DIALUP and even Cable systems control the DHCP given out. They have a limited pool, and in DialUp of course once you hang up your IP Address is put back into the available pool. Cable, different story, always on unless you power down the modem. Still, Cable uses a server with a limited number of IP Addresses assigned to an area. Let's say 254 addresses. However it is NOT cost effective for them to have a node for only 254 customers. They know not everyone uses the computer at the same time, so for arguements sake lets say they assign 300 users to that node. Now when 254 are in use and no one has disconnected or let the LEASE (24 to 36 hours are normal with a RENEW usually done in 1/2 that time) expire they will look at the LAST TIME USE, and the oldest time last used will be dropped and given that IP Addresss. However, this IS rare. When it does happen the ISP knows it needs to split the node and create a new one.

So what does all this have to do with anything? The PC doesn't really know for sure where the DHCP server is? Under whose control either, so when it comes back to 'life' it will check if it is still its IP Address probably. If it were given away it would get a new one. If you are using a declared IP Address (Static) then as LONG as it is NOT within the POOL of available DHCP IP Addresses (you can set the size of the pool in the router and the highest number should be below the declares fixed IP address or conversely, the lowest number above the last fixed IP Address you used. Other wise you could have conflicts on the address and someone could lose Internet connections.

Forum Discussion

Hello i wanna join in netgear xr1000 beta, how can i do it?