On 01/12/2023 01:44, gene heskett wrote:
/e/n/i waa replaced, and nothing in an ip a or ip r was changed.
[...]
On 11/30/23 07:31, Max Nikulin wrote:
May it be that klipper-related "optimizers" add some script?
klipper runs fine on several other bananapi-m5 here, w/o any special
treatment
[...]
root@mkspi:/# journalctl -b
/root/xindi/src/mks_wpa_cli.cpp: 416
Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息:
Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-NETWORK-NOT-FOUND
Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28]
So to install "klipper is just a program" you run some scripts that
overwrite /etc/network/interfaces and you blame NetworkManager and some
other stuff instead.
Good luck in your attempts to find pieces of your "3d" network
configurator in cron tasks, all kinds of init scripts, and systemd
units. It is completely unrelated to Debian.
which requires it get rid of the 169.254.nnn.nnn its using now.
This case 169.254.x.y IPv4LL addresses is a manifestation of another
trouble. These addresses can coexist with 192.168.x.y addresses. Do not
concentrate on link local addresses.
I don't want or need a dhcp-server.
Then you are incompatible with software you are trying to run. Your options:
- do not allow scripts coming with klipper or its installer to touch
network configuration
- setup a DHCP server in your network and provide to 3d wizards
environment they expect.
