Re: [systemd-devel] Bouncing interface once chrony is synced

2017-07-10 Thread Mantas Mikulėnas
On Mon, Jul 10, 2017 at 7:03 PM, Julian Andres Klode wrote: > On Wed, Jul 05, 2017 at 10:29:21AM -0500, Ian Pilcher wrote: > > I am using CentOS 7 (systemd 219) on a Banana Pi as my residential > > firewall/gateway. The Banana Pi does not have a persistent clock, so > > it has

Re: [systemd-devel] Bouncing interface once chrony is synced

2017-07-10 Thread Ian Pilcher
On 07/10/2017 03:43 AM, Lennart Poettering wrote: If your DHCP client implementation gets confused by the wallclock not being steady then this appears to be a bug in the implementation. Given that there are so many DHCP clients to choose from, maybe use a different one? Oh, it's definitely a

Re: [systemd-devel] Bouncing interface once chrony is synced

2017-07-10 Thread Julian Andres Klode
On Wed, Jul 05, 2017 at 10:29:21AM -0500, Ian Pilcher wrote: > I am using CentOS 7 (systemd 219) on a Banana Pi as my residential > firewall/gateway. The Banana Pi does not have a persistent clock, so > it has no idea what the time is until it is able to sync via NTP. Thus, > the initial DHCP

Re: [systemd-devel] Bouncing interface once chrony is synced

2017-07-10 Thread Lennart Poettering
On Wed, 05.07.17 10:29, Ian Pilcher (arequip...@gmail.com) wrote: > I am using CentOS 7 (systemd 219) on a Banana Pi as my residential > firewall/gateway. The Banana Pi does not have a persistent clock, so > it has no idea what the time is until it is able to sync via NTP. Thus, > the initial

Re: [systemd-devel] Bouncing interface once chrony is synced

2017-07-05 Thread Reindl Harald
Am 05.07.2017 um 17:29 schrieb Ian Pilcher: I am using CentOS 7 (systemd 219) on a Banana Pi as my residential firewall/gateway. The Banana Pi does not have a persistent clock, so it has no idea what the time is until it is able to sync via NTP. Thus, the initial DHCP leases that the BPi

[systemd-devel] Bouncing interface once chrony is synced

2017-07-05 Thread Ian Pilcher
I am using CentOS 7 (systemd 219) on a Banana Pi as my residential firewall/gateway. The Banana Pi does not have a persistent clock, so it has no idea what the time is until it is able to sync via NTP. Thus, the initial DHCP leases that the BPi receives have incorrect expiration/ renewal times