the ntpd on openwrt is confused by the a records and only tries IPv4 even though mesh-only-nodes have exclusively ipv6 addresses.
/usr/sbin/ntpd -n -N -S /usr/sbin/ntpd-hotplug -p 1.ntp.ffmd -p 2.ntp.ffmd -d
ntpd: '1.ntp.ffmd' is 10.139.0.9
ntpd: '2.ntp.ffmd' is 10.139.0.2
ntpd: sending query to 10.139.0.2
ntpd: sending query to 10.139.0.9
ntpd: timed out waiting for 10.139.0.2, reach 0x00, next query in 2s
ntpd: '2.ntp.ffmd' is 10.139.0.2
ntpd: timed out waiting for 10.139.0.9, reach 0x00, next query in 1s
ntpd: '1.ntp.ffmd' is 10.139.0.9
ntpd: sending query to 10.139.0.2
ntpd: sending query to 10.139.0.9
to allow mesh-only-nodes to adjust their system clock, we can remove the A records from 1.ntp.ffmd and 2.ntp.ffmd. This is relevant for both: the current batman net and the babel net.
the ntpd on openwrt is confused by the a records and only tries IPv4 even though mesh-only-nodes have exclusively ipv6 addresses.
to allow mesh-only-nodes to adjust their system clock, we can remove the A records from 1.ntp.ffmd and 2.ntp.ffmd. This is relevant for both: the current batman net and the babel net.