| 1 |
Hei Neil, |
| 2 |
|
| 3 |
The NTPServer is in the internet, standard gentoo ntp.conf file: |
| 4 |
|
| 5 |
# Pools for Gentoo users |
| 6 |
server 0.gentoo.pool.ntp.org |
| 7 |
server 1.gentoo.pool.ntp.org |
| 8 |
server 2.gentoo.pool.ntp.org |
| 9 |
server 3.gentoo.pool.ntp.org |
| 10 |
|
| 11 |
I am using systemd-networkd, regarding the gentoo systemd network guide: |
| 12 |
https://wiki.gentoo.org/wiki/Systemd#systemd-networkd |
| 13 |
|
| 14 |
/etc/systemd/network/50-dhcp.network looks like this: |
| 15 |
|
| 16 |
[Match] |
| 17 |
Name=en* |
| 18 |
|
| 19 |
[Network] |
| 20 |
DHCP=yes |
| 21 |
IPv6PrivacyExtensions=true |
| 22 |
|
| 23 |
[DHCP] |
| 24 |
UseDNS=false |
| 25 |
|
| 26 |
/etc/systemd/resolved.conf looks like this: |
| 27 |
|
| 28 |
[Resolve] |
| 29 |
DNS=1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001 |
| 30 |
|
| 31 |
|
| 32 |
ifconfig -a: |
| 33 |
|
| 34 |
enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 |
| 35 |
ether 00:01:2e:80:8c:2d txqueuelen 1000 (Ethernet) |
| 36 |
RX packets 0 bytes 0 (0.0 B) |
| 37 |
RX errors 0 dropped 0 overruns 0 frame 0 |
| 38 |
TX packets 0 bytes 0 (0.0 B) |
| 39 |
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 40 |
|
| 41 |
enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
| 42 |
inet 192.168.0.248 netmask 255.255.255.0 broadcast 192.168.0.255 |
| 43 |
inet6 fe80::201:2eff:fe80:8c2e prefixlen 64 scopeid 0x20<link> |
| 44 |
inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:fe80:8c2e prefixlen 64 |
| 45 |
scopeid 0x0<global> |
| 46 |
ether 00:01:2e:80:8c:2e txqueuelen 1000 (Ethernet) |
| 47 |
RX packets 123185 bytes 136156971 (129.8 MiB) |
| 48 |
RX errors 0 dropped 2 overruns 0 frame 0 |
| 49 |
TX packets 46499 bytes 8831194 (8.4 MiB) |
| 50 |
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 51 |
|
| 52 |
(i replaced ipv6 address with xxx....) |
| 53 |
|
| 54 |
|
| 55 |
|
| 56 |
On 11.03.19 09:23, Neil Bothwick wrote: |
| 57 |
> On Sun, 10 Mar 2019 18:55:29 -0400, Rich Freeman wrote: |
| 58 |
> |
| 59 |
>>> Mar 11 00:33:37 localhost ntpdate[4553]: Exiting, name server cannot |
| 60 |
>>> be used: Temporary failure in name resolution (-3)11 Mar 00:33:37 |
| 61 |
>>> ntpdate[4553]: name server cannot be used: Temporary failure in name |
| 62 |
>>> resolution (-3) |
| 63 |
>> Ok, you didn't mention what you're using for a network manager. How |
| 64 |
>> is the network interface being configured in the first place? There |
| 65 |
>> are several ways that it is commonly done. |
| 66 |
>> |
| 67 |
>> Also, what are you using for DNS? In particular, are you running a |
| 68 |
>> local DNS server, or are you relying on a network-supplied DNS server? |
| 69 |
>> How is /etc/resolv.conf being created (likely by the network manager, |
| 70 |
>> but maybe it is being done in another way). |
| 71 |
> Also, where is the NTP server? On the local network or external? |
| 72 |
>> ntpdate by default depends on network-online.target and not on |
| 73 |
>> nss-lookup.target, which can sometimes lead to issues if you're |
| 74 |
>> running a DNS server that isn't online when the network is online |
| 75 |
>> (such as a local server). |
| 76 |
> The definitions of when a network is actually online are variable, see |
| 77 |
> https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ |
| 78 |
> |
| 79 |
> You may need to add NetworkManager-wait-online.service or |
| 80 |
> systemd-networkd-wait-online.service to the dependencies for ntpdate, |
| 81 |
> which is possibly why Rich is asking how you manage your network. |
| 82 |
> |
| 83 |
> I don't use ntpdate here but systemd-timesyncd.service instead, which |
| 84 |
> seems to handle this better. |
| 85 |
> |
| 86 |
> |
Archives