On Thu, 4 Feb 2021 22:16:12 +0100
basti wrote:
> As I can see now timedatectl seems *not*
> using the NTP Server provide by DHCP. I have configure a NTP server
> in LAN.
Are you using NetworkManager? Out of the box, it does not pick up the
relevant information from the dhcp client. There are sc
On Fri, 5 Feb 2021 12:13:43 -0700
Charles Curley wrote:
> > For lack of time, I resorted to use systemd-timesyncd but apparently
> > you need to configure NM to handle NTP server by way of a hook or
> > tweaking the profile for the desired connection.
>
> So I conjecture. I am working on a scr
Darac Marjal wrote:
> And, for the D part in DHCP, the ArchWiki has as recipe for how to do
> this automatically using NetworkManager's dispatcher scripts. OP hasn't
> said what DHCP client they use, so some adaption might be required.
I am afraid I missed that part. Indeed it seems to be the bug
On Fri, 5 Feb 2021 19:50:49 +0100
john doe wrote:
> >
> > Is NetworkManager causing problems here?
> >
>
> For lack of time, I resorted to use systemd-timesyncd but apparently
> you need to configure NM to handle NTP server by way of a hook or
> tweaking the profile for the desired connection.
On Fri, 5 Feb 2021 08:33:30 -0700
Charles Curley wrote:
> I have two other machines running the systemd time client. Both are
> Bullseye. Both show that they are using the local NTP server. Neither
> is running NetworkManager.
>
> Is NetworkManager causing problems here?
Apparently, yes. And ap
On 2/5/2021 4:33 PM, Charles Curley wrote:
On Fri, 5 Feb 2021 07:22:27 -0700
Charles Curley wrote:
On Fri, 5 Feb 2021 07:24:05 +0100
john doe wrote:
It does work fine for me, is the lease showing the ntp server?
I don't know. The computer in question is a laptop and using wifi and
Network
On Fri, 5 Feb 2021 07:22:27 -0700
Charles Curley wrote:
> On Fri, 5 Feb 2021 07:24:05 +0100
> john doe wrote:
>
> > It does work fine for me, is the lease showing the ntp server?
>
> I don't know. The computer in question is a laptop and using wifi and
> NetworkManager. There is no dhcp.leas
On Fri, 5 Feb 2021 07:24:05 +0100
john doe wrote:
> It does work fine for me, is the lease showing the ntp server?
I don't know. The computer in question is a laptop and using wifi and
NetworkManager. There is no dhcp.leases file for the wifi nic. There is
an old one for the wired nic, which sho
On Fri, 05 Feb 2021 09:22:55 +0100
deloptes wrote:
> set your NTP IP in /etc/systemd/timesyncd.conf
> and restart
>
> systemctl restart systemd-timesyncd
I thought the whole point of specifying the time server via DHCP was to
avoid editing /etc/systemd/timesyncd.conf.
--
Does anybody
On 05/02/2021 08:22, deloptes wrote:
> basti wrote:
>
>> Hello,
>> I use a up to date debian. As I can see now timedatectl seems *not*
>> using the NTP Server provide by DHCP. I have configure a NTP server in
>> LAN.
>>
>> timedatectl timesync-status
>>Server: 167.86.86.192 (0.debian.poo
basti wrote:
> Hello,
> I use a up to date debian. As I can see now timedatectl seems *not*
> using the NTP Server provide by DHCP. I have configure a NTP server in
> LAN.
>
> timedatectl timesync-status
>Server: 167.86.86.192 (0.debian.pool.ntp.org)
> Poll interval: 1min 4s (min: 32s;
OK thanks John,
I don't know what was wrong here. I move the option from global to the
subnet and backup to global and for now it works on Debian Buster.
On 05.02.21 07:24, john doe wrote:
On 2/5/2021 4:10 AM, Charles Curley wrote:
On Thu, 4 Feb 2021 22:16:12 +0100
basti wrote:
I use a u
On 2/5/2021 4:10 AM, Charles Curley wrote:
On Thu, 4 Feb 2021 22:16:12 +0100
basti wrote:
I use a up to date debian. As I can see now timedatectl seems *not*
using the NTP Server provide by DHCP. I have configure a NTP server
in LAN.
timedatectl timesync-status
Server: 167.86.86.192
On Thu, 4 Feb 2021 22:16:12 +0100
basti wrote:
> I use a up to date debian. As I can see now timedatectl seems *not*
> using the NTP Server provide by DHCP. I have configure a NTP server
> in LAN.
>
> timedatectl timesync-status
>Server: 167.86.86.192 (0.debian.pool.ntp.org)
> Poll int
basti wrote:
> I use a up to date debian.
Stable? Testing? Unstable?
> As I can see now timedatectl seems *not*
> using the NTP Server provide by DHCP. I have configure a NTP server in LAN.
>
Assuming you are sending option 42, the usual way to get that
adopted is to tell dhclient.conf:
re
Hello,
I use a up to date debian. As I can see now timedatectl seems *not*
using the NTP Server provide by DHCP. I have configure a NTP server in LAN.
timedatectl timesync-status
Server: 167.86.86.192 (0.debian.pool.ntp.org)
Poll interval: 1min 4s (min: 32s; max 34min 8s)
Leap: n
16 matches
Mail list logo
