@wadesmart
While we wait for Daniel,
It would seem the NetworkManager daemon is not running
We need to see if any other network daemon is running
Could you have a careful scroll thru ps ax and see if you can see any network daemon - it might be called dhcpcd or networkd or wicked or maybe something else. It will probably end in d .
Your wifi must be being driven by some daemon, and we should not start NetworkManager while some other network daemon is running.
Cheers
Neville
79364 ? Ssl 0:04 /usr/sbin/NetworkManager --no-daemon
601 ? Ss 0:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers
those are the only two I see with network in the name.
Try this :
â°â†systemctl status NetworkManager
â NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-02-07 15:40:45 AWST; 4 days ago
Docs: man:NetworkManager(8)
Main PID: 1246 (NetworkManager)
Tasks: 3 (limit: 47903)
Memory: 13.3M
CGroup: /system.slice/NetworkManager.service
ââ1246 /usr/sbin/NetworkManager --no-daemon
Feb 12 06:05:51 titan NetworkManager[1246]: <info> [1644617151.0401] manager: NetworkManager state is now CONNECTED_SITE
... (snip snip) ...
Feb 12 07:57:26 titan NetworkManager[1246]: <info> [1644623846.1872] manager: NetworkManager state is now CONNECTED_GLOBAL
(you donât necessarily need sudo to query the status of a systemd service, but you could prefix that with sudo - as in âsudo systemctl status NetworkManagerâ)
What youâre looking for is âloadedâ and âactive (running)â - or any errors below those lines. If it shows something else - e.g. error, inactive, dead - then maybe try restarting it (you will need sudo) :
sudo systemctl restart NetworkManager
then check it again :
systemctl status NetworkManager
Or even maybe :
sudo systemctl stop NetworkManager
Wait 20-30 seconds, then start it again :
systemctl start NetworkManager
then check it again :
systemctl status NetworkManager
But - if that still doesnât work - not sure how I can help - sorry⊠I can only make certain assumptions - e.g. your ethernet switch is also your internet / wifi router / modem device, and it has a DHCP server running and providing IP addresses via ethernet.
My ethernet link is a bit more complex, at my desk in my home office, I have a 24 port switch, thatâs cabled to a 500 Mbit Ethernet over Power (Powerline) device, my WiFi modem/router is patched to another Powerline device in the kitchen - whenever anything goes wrong, power outage, one Powerline device goes offline, ethernet still works âisolatedâ (ethernet devices in my office can still talk to one another, but not beyond my switch), i.e. my DHCP scopeâs leases are so long, devices keep their IP addresses for days before asking for a new lease, if thereâs an issue with Powerline devices, I usually just pull them out of the wall and plug them back in.
Note : I just saw your update. Looks like itâs running, but you could check for any errors with (sometimes the âdebugâ info at the bottom of the output has clues to which files to check - not that Iâve ever had to - NetworkManager on Ubuntu seems mostly plug and play - but not always so on Debian):
sudo systemctl status NetworkManager
as my process tree looks much like yours :
ps -ef |grep -i network 130 â”
root 1246 1 0 Feb07 ? 00:03:00 /usr/sbin/NetworkManager --no-daemon
root 1256 1 0 Feb07 ? 00:00:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers
Also show us the output of
ip a
or maybe
sudo /sbin/ifconfig -a
â and furthermore â
To find out some DHCP info - something like :
ââx@titan ~
â°â†sudo ls -al /var/lib/NetworkManager
total 64
drwx------ 2 root root 4096 Feb 12 08:31 .
drwxr-xr-x 87 root root 4096 Feb 11 17:38 ..
-rw-r--r-- 1 root root 1212 Feb 21 2021 dhclient-2b36729a-a43d-3d8e-a353-4763e90a0212-enp39s0.lease
-rw-r--r-- 1 root root 69 Feb 21 2021 dhclient6-2b36729a-a43d-3d8e-a353-4763e90a0212-enp39s0.lease
-rw-r--r-- 1 root root 2324 Feb 21 2021 dhclient-enp39s0.conf
-rw-r--r-- 1 root root 57 Feb 11 03:40 internal-2b36729a-a43d-3d8e-a353-4763e90a0212-enp39s0.lease
-rw-r--r-- 1 root root 55 Dec 5 18:55 internal-30729d94-0b0d-3e2d-8f53-8f6137b02626-enx1a5589a26942.lease
-rw-r--r-- 1 root root 57 Oct 21 21:43 internal-31934c8a-c65b-3c30-95e8-e699c0a44721-eth0.lease
-rw-r--r-- 1 root root 57 Feb 2 19:46 internal-50656978-691b-4c28-a80b-117c88314036-wlp41s0.lease
-rw-r--r-- 1 root root 55 Sep 28 20:20 internal-690207c9-2352-3a1d-9b68-68300d6f06fd-enx1a5589a26942.lease
-rw-r--r-- 1 root root 57 Oct 24 12:20 internal-b1ca5a16-deec-3a8f-b210-834dd65d1ad4-eth0.lease
-rw-r--r-- 1 root root 939 Feb 21 2021 NetworkManager-intern.conf
-rw-r--r-- 1 root root 69 Feb 7 15:39 NetworkManager.state
-rw------- 1 root root 32 Feb 21 2021 secret_key
-rw-r--r-- 1 root root 70 Feb 7 15:39 seen-bssids
-rw-r--r-- 1 root root 868 Feb 12 08:31 timestamps
Above - the file Iâm looking for is *.lease file with my NIC device name âenp39s0â, but the slightly longer version of this file is for IPV6 âdhclient6â - Iâm only interested in IPV4 âdhclientâ - so :
ââx@titan ~
â°â†sudo cat /var/lib/NetworkManager/dhclient-2b36729a-a43d-3d8e-a353-4763e90a0212-enp39s0.lease
lease {
interface "enp39s0";
fixed-address x.x.x.x;
option subnet-mask x.x.x.x;
option routers x.x.x.x;
option dhcp-lease-time 604800;
option dhcp-message-type 5;
option domain-name-servers 8.8.8.8,8.8.4.4;
option dhcp-server-identifier x.x.x.x;
option domain-name "LOCAL";
renew 3 2021/02/24 05:43:19;
rebind 6 2021/02/27 06:22:19;
expire 0 2021/02/28 03:22:19;
}
lease {
interface "enp39s0";
fixed-address x.x.x.x;
option subnet-mask x.x.x.x;
option dhcp-lease-time 604800;
option routers x.x.x.x;
option dhcp-message-type 5;
option dhcp-server-identifier x.x.x.x;
option domain-name-servers 8.8.8.8,8.8.4.4;
option domain-name "LOCAL";
renew 2 2021/02/23 22:11:18;
rebind 6 2021/02/27 07:56:08;
expire 0 2021/02/28 04:56:08;
}
lease {
interface "enp39s0";
fixed-address x.x.x.x;
option subnet-mask x.x.x.x;
option routers x.x.x.x;
option dhcp-lease-time 604800;
option dhcp-message-type 5;
option domain-name-servers 8.8.8.8,8.8.4.4;
option dhcp-server-identifier x.x.x.x;
option domain-name "LOCAL";
renew 3 2021/02/24 04:02:12;
rebind 6 2021/02/27 07:58:09;
expire 0 2021/02/28 04:58:09;
}
(note - Iâve âredactedâ my site specific addresses with x.x.x.x)
sudo systemctl status NetworkManager
NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Friday 2022-02-11 10:52:05 CST; 7hr ago
Docs: man:NetworkManager(8)
Main PID: 79364
Tasks: 3 (limit: 3573)
Memory: 8.4M
CGroup: /system.slice/NetworkManager.service ->79364 /usr/sbin/NetworkManger --no-daemon
⊠Ill run the other commands and post back. Working tonight.
trekjunky@Enterprise:~$ aptin wicked
[sudo] password for trekjunky:
Sorry, try again.
[sudo] password for trekjunky:
Reading package lists⊠Done
Building dependency tree
Reading state information⊠Done
E: Unable to locate package wicked
So it looks like you only have NetworkManager, but it is dead or inactive, or poorly configured
Follow what Daniel suggests.
@TrekJunky
So they have removed it, just like Devuan.
Must be a reason for scrapping it. Maybe the project folded
NetworkManager seems to have taken over in most distros. It is not easy to configure, in my opinion
@nevj
To me this looks like it is running :
Itâs âloadedâ, and âenabledâ, its Active state is : âactive (running)â
But Iâd need to see all the debug / diag stuff at the bottom of the output - e.g. in my case :
â NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-02-07 15:40:45 AWST; 4 days ago
Docs: man:NetworkManager(8)
Main PID: 1246 (NetworkManager)
Tasks: 3 (limit: 47903)
Memory: 13.3M
CGroup: /system.slice/NetworkManager.service
ââ1246 /usr/sbin/NetworkManager --no-daemon
Feb 12 06:56:14 titan NetworkManager[1246]: <info> [1644620174.0398] manager: NetworkManager state is now CONNECTED_SITE
Feb 12 06:56:15 titan NetworkManager[1246]: <info> [1644620175.5411] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 12 07:06:35 titan NetworkManager[1246]: <info> [1644620795.0400] manager: NetworkManager state is now CONNECTED_SITE
Feb 12 07:06:35 titan NetworkManager[1246]: <info> [1644620795.5163] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 12 07:56:55 titan NetworkManager[1246]: <info> [1644623815.0402] manager: NetworkManager state is now CONNECTED_SITE
Feb 12 07:57:03 titan NetworkManager[1246]: <info> [1644623823.6364] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 12 07:57:18 titan NetworkManager[1246]: <info> [1644623838.0401] manager: NetworkManager state is now CONNECTED_SITE
Feb 12 07:57:26 titan NetworkManager[1246]: <info> [1644623846.1872] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 12 09:02:44 titan NetworkManager[1246]: <info> [1644627764.0398] manager: NetworkManager state is now CONNECTED_SITE
Feb 12 09:02:59 titan NetworkManager[1246]: <info> [1644627779.5621] manager: NetworkManager state is now CONNECTED_GLOBAL
And any DHCP info - per my earlier post.
I wonder is the ethernet connector not turned to connected in the panel icon?
Thereâs also the output of nmcli, or even ânmcli device showâ⊠If youâre going to paste the output - could you format it as âcodeâ - i.e. select the text you pasted and hit the â</>â button in the forum toolbar (next to " and left of the âUploadâ button) - it makes our job easier to read your output if character spacing and indentation is âpreservedââŠ
ââx@titan ~
â°â†nmcli
enp39s0: connected to Wired connection 1
"Realtek RTL8111/8168/8411"
ethernet (r8169), 2C:F0:5D:74:48:B8, hw, mtu 1500
ip4 default, ip6 default
inet4 x.x.x.x/24
route4 0.0.0.0/0
route4 x.x.x.0/24
route4 169.254.0.0/16
inet6 fe80::dd6b:44d4:76e9:4a2e/64
route6 fe80::/64
route6 ::/0
wlp41s0: unavailable
"Intel 6 AX200"
wifi (iwlwifi), 68:54:5A:D3:53:74, sw disabled, hw, mtu 1500
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
gpd0: unmanaged
"gpd0"
tun, sw, mtu 1500
DNS configuration:
servers: x.x.x.x
interface: enp39s0
Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
Note : wlp41s0 is unavailabe 'cause I disabled WiFi in the top panel doohicky widget thingie on the right, âWi-Fi Offâ :
Try wicd
We are both spelling it wrong
Debian and Devuan have removed wicd because it depends on python2. When the python3 version of wicd is available, it might reappear.
So the basic install misconfigures on install?
Hi Wade,
I missed this comment way back
Does it really fail to connect the wired interface with the lower panel button?
It is confusing
When it is disconnected, the button says connect
When it is connected, the button says disconnect
Stupid isnt it.
Now if that is the case, I wonder if the driver for the ethernet interface does not load when you boot?
Can check it easily - use dmesg
sudo dmesg | more
and scroll thru all the boot sequence until you find name of ethernet interface. What does it say there? Does it load a driver?
Neville
Yes - never connected when it it did that.
See my other reply.
If the interface does not connect NetworkManager will not configure it.
NetworkManager is dynamic, it will configure at any time ( because it is a daemon) but the interface has to be connected. It configures at boot too, but if you add something while Linux is running NetworkManager hops in and configures the new item.
It can be very confusing
Neville
Right, so something is not enabling the interface, before it gets to NetworkManager.
Can you go ahead and investigate if the driver is there using
sudo dmesg | more
Sorry for slow reply. We had our covid booster yesterday - some reaction - sleeping it off
Neville
@daniel.m.tripp
Can you think of anything other than a driver missing that would cause the lower panel button not to connect to an ethernet interface?
Neville
No idea mate⊠curious to see if nmcli works, and what the output is⊠Iâve no idea what wicd is, never used itâŠ
Good job on getting your booster @nevj mate! I got AZ first two shots (got crook for a couple days after first one), but Pfizer for my booster, all I got was a sore arm for a couple days.
@daniel.m.tripp
Yeah, we had same, 2 x AZ, and now Phizer. Am sleeping it off today.
Wife had bad reaction to second AZ - rash, suspected clots, the works.
She is better than me this time with Phizer.
Will prompt Wade to do the nmcli
Neville
@wadesmart
Can you also do the
nmcli
that Daniel suggested please?
Neville