On 11/30/23 05:32, Dan Purgert wrote:
On Nov 29, 2023, gene heskett wrote:
On 11/29/23 17:52, Dan Purgert wrote:
On Nov 29, 2023, gene heskett wrote:
On 11/29/23 14:03, Greg Wooledge wrote:
On Wed, Nov 29, 2023 at 01:17:18PM -0500, Dan Purgert wrote:
'ntpd' I think (or is it systemd-timed or something like that nowadays?)
Gene's system is running some derivative of buster (Debian 10).
No I am not, Greg, been running bookworm for almost a year on this machine.
It is the 3d printer, a QIDI X-MAX 3, which is running armbian buster that
I am trying to fix. At least enough to set its clock, which is about a year
out of date ATM.
Just now did a powerdown which restarts it at:Sun 01 Jan 2023 06:02:14 AM
PST
I have added some of my hosts file into its hosts file, and I can ping back
and forth, and a valid ipv4 nameserver to resolv.conf and ping is working
locally. But I can't find where its setting its default ipv4 address to the
avahi bs, even with grep -r.
Avahi BS? APIPA ("A"utomatic "P"rivate "IP" "A"ddressing) is not
avahi/mDNS (aka Bonjour / Zeroconf).
Your DHCP client giving you an APIPA address is indicative of broken
DHCP, and the fix is either:
A. Fix your broken DHCP
B. Set the machine up with a static IP address
I'm kind of surprised that an Armbian box doesn't have a hwclock that
you can set the proper time on, to survive reboots (but anyway, I
imagine once you get the machine running with a valid IP address for
your network, it'll be able to use whatever time-sync service armbian
ships with (quick ddg search implies it ships with chrony installed /
setup as default).
I'll have to check that, but installing chrony here on this bookworm box
will remove the systemd thing, which is present on the armbian buster
Leave the bookworm PC alone - the problem is specifically on your
armbian box or network in general.
installed on it. ISTR I had the rpi4 setup on buster raspios plus my rt
kernel, and that static entry IIRC was in /etc/network/interfaces, which I
haven't tried yet. Was that buster or did they have a better place.
/etc/network/interfaces is the standard place for configuring network
interfaces in Debian and derivatives (although Network Mangler may be
offered as a frontend)
Tickled my memory, /etc/dhcpcd.conf would appear to be the place. But I'll
have to compose 100% of the option "static".
"Static" IP addressing is not handled in dhcp client configs.
According to the buster it is an option, and at one time, perhaps
wheezy, there was a whole stanza of commented code at the bottom of the
file, where last ditch descriptions could be uncommented and filled in
to suit a static setup after all efforts to find a dhcp server have
failed. This to me was the logical place to put that. Re-read the man
page. Its been simplified quite a bit but seems to exist yet if you
know how.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
