On 2023-03-02 00:24, David Wright wrote:
On Tue 28 Feb 2023 at 16:05:14 (+0100), daven...@tuxfamily.org wrote:
On 2023-02-28 05:27, David Wright wrote:
> On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
> > On 2023-02-23 02:59, cono...@panix.com wrote:
[ … ]
Well, it looks like cruft from an earlier installation of networking;
and a couple of months later, you installed ifupdown and wpasupplicant,
by the looks of things. I don't know whether /etc/network/interfaces
itself would interfere with however connman is configured.
This system never had any debian 10 or lower. It has been issued to my
by $worksplace
in december 2021, initially running windows.
I erased the full disk and installed à "default" (official image) debian
11, from an LXDE live USB image
It has never had any interface named eth0. I still fail to see why setup
conf would refer to eth0 at all
Then I few month later, I finally took the time to debug why WiFi card
didn't work/what firmware is needed
Debian's firmware packaged started supporting the WLAN/WiFi card
after I installed my system.
So then I installed the firmware. I most likely installed wpasuppicant
the same day, and tested it worked.
Not sure about ifup thought. Doesn't seem to be a wpasupplicant
dependency.
akb@akira:~$ LC_ALL=C aptitude why ifupdown
p netscript-2.4 Provides ifupdown
p netscript-2.4 Depends bridge-utils (>= 0.9.3)
p bridge-utils Suggests ifupdown
akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
p netscript-2.4 Provides ifupdown
Why openresolv wouldn't work?
Cheers,
David.
