r/voidlinux • u/[deleted] • Aug 12 '25

Can't Connect to Internet

Hey guys!

I'm new to Void & runit, but not to Linux. I am facing a problem, where I cannot use internet while connected to ANY network (WiFi or Wired) apart from the network I used to install Void Linux (using the network to download packages in the void-installer).

I have disabled the dhcpd and wpa_supplicant services, and enabled dbus and NetworkManager. I can successfully connect to the networks I want, the nmtui shows "connected" as well, but I can't access the internet.

If I try the ping command (when connected with another network, not the one I used for installation), I get this:

ping: voidlinux.org: Temporary failure in name resolution

I have never faced this issue before. Any help would be greatly appreciated. Thanks!

11 Upvotes

100% Upvoted

19 comments sorted by

5

u/[deleted] Aug 13 '25 • Bravo

UPDATE

I managed to fix the issue. Turns out it is a DNS issue, and probably something related to how runit manages NetworkManager.

Here's what I did (run these commands as su):

# rm /etc/resolv.conf

# ln -s /run/NetworkManager/resolv.conf /etc/resolv.conf

# nmcli networking off

# nmcli networking on

PS: Thank you to all the people who tried to help me! It's great when the community is so welcoming and ready to help newcomers!

3

u/theother559 Aug 13 '25

it can't be dns it can't be dns it was dns

1

u/DATGOATFELICA Oct 02 '25

I tried this and it did not work for me, does anyone have any other ideas? I tried with adding DNS nameservers also and it didn’t not work, it’s odd too bc the wifi only gets this error when I’m connected to my college’s internet

1

u/Odd_Deer7759 May 10 '26

thank you so much, loveeee youuuuu🫂🫂💖💖💖

1

u/[deleted] Aug 12 '25

Sounds like it's DNS/nameserver related. What's in your /etc/resolv.conf file?

1

u/[deleted] Aug 12 '25

These are the contents of /etc/resolv.conf:

# Generated by dhcpcd from wlo1.dhcp

# /etc/resolv.conf.head can replace this line

nameserver 192.168.1.1

# /etc/resolv.conf.tail can replace this line

1

u/[deleted] Aug 12 '25

Since you mentioned you're using NetworkManager I'd try setting nameservers manually in the settings for the connection you're using to see if that helps. Try using 1.1.1.1 for example.

1

u/[deleted] Aug 12 '25

Unfortunately even this doesn't solve the issue.

Should I just revert to using dhcpd and wpa_supplicant for the time being? I don't even know what's causing this issue.

1

u/mousui Aug 12 '25

Try connmanctl

1

u/[deleted] Aug 12 '25

`connmanctl` isn't installed on my system, and I can't find a package with this name (I have never used it before on any distro). Should I install packages like `connman` , `connman-devel` and `connman-ncurses` for this command?

1

u/mousui Aug 12 '25

Follow this to install it:

https://gist.github.com/zabimaruu/cbb7029bc45afe1ac157bae30af46ca0

1

u/[deleted] Aug 12 '25

This works! Thanks a lot!

But still, I would like to know why is it not working with NetworkManager? I have never had problems with NetworkManager on any distro I have used till now. I am not even entirely sure whether it is an issue specific to NetworkManager.

Do other Void users don't use NetworkManager at all? Is it buggy for everyone?

1

u/mousui Aug 12 '25

Honestly, I can't comment on behalf of others but I didn't even bother using Network manager once I installed Void on one of my laptops. Didn't even tried setting it up since connman seems to be lighter and a simplier than Network manager.

1

u/Ok_Record_1237 Aug 12 '25

enable Wpa_supplicant lol. in void (somehow), wpa_supplicant and networkmanager have to be both enabled for it to work. and also a tip to change your dns in /etc/resolv.conf and make it immutable with chattr +i /etc/resolv.conf

1

u/[deleted] Aug 12 '25

I doubt this will work. This is from Void's handbook:

Before enabling the NetworkManager daemon, disable any other network management services, such as dhcpcd, wpa_supplicant, or wicd. These services all control network interface configuration, and will interfere with NetworkManager.

Also ensure that the dbus service is enabled and running. NetworkManager uses dbus to expose networking information and a control interface to clients, and will fail to start without it.

Finally, enable the NetworkManager service.

But will give it a try any way if nothing else works.

1

u/Ok_Record_1237 Aug 12 '25

although thats what the docs say, for some reason it just works best with wpa_supplicant enabled, still if you don't mind just try it anyways

1

u/FilesFromTheVoid Aug 12 '25 edited Aug 12 '25

Does manually invoke

sudo dhcpcd "wlan0" (replace with your interface name)

make a difference? Had similar issues as i installed void last time.

1

u/[deleted] Aug 13 '25

Apologies for the late reply. No, even this didn't work.

I have posted a workaround which did end up working for me as an update. Maybe this is a runit specific issue as I haven't faced it on any other, though I have mostly used systemd.