Hi Gene,

On Wed, Nov 29, 2023 at 01:52:46PM -0500, gene heskett wrote:
> On 11/29/23 13:20, John Hasler wrote:
> > But first fix that address.
> 
> How, John? QIDI is afraid of enabling full net access because it might
> overwrite some of their special stuff. Right now its running armbian buster,
> which is out of support.  And surprise, kiauh.sh is installed, likely how
> they set the printer up in the first place.  Its just a bash script but its
> magic!

No one knows what any of this stuff is because it's NOT DEBIAN and
this is DEBIAN-users. You should ask these questions on the support
venues for whatever these things are, where you will get fewer
answers that are specific to Debian.

Once you've got your networking sorted out and you are setting up an
NTP server, your next issue will be that one NTP server isn't
enough:

    
https://www.ntp.org/ntpfaq/ntp-s-algo-real/#532-why-should-i-have-more-than-one-clock

The reason for this is that if you have just one NTP server for your
network, and it goes bad (tells the wrong time), no one will be able
to tell.

If you have two, clients will be able to tell that one of them has
gone bad (or both!) but not which one of them.

If you have at least three, then it is possible to determine when
one of them is off.

Unless you have a dedicated time source (e.g. GPS receiver, atomic
decay source, …) then any NTP server you set up will not be
significantly better than just using the public NTP pool as all
Debian NTP clients are configured to do by default.

So basically I would say there is no point in you trying to run an
NTP server and you should just try to make sure that all your
machines having working networking and run a working NTP client.

If you DID want to run an NTP server on your network, all it would
achieve is slightly reducing the amount of traffic you send over the
Internet, however it would be entirely unsurprising for your local
NTP clients to select the remote servers as being more accurate and
send the packets over the Internet anyway. And since you need at
least least three clocks defined in every NTP client, you can't
avoid configuring at least two off-site servers. It may as well be
all three (preferably more).

But sort the networking out first.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Reply via email to