DanologyUK

Im aware of the DHCP bug so have set my DHCP to start at .100 and statically assigned my devices via the router. Im not sure if this example is a redherring as i have checked and have nothing with a .100+ IP. I had 1 drop out earlier today which resulted in the need to restart the router so i decided to then leave the System information page up so i could monitor when it happened again to help capture the logs and it dropped again. The logs i captured are below [DumaOS] DHCP lease change., Tuesday, February 21, 2023 18:05:26 [DumaOS] DHCP new event., Tuesday, February 21, 2023 18:05:26 [DHCP IP: 192.168.1.16] to MAC address 0a:21:32:53:63:d9, Tuesday, February 21, 2023 18:05:26 [DumaOS] DHCP new lease allocated., Tuesday, February 21, 2023 18:05:23 [DumaOS] DHCP new event., Tuesday, February 21, 2023 18:05:23 [DHCP IP: 192.168.1.16] to MAC address 0a:21:32:53:63:d9, Tuesday, February 21, 2023 18:05:23 [DumaOS] applying qos for zone lan, Tuesday, February 21, 2023 18:03:01 [DumaOS] applying qos for zone wan, Tuesday, February 21, 2023 18:03:01 [DumaOS] applying qos for zone lan, Tuesday, February 21, 2023 18:02:31 [DumaOS] applying qos for zone wan, Tuesday, February 21, 2023 18:02:30 [DumaOS] DHCP lease change., Tuesday, February 21, 2023 17:50:24 [DumaOS] DHCP new event., Tuesday, February 21, 2023 17:50:24 [DHCP IP: 192.168.1.2] to MAC address 90:9d:7d:6f:7e:e9, Tuesday, February 21, 2023 17:50:24 [DumaOS] applying qos for zone lan, Tuesday, February 21, 2023 17:48:56 [DumaOS] applying qos for zone wan, Tuesday, February 21, 2023 17:48:56 [DumaOS] applying qos for zone lan, Tuesday, February 21, 2023 17:48:45 [DumaOS] applying qos for zone wan, Tuesday, February 21, 2023 17:48:45 [DumaOS] applying qos for zone lan, Tuesday, February 21, 2023 17:47:34 I thought id then load up another tab for the router and check the dashboard page to see if it showed i was connected to my WAN or not when the 2nd tab then showed me You are no longer connected to your router. If your router is rebooting then keep this page open as it will automatically reconnect to the router's interface when the reboot is complete. Otherwise please check your connection e.g. you are connected to the correct router. Not sure if any of this will help with your investigations into the DHCP bug?

Excellent, I have my fingers crossed.

It's difficult for me to catch it quick enough to be able to get the logs unfortunately before the router page is not accessible as i know they would of been useful. Yes please for the beta. Im willing to try anything to get rid of this issue.

I am finding myself having to restart my Xr500 on a daily basis because of a loss of network to my devices. I am not losing my WAN connection as i have a Thinkbroadband tracking this. I have set my DHCP to start at .50 already and it's like herding sheep, trying to keep all devices below .50, especially when friends and family visit with their new devices. Its currently just me and my partner in the house and the router has frozen once again and we have lost connectivity. Restarted the router and gone into LAN set up and then clicked the ADD button to check nothing was trying to connect with a >.50 address and everything is below. Nothing is reserved in a >.50 address so i am lost as to what else i should be doing? I am really hoping this new pending update is going to be nice to me and fix this issue and rid me of this annoyance.

Is this update going to fix the DHCP bug? If so, id like to test this beta as I always getting caught out when a new device (such as family member) visits and uses the wifi and i have to manually connect it with a static IP.