I noticed that when setting a reboot schedule that some wired devices become uncontactable after the reboot occurs. The device does not appear in the TP-Link router administration, and pings to the reserved IP address come back as `no route to host`.

The workaround right now is to reboot the client device (far from optimal) or to physically unplug and plug back in the ethernet connector.

Given that I bought this router because of its many ethernet ports, I find this quite problematic.

Is this the correct place to lodge a bug report?