Networking problem

I have EndeavorOS installed on one partition of my hard disk. On the other I have Debian. I am able to access the Internet normally on the Debian partition and by using the EndeavorOS live USB stick. But I cannot access the Internet on the already installed EndeavorOS.

In short, I can’t access the Internet from the installed EndeavorOS but it works fine from USB stick.
The problem seems to have something to do with the partition. My wifi modem is TP-LINK CC20 if that helps anything. I have tried some other forums and searched with Google but have found nothing on this. Do I have to reinstall? What could it be that causes this kind of thing?

Thanks in advance for any help.

please post the result of the command ip a and also ip r

Ok, two screenshots, although the second one contains the results of both commands.


Sorry for posting twice, but I wasn’t sure if you wanted to see the results from within Debian (wifi working) or the one from within Endeavor (wifi not working). These are the results from Endeavor:

Sorry also if the transparency makes it unclear, but I was in a hurry. Thanks.

So you have a network device and it has an ip address and a route. pls show the result of ping 192.168.1.1 and traceroute 1.1.1.1, as well as iwconfig



That proves that you have internet connectivity. Nevertheless you may have DNS issues that prevent your browser from properly resolve URLs that you type in. Please show cat /etc/resolv.conf and also host -v www.google.com

1 Like

cat /etc/resolv.conf

Generated by NetworkManager

nameserver 192.168.1.1

That was from inside Debian. This is the output from Endeavor:
resolve

/etc/resolv.conv is missing, that is a problem. For testing you can just create this file with the content:
nameserver 1.1.1.1
and the dns resolution should work. Test this by host www.google.com

1 Like

That’s it. I don’t know why there was a symlink there to another file. I deleted the symlink and created the file with nameserver 1.1.1.1 Everything back to normal. Thank you!

That is not a proper solution, the symlink usually points to some file that is created when the connection comes online. This way it can adjust settings from changing from one to another network. A DNS should be configured by DHCP not manually. Either NeworkManager is used or systemd.resolved is used to provide this functionality. (I am not sure what the install default is on EOS). So one or the other should be configured to start. Find out by systemctl status networkmanageror systemctl status systemd-resolved. A disabled service has a line saying Loaded: loaded (… ; disabled; preset: enabled). An enabled service the line is Loaded: loaded (… ; enabled; preset: disabled).

1 Like

OK. Strangely, systemctl status networkmanager returns “no such service.” (or words to that effect)
systemctl status systemd-resolved is disabled.

I’m off to bed. I will peek in tomorrow morning for any next steps.

I enabled systemd-resolved and then started it. Now when I check /etc/resolv.conf it give me the proper name server 192.168.1.1 and says “Generated by Network Manager”. That should be it. Just one question one, if you have the chance: why was it disabled? I didn’t change anything. Thank you very much. You guys are great. I would never have found this solution through google or on Facebook groups.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.