Skip to main content
Topic: Networking Problems (Read 748 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Networking Problems

I have as I am sure many of you have been experiencing networking issues. My Artix system (Thinkpad X230) can no longer connect to the internet. At first it was that it couldn't connect after a suspension, then after a few reboots networking as a whole just stopped working.

I have noticed the same issue on Void Linux and there are mentions of it too on the Arch forums.

From what I have gathered it appears to be an issue with d-bus, but I am just speculating.

Has anyone managed to fix this yet?

Re: Networking Problems

Reply #1
you are providing too little information about the problem.
I did not notice this problem, internet works for me without any problems.
what exactly is the problem? hardware, firmware, software, kernel?

Re: Networking Problems

Reply #2
@OP: Check logs. That should be the first thing that you do when something goes wrong in GNU/Linux. GNU/Linux (non-systemd) systems have an excellent textual logging feature that writes to /var/log, so you can dissect the problem more efficiently than on proprietary systems.

If you haven't done anything to your system configuration-file-wise, I'd say that looks more like a network hardware issue. Try using the (Ethernet) network with LiveUSB. If that doesn't work, then indeed it is a hardware issue.

And read the documentation. Read Artix/Arch wiki, manual pages, package documentation/websites... if you don't know how to check if the service is up or not, you should read up on it.

Re: Networking Problems

Reply #3
I have as I am sure many of you have been experiencing networking issues.
No connection problem here for two years.
N.B. I use connman.

$ pacman -Qs connman
local/connman 1.39-1
    Intel's modular network connection manager
local/connman-gtk 1.1.1-3
    Tray menu and GTK3 GUI for ConnMan
local/connman-openrc 20210506-1 (openrc-galaxy)
    OpenRC connman init script

Re: Networking Problems

Reply #4
I have noticed the same issue on Void Linux and there are mentions of it too on the Arch forums.

From what I have gathered it appears to be an issue with d-bus, but I am just speculating.
Let me guess: you use something like NetworkManager for your network connections, and the issue with dbus is that it is not enabled.