It boils down to a bug in the isc-dhcp-client. It doesn't correctly react to time synchronization events and therefore simply breaks in situations where time jumps "backwards" and the lease time in the network is relatively short.
In my case I "fixed" the bug by removing the package isc-dhcp-client. The NetworkManager now uses its internal dhcp client which doesn't support as much features but at least works in my situations without breaking the network connection.
I think I found the culprit: /bugs.isc. org/Public/ Bug/Display. html?id= 45540
https:/
It boils down to a bug in the isc-dhcp-client. It doesn't correctly react to time synchronization events and therefore simply breaks in situations where time jumps "backwards" and the lease time in the network is relatively short.
In my case I "fixed" the bug by removing the package isc-dhcp-client. The NetworkManager now uses its internal dhcp client which doesn't support as much features but at least works in my situations without breaking the network connection.