NTP with time.google.com after a reboot
-
@johnpoz ok, I also tried an empty /conf/ntp-boot-time-servers file to disable the bootstrap setting of time, disabled IPv6 configuration on the Starlink interface rebooted, and NTP still attempted to use an IPv6 interface address on the Starlink interface, even though none exists:
Jul 8 15:43:59 ntpd 81262 failed to init interface for address fe80::f2ad:4eff:fe1d:bd1f%12 Jul 8 15:43:59 ntpd 81262 unable to create socket on mvneta0.4092 (27) for fe80::f2ad:4eff:fe1d:bd1f%12#123 Jul 8 15:43:59 ntpd 81262 bind(45) AF_INET6 fe80::f2ad:4eff:fe1d:bd1f%12#123 flags 0x11 failed: Can't assign requested address Jul 8 15:43:40 ntpd 81262 108.61.56.35 144a 8a sys_peerI re-enabled the Starlink IPv6 setup, deleted the /conf/ntp-boot-time-servers file (restoring default behavior) and NTP is now still reporting being unable to to create a socket on the Starlink interface IPv6 address. I must be missing something I'd done before. To wit:
Jul 8 16:11:20 ntpd 78011 failed to init interface for address fe80::f2ad:4eff:fe1d:bd1f%18 Jul 8 16:11:20 ntpd 78011 unable to create socket on mvneta0.4092 (30) for fe80::f2ad:4eff:fe1d:bd1f%18#123 Jul 8 16:11:20 ntpd 78011 bind(45) AF_INET6 fe80::f2ad:4eff:fe1d:bd1f%18#123 flags 0x11 failed: Can't assign requested addressBarring documentation that this attempt to use an IPv6 interface for NTP socket creation when IPv6 is disabled on the router is normal behavior, this appears to be a bug. Otherwise, it's hard for me to figure out why normal behavior would be to attempt the use of an IPv6 address when it's disabled system wide and loop an error every five minutes forever.
Interestingly, earlier in the NTP log during boot, it appears to be trying to use IPv6 addresses on every interface, but only fails on the Starlink interface:
Jul 8 15:55:47 ntpd 78011 failed to init interface for address fe80::f2ad:4eff:fe1d:bd1f%18 Jul 8 15:55:47 ntpd 78011 unable to create socket on mvneta0.4092 (23) for fe80::f2ad:4eff:fe1d:bd1f%18#123 Jul 8 15:55:47 ntpd 78011 bind(43) AF_INET6 fe80::f2ad:4eff:fe1d:bd1f%18#123 flags 0x11 failed: Can't assign requested address Jul 8 15:55:47 ntpd 78011 Listen normally on 22 mvneta0.60 192.168.60.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 21 mvneta0.60 [fe80::f2ad:4eff:fe1d:bd1f%17]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 20 mvneta0.50 192.168.50.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 19 mvneta0.50 [fe80::f2ad:4eff:fe1d:bd1f%16]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 18 mvneta0.40 192.168.40.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 17 mvneta0.40 [fe80::f2ad:4eff:fe1d:bd1f%15]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 16 mvneta0.30 192.168.30.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 15 mvneta0.30 [fe80::f2ad:4eff:fe1d:bd1f%14]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 14 mvneta0.20 192.168.20.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 13 mvneta0.20 [fe80::f2ad:4eff:fe1d:bd1f%13]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 12 mvneta0.10 192.168.10.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 11 mvneta0.10 [fe80::f2ad:4eff:fe1d:bd1f%12]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 10 mvneta0.4091 192.168.2.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 9 mvneta0.4091 [fe80::f2ad:4eff:fe1d:bd1f%11]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 8 mvneta0.4090 192.168.12.216:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 7 mvneta0.4090 [fe80::f2ad:4eff:fe1d:bd1f%10]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 6 lo0 10.10.10.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 5 lo0 127.0.0.1:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 4 lo0 [fe80::1%7]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 3 lo0 [::1]:123 Jul 8 15:55:47 ntpd 78011 Listen normally on 2 mvneta0 [fe80::f2ad:4eff:fe1d:bd1f%1]:123 Jul 8 15:55:47 ntpd 78011 Listen and drop on 1 v4wildcard 0.0.0.0:123 Jul 8 15:55:47 ntpd 78011 Listen and drop on 0 v6wildcard [::]:123 Jul 8 15:55:47 ntpd 78011 gps base set to 2023-01-01 (week 2243) Jul 8 15:55:47 ntpd 78011 basedate set to 2022-12-26 Jul 8 15:55:47 ntpd 78011 proto: precision = 0.320 usec (-21) Jul 8 15:55:47 ntpd 77912 ---------------------------------------------------- Jul 8 15:55:47 ntpd 77912 available at https://www.nwtime.org/support Jul 8 15:55:47 ntpd 77912 corporation. Support and training for ntp-4 are Jul 8 15:55:47 ntpd 77912 Inc. (NTF), a non-profit 501(c)(3) public-benefit Jul 8 15:55:47 ntpd 77912 ntp-4 is maintained by Network Time Foundation, Jul 8 15:55:47 ntpd 77912 ---------------------------------------------------- Jul 8 15:55:47 ntpd 77912 Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid Jul 8 15:55:47 ntpd 77912 ntpd 4.2.8p15@1.3728-o Sat Jan 7 19:55:07 UTC 2023 (1): Starting -
Ok, without rebooting I went back to the Starlink interface, disabled IPv6 again, then re-enabled it again and the NTP IPv6 socket error has stopped. I can't reboot now to test if the error returns with a reboot but will try later.
Seems flaky.