Entries in a PN Hub2 'router'

[#1]

Below is a screen capture of consecutive (unlfiltered) log file entries

Obviously there's something issuing a DHCP request. But the Hub2 is being a bit coy about saying anthing more.

Perhaps a little more detail/info in the logging miay provide enlightenment.

One thing I can say is that it isn't the PC I'm posting from, because the entries continue when that device is powered down.

Obviously I could power down every device on my local LAN in turn and see whether that provides insight. But a bit more info from the Hub2 might be better.

This is on a totally wired LAN.

[#2]

@greygit1 

What happens if you turn wireless off completely?

[#3]

This is how it is and has been since well before my orginal question.

[#4]

@greygit1 looking at those times, I would guess that the lease time is set to 1 hour and there are 4 devices connected and renewing their leases at 30 min intervals.

[#5]

That is my current understanding. I had to alter DHCP lease times to test what is happening. And read some DHCP-related documentation. And look at the log files and do some inferring.

The hub2 is coy in revealing which devices, and when.

It appears that the hub2 only reports the device when (a) a lease is issued (b) a device has reliquished the lease. Extensions and lease renewals just appear as "a request" with no further logging.

Whether this is by design, or a lack of specification, or assumption - I don't know. And this is only IPv4...

[#6]

@MisterW

Thought you might be interested in a event log extract for a device joining a Hub Two LAN, DHCP lease time is 24 hours

08:29:03, 05 Mar. ARP [add] br0(eth1) 192.168.10.247 08:00:27:fc:c6:0b
08:28:55, 05 Mar. DHCP device Connected: 192.168.10.247, 08:00:27:fc:c6:0b, ntrb53-wine
08:28:55, 05 Mar. DHCP lease issued 192.168.10.247 to 08:00:27:fc:c6:0b ntrb53-wine, lease duration is 86400 seconds
08:28:55, 05 Mar. LAN [ADD] ARP 192.168.10.247 with 08:00:27:fc:c6:0b from br0(eth1)
08:28:55, 05 Mar. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
08:28:54, 05 Mar. Receive a DHCP request

From what I see of this Hub once it has issued a IP Address to a device it (the device) will always use the same one, unless the device is removed from the DHCP list via the GUI.

[#7]

@Dan_the_Van thanks for that.

From what I see of this Hub once it has issued a IP Address to a device it (the device) will always use the same one, unless the device is removed from the DHCP list via the GUI.

I think that's true of most routers, they all use the same dhcp code to a large extent. Effectively once its seen a MAC address and issued an IP to it, its retained as a preferred address for that MAC.

Don't forget though, that a device will/should attempt to renew its lease once half the lease time has expired. What does your log show in that case ? does it show the same level of detail or just the 'receive dhcp request' as in @greygit1 s log

Although I have a Hub 2 , its not in use at the moment. Looking at the logs for my router which is running Openwrt , a DHCP request where no current lease exists reports a DHCPDISCOVER and a DHCPOFFER followed by a DHCPREQUEST and DHCPACK whereas a request to renew a lease just has the request and ACK , see examples below

Sat Mar  2 14:39:31 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 64:dd:e9:55:1f:af
Sat Mar  2 14:39:31 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.5.253 64:dd:e9:55:1f:af
Sat Mar  2 14:39:31 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.5.253 64:dd:e9:55:1f:af
Sat Mar  2 14:39:31 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.5.253 64:dd:e9:55:1f:af M2103K19G

Sat Mar  2 14:40:52 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.5.225 90:f8:2e:b2:48:52
Sat Mar  2 14:40:52 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.5.225 90:f8:2e:b2:48:52

[#8]

@MisterW 

I have many 'receive dhcp request' during the day, not really been bothered with them as (i) I knew why they were happening (ii) they weren't causing an issue.

"a device will/should attempt to renew its lease once half the lease time has expired. What does your log show in that case?"

The problem is associating a 'receive dhcp request' to the device which has made request, as the entries are not in order (I have 25 devices on my LAN) and it's not clear when the DHCP requested would have be serviced in the first place, my Hub system up time is 248 days so the log file is rather extensive, the only reason for reboots for devices would be for system updates.

This has prompted me to do some further investigation.

Dan