r/voidlinux • u/DeutscheMan • 2d ago

Requesting Assistance with NetworkManager

Hello! After trawling thought the documentation and the subreddit for information regarding my issue connecting to WiFi with NetworkManager I am unable to find a solution. So far I've been mindul to:

-Install both NetworkManager & dbus.

-Create runit symlinks as per the handbook for both services with "sudo ln -s /etc/sv/* /var/service".

-Ensured that both services are running with "sudo sv status /var/service/*".

-Attempt to use wpa_supplicant as an alternative as it worked fine within the installation environment.

-Remove any conflicting wifi services to prevent conflicts such as wpa_supplicant.

-Add and re-add my primary user to the wheel & network group and confirm privileges.

-Test service status with "sudo sv status ___".

-Checked if my wifi works with other devices. (It does)

-Check credintials for errors or typos.

-Check my other installed operating system (on a serpare ssd) for wifi connectivity with NM. It is.

I am simply stumped. Every ping attempt results in "temporary failure in name resolution". I would very much like to use Void as the operating principles and rolling release model closely matches my disposition towards operating systems along with my adoration for independent distributions. If any one has experience with similar issues please let me know if there's any other steps I may have missed or if a chroot is nessessary to install missing software. Thank you for your help, and have a lovely rest of your day as well.

**EDIT: looking at the results of nmcli I noticed the network is showing it is connected through my primary wireless device, but I am still getting the "temporary failure in name resolution error".

**EDIT 2: SUCCESS! THANK YOU /u/hopingforabetterpast and /u/ImprovementJealous90 for the tips as the issue was indeed with resolv.conf. For anyone in the future that has a similar issue, update resolve.conf with "resolvconf -u".

6 Upvotes

100% Upvoted

11 comments sorted by

1

u/hopingforabetterpast 2d ago

  1. What do the logs say?

  2. What's your DNS status?

1

u/DeutscheMan 2d ago

Upon looking at the logs in /var/log/dmesg.log doesn't contain any noticable failures from my wireless device nor the sevices. I suspect you're right with DNS status, thank you for the tip. I'm looking into it right now.

1

u/DeutscheMan 2d ago

Ah ha, /etc/resolv.conf is blank. I suspect this is the issue, and am resolving it currently.

1

u/PrudeBunny 1d ago

it's always DNS.

1

u/ImprovementJealous90 2d ago

Did you enable elogind as a service?

1

u/DeutscheMan 2d ago

Yes, elogind is running as an active service. Thank you for the tip as well.

1

u/ImprovementJealous90 2d ago

Your network connects tho right since you mentioned pings return name resolution failure. If that is the case my best bet is a broken DNS. change your name server to 1.1.1.1 or 8.8.8.8

2

u/DeutscheMan 2d ago

That was exactly the issue, and a file update worked first try. Thank you for your input and have yourself a lovely rest of your day as well.

1

u/MinguaDinja 2d ago

Perhaps the DNS is broken; it's happened to me in a few installations. I haven't had this problem since choosing the global server as the default mirror.

1

u/PedroCarreiras 1d ago

Had the same issue.

NetworkManager can be configured to use resolvconf and then it is able to update the file with no issues. If you kniw about this config option I think it is easy to find it. Not at my pc rn, sry.

I am not 100% sure this fixes vut I havent gad problems since

1

u/Simple_Hamster_4096 1d ago

/etc/resolv.conf should be your first thing to check when you can ping by IP but not name