On 02/12/2023 02:24, gene heskett wrote:
On 12/1/23 10:27, Max Nikulin wrote:
so I have to repeat it. You *do* *not* have NetworkManager installed
hence it can not overwrite files.
What particular *evidences* do you have that namely NetworkManager
overwrites /etc/network/interfaces? I am not interested in you
*speculations*.
[...]
I do not know the mechanism by which my addition and deletions were done
during boot, I had added the correct data to put eth0 at 192.168.71.100
in /e/n/i, and had deleted the line saying it was managed by
networkmanager. The evidence I have is that the original file was
restored, has only lo and the line giving credit to networkmanager was
restored, my additions were gone. Based on the evidence I can see, what
else am I supposed to think?
The only problem is that neither upstream sources nor debian patches in
buster or bookworm contain the "Network is managed" text as in (from an
earlier message):
root@mkspi:/# cat /etc/network/interfaces
source /etc/network/interfaces.d/*
# Network is managed by Network manager<-this line I had removed
auto lo
iface lo inet loopback
So ask the 3d printer vendor why you see this misleading line and why
ifupdown and NetworkManager are broken.
I had a hope that you would at least check list of processes, systemd
units, init scripts for something suspicious. Instead I still see
speculations again and attempts to blame NetworkManager developers for
no reason.
Have you tried some online translator to guess meaning of the following?
Jan 02 02:56:20 mkspi bash[1443]: 已获取到了扫描的结果
Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28]
/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]: WPS-AP-AVAILABLE
Have you find files containing these messages?